- openstack-discuss - lists.openstack.org

[nova][libvirtd] internal error: unable to execute QEMU command 'query-named-block-nodes'
by Satish Patel 22 Oct '24

22 Oct '24

Folks, I have a ceph cluster and recently I configured rbd-mirror to replicate all data to remove ceph cluster for disaster recovery. Yesterday for POC we did a hard cutover on ceph and point openstack to the new cluster. All other vms came back up fine but 2 vms stuck in this error state in libvirt logs 2024-01-31 22:44:37.591+0000: 474597: error : qemuMonitorJSONCheckErrorFull:399 : internal error: unable to execute QEMU command 'query-named-block-nodes': cannot read image start for probe: Permission denied If it's a wider issue than it should impact all the vms but why only two VM stuck and not starting and libvirt giving me this error in logs nova-compute logs also showing same error 2024-01-31 22:44:40.925 7 INFO nova.compute.manager [None req-b33485b5-8740-48ae-8b5b-a440de3f11a4 c48fcfb9347f413f92fcece065644b00 ca5c652478c7429e964257990800e9cb - - default default] [instance: 2de0f880-77c7-4d2c-9e01-898c57ad3693] Successfully reverted task state from powering-on on failure for instance. 2024-01-31 22:44:40.944 7 ERROR oslo_messaging.rpc.server [None req-b33485b5-8740-48ae-8b5b-a440de3f11a4 c48fcfb9347f413f92fcece065644b00 ca5c652478c7429e964257990800e9cb - - default default] Exception during message handling: libvirt.libvirtError: internal error: unable to execute QEMU command 'query-named-block-nodes': cannot read image start for probe: Permission denied

3 8

[swift][ptg] Ops Feedback Session - 23 October at 14:00 UTC
by Tim Burke 22 Oct '24

22 Oct '24

As we've done in PTGs past, we're getting devs and ops together to talk about Swift: what's working, what isn't, and what would be most helpful to improve. We're meeting on meetpad (https://meetpad.opendev.org/p/swift-epoxy-ops-feedback) on Wednesday at 14:00UTC -- if you run a Swift cluster, we hope to see you there! Even if you can't make it, we'd appreciate it if you can offer some feedback on the etherpad (https://etherpad.opendev.org/p/swift-epoxy-ops-feedback) This has always been a highlight at every PTG for the swift developers. Have your say and help make the next Swift the best one yet! Tim

1 0

[all][rbac] Canceling policy popup team tomorrow meeting
by Ghanshyam Mann 22 Oct '24

22 Oct '24

Hello Everyone, Due to vPTG weeks, I am cancelling the policy pop-up tomorrow meeting. https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… -gmann

1 0

[cinder] 2025.1 PTG reminder
by Jon Bernard 21 Oct '24

21 Oct '24

Hello all, We covered the schedule in last week's meeting but I wanted to post it here for reference. For Cinder, we are meeting Wednesday, Thursday, and Friday of this week from 14:00 UTC until 17:00 UTC. I have consolidated and updated our etherpad [1] to include both a tentative schedule that includes cross-project session commitments and the set of proposed topics. As we did in the previous PTG, we'll be using the same google meet link and the sessions will be recorded. Everything should be noted in the etherpad. If you notice something is missing please add it or reach out with any questions. See you all in a couple of days! [1] https://etherpad.opendev.org/p/epoxy-ptg-cinder -- Jon

1 0

[openstack-helm] 2025.1 PTG reminder
by Vladimir Kozhukalov 21 Oct '24

21 Oct '24

Hi dear helmers, This is a reminder that we have a PTG session scheduled at 15:00-18:00 UTC on Wednesday 2024-10-23 [1]. This time we have quite a lot to discuss (and this is good) so I booked a 3 hours session (instead of our usual 2 hours). If you have something to discuss please put topics to the Etherpad [2] [1] https://ptg.opendev.org/ptg.html [2] https://etherpad.opendev.org/p/oct2024-ptg-os-helm -- Best regards, Kozhukalov Vladimir

1 0

Spot Instances
by Mia 21 Oct '24

21 Oct '24

Hello everyone, I am working on a project in the OpenStack environment. More precisely, I am looking into the implementation of spot instances as a cost optimization strategy and better resource utilization. If any community members could share their experiences and insights related to the following areas, it would be greatly appreciated. Implementation Strategies: How did you go about implementing spot instances in your cluster? Challenges Faced: Mention some of the challenges or limitations. Best Practices: Do you have any recommendations or best practices that you would like to suggest for seamless deployment? Thank you very much for your time and support.

8 11

[all][designate][manila] Grenade job failures caused by GLOBAL_VENV=True
by Takashi Kajinami 21 Oct '24

21 Oct '24

Just in case you are not aware of the situation. The change to enable GLOBAL_VENV in grenade job was recently merged[1] in core grenade. As we saw when the same was introduced in devstack some time ago, some project got their (grenade) jobs broken and need a few adjustments. [1] https://review.opendev.org/c/openstack/grenade/+/930507 So far I'm aware that the change affected manila and designate, which I'm fixing by the changes below. Please be careful in case you see grenade job failing in your project. designate: - https://review.opendev.org/c/openstack/designate/+/932697 Disable GLOBAL_VENV in grenade This is temporal workaround and needs to be reverted once the actual fix below is merged in master and backported to stable 2024.1/2 - https://review.opendev.org/c/openstack/designate/+/932697 devstack: Fix manage.py execution with GLOBAL_VENV This actually fixes the current issue caused by GLOBAL_VENV=True. As noted above, we have to backport this to stable branches manila: - https://review.opendev.org/c/openstack/manila/+/932671 Disable GLOBAL_VENV in grenade This is temporal workaround and needs to be reverted once the actual fix below is merged in master and backported to stable 2024.1/2 - https://review.opendev.org/c/openstack/manila/+/932665 devstack: Fix missing manila command This actually fixes the current issue caused by GLOBAL_VENV=True. As noted above, we have to backport this to stable branches Thank you, Takashi -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

4 4

[ptg][sunbeam] Epoxy cycle PTG 2025.1 schedule
by Guillaume Boutry 21 Oct '24

21 Oct '24

Hi All, OpenStack PTG has been scheduled on Oct 22nd and Oct 24th 2024 [1] and I have scheduled the following time slots for the OpenStack Sunbeam project. Tuesday 22 October 2024 0600 UTC to 0800 UTC Thursday 24 October 2024 1400 UTC to 1600 UTC The meeting links and details are in ptg link [2] or etherpad [3]. Feel free to add the topics of interest to discuss in the etherpad [3]. [1] https://openinfra.dev/ptg/ [2] https://ptg.opendev.org/ptg.html [3] https://etherpad.opendev.org/p/oct2024-ptg-sunbeam Looking forward to seeing you next week! Regards, Guillaume Boutry

1 0

[tacker] Cancel IRC meeting this week
by Yasufumi Ogawa 21 Oct '24

21 Oct '24

Hi tacker team, Since we have vPTG sessions, I'm going to cancel weekly IRC meeting tomorrow. Thanks Yasufumi

1 0

[ptl][tc][all] Community Leaders meeting at the PTG
by Goutham Pacha Ravi 21 Oct '24

21 Oct '24

Hello PTLs, Project Liaisons, Core Reviewers, and invested maintainers, The TC is hosting a cross project session with all OpenStack project leaders at 1400 UTC today (2024-10-21). Please see the PTG schedule at https://ptg.opendev.org/ptg.html and the TC PTG etherpad for details: https://etherpad.opendev.org/p/oct2024-ptg-os-tc We look forward to seeing you all there! P.S: while you are there, you may also be interested in the cross project goal proposal/discussion for migrating away from Eventlet (1500 UTC); and other community-wide topics in the TC PTG room. Thanks, Goutham Pacha Ravi OpenStack TC Chair

1 0