lpetrut's profile - activity

We'd need the event log messages as well in order to figure out what's wrong. Worst case scenario, the rbd-wnbd service

The above issues have been addressed, here's a beta Reef MSI that includes this fix: https://cloudbase.it/downloads/ceph

Also, the PR caches a single cluster connection, meaning that we can no longer connect to multiple clusters. One workaro

The PR hasn't merged upstream yet but we might apply it downstream. I did notice a few issues while running some tests:

Here's a preview MSI: https://cloudbase.it/downloads/cephdevsingle_process.msi. Please let me know if you hit any issues

Hi, I suggest checking the Openstack controller conf files (e.g. nova api) and use the same keystone endpoint. It might

Hi, Openstack Liberty was released in 2015, it was discontinued a long time ago. Also, we've announced that we'd no lo

The PR is up for review: https://github.com/ceph/ceph/pull/52540. Let me know if you'd like to try out a custom MSI befo

I've fixed the crashes, will have a PR soon. We'll most probably include this in the Reef msi.

I'll need to discuss it with the RBD team and see if it's a known issue.

The good news is that the OSD connections are shared when using a single process, so the number of connections is signif

Hi, Other Ceph users reported similar problems with rbd + qemu: https://ceph-users.ceph.narkive.com/SZb6qTQB/understand

That's expected. Openstack request headers must include the authentication token.

Hi, I suggest double checking the credentials from the [neutron] section. You can also compare it against your Openstac

Hi, I suggest double checking the credentials from the [neutron] section. You can also compare it against your Openstac

Thanks for the updates, keep us posted.

Hi, The MSIs from cloudbase.it are updated daily, including the latest WNBD version. You can verify it by doing a wnbd

Hi, The beta MSIs from cloudbase.it are updated daily, including the latest WNBD version. Regards, Lucian

Hi, What happens if you manually create that folder, i.e. by issuing a mkdir command? The following isn't necessarily

Hi, What happens if you manually create that folder, i.e. by issuing a mkdir command? The following isn't necessarily

Hi, For RBD mappings, there are two components: the WNBD driver and the userspace daemon (rbd-wnbd). rbd-wnbd logging

Have you specified the user? For example: rbd ls --user hostadmin.

Do the keyring files have the same content? Can you double check the paths? It might be that nodepad added a .txt extens

The next official Ceph release (Reef) is scheduled for late June: https://lists.ceph.io/hyperkitty/list/dev@ceph.io/thre

Hi, We've recently added live resize support, basically watching for rbd resize events and notifying the driver accordi

duplicate of https://ask.cloudbase.it/question/3517/looking-for-the-rocky-version-of-hypervnovacompute/?answer=3518#post

Hi, Here are the MSI links: https://cloudbase.it/downloads/HyperVNovaCompute_Rocky_18_0_3.msi https://cloudbase.it/dow

Hi, Here are the MSI links: https://cloudbase.it/downloads/HyperVNovaComputeRocky1803.msi https://cloudbase.it/downloa

Since all Victoria releases should have this change, I think you have multiple Neutron controllers and there's a chance

Even the above mentioned (breaking) rpc change got backported: https://review.opendev.org/q/I2e3aa7c400d7bb17cc117b65faa

The Neutron controller and the Hyper-V Neutron agent should use the same Openstack release (e.g. Victoria). However, Neu

Hi, I think your Neutron controller is using an older, incompatible version. Could you please check? The Neutron RPC i

Hi, Can you please send us the Ceph version (ceph-dokan -v)? ceph-dokan can log to stderr, event log and/or a log file

Hi, This seems to be the problem: 'ovs-vsctl: tcp:127.0.0.1:6640: database connection failed ()\r\n'. Make sure that O

You can use qemu-img to retrieve the interal image size. The actual file size can be much lower when dealing with dynami

It's useful to have both API and hypervisor side logs so that we can correlate them. I'd be interested to see when the r

Hi, I suggest enabling debug logging and follow the request id. You should be able to see the following in your nova co

One option would be to use the "manage volume" feature. You'd request Cinder to "unmanage" it, manually move it and then

Sure, just set the following in nova.conf: [hyperv] instance_automatic_shutdown = true Note that changing this option

Sure, just set the following: [hyperv] instance_automatic_shutdown = true Note that changing this option won't affect

Sure, just set the following: [hyperv] instanceautomaticshutdown = true Note that changing this option won't affect al

Hi, Not at the moment. There's been an inline TODO since forever but it never got implemented: https://github.com/opens

Judging by your error message, looks like ovsdb-monitor is still connecting to that "pipe" instead of the 6640 tcp port.

Judging by your error message, looks like ovsdb-monitor is still connecting to that "pipe" instead of the 6640 tcp port.

Hmm, recent Windows Sever versions include ovsdb binaries that may not work properly with neutron. One idea would be to

Hi, ovsdb is probably not configured to listen to that pipe. In most cases, ovsdb listens to :6640. You may set the fol

Hi, ovsdb is probably not configured to listen to that pipe. In most cases, ovsdb listens to :6640. You may set the fol

Small update: networking-hyperv 7.0.1 has been released. In case you want to stick to the current configuration, you may

The bad news is that it's a networking-hyperv bug, the good news is that I sent a fix and we'll soon have updated MSIs.