- openstack-discuss - lists.openstack.org

[freezer] IRC channel #openstack-freezer has been registered
by Dmitriy Rabotyagov 28 Mar '24

28 Mar '24

Hey folks, After ML [1] some folks joined the #openstack-freezer channel on OFTC network, but I asked ppl to leave it since we had to empty the channel and register it accordingly. I'm glad to announce that this process has been completed (huge kudos to Jeremy Stanley (fungi) for helping with that!) and everyone interested in reviving/contributing to the Freezer project are warmly welcome to join the channel. [1] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack…

2 1

[Glance] Cancelling Today's Weekly Meeting
by Pranali Deore 27 Mar '24

27 Mar '24

Hello, Cancelling today's meeting since there is nothing much on agenda for today. Thanks & Regards, Pranali Deore

1 0

tool can be used to monitor an OpenStack
by kjme001＠gmail.com 27 Mar '24

27 Mar '24

hello what tool can be used to monitor an OpenStack cluster? Regards

2 1

[tc][ptg] PTG Schedule
by Jay Faulkner 27 Mar '24

27 Mar '24

Hi all, I've put together a tentative schedule for TC topics and times for discussion on the etherpad: https://etherpad.opendev.org/p/apr2024-ptg-os-tc -- it may change if new topics emerge. Please let me know if any of the scheduled times are a hardship or if there are any questions. Thanks, Jay Faulkner OpenStack TC Chair

1 0

[ptl][release] OpenStack Caracal OpenInfra Live
by Allison Price 27 Mar '24

27 Mar '24

Hi everyone, Apologies for the late notice, but I wanted to gather interest from PTLs to participate in an OpenStack Caracal OpenInfra Live next Thursday, April 3 after Wednesday’s release. Like past episodes (you can see Bobcat here [1]), we will give interested PTLs the opportunity to present the progress their team made in Caracal as well as present upcoming priorities for Dalmatian. The episode will air on Thursday at 1400 UTC, so interested participants would need to be available 1330-1500 UTC on Thursday, April 3. If you are interested, please let me know. Thanks! Allison [1] https://www.youtube.com/watch?v=q7WDncK3YuM

6 9

Proposing Pete Zaitcev as Cinder core
by Rajat Dhasmana 27 Mar '24

27 Mar '24

Hello everyone, I would like to nominate Pete Zaitcev for the Cinder core position. Here is a summary of the work done by Pete in the Cinder project: 1. Reviews In the last 90 days[1] (half cycle), he has been the third highest reviewer in number (after 2 cores) and has a decent +/- ratio (stating that he frequently suggests improvements/asks questions in patches) In the last 180 days[2] (one cycle), we see the same pattern. 2. Commits Pete has taken over the backup domain of Cinder, which was not very actively looked at before. He has already completed features and fixes to improve our backup drivers, and is actively looking to improve swift and ceph backup backends which are the most used by OpenStack users. 3. Community Presence Pete consistently attends Cinder upstream events like meetings, festival of XS reviews, midcycles, PTGs etc. Apart from that, Pete also brings expertise from his Swift experience in the object storage domain. Given all the above reasons, I feel Pete is a good candidate for the cinder core team. I will keep this thread open for 1 week and if there are no objections, I will add Pete to the cinder core group. [1] https://www.stackalytics.io/report/contribution?module=cinder-group&project… [2] https://www.stackalytics.io/report/contribution?module=cinder-group&project… Thanks Rajat Dhasmana

5 6

[cinder][PTG] Cinder 2024.2 Dalmatian PTG planning
by Jon Bernard 27 Mar '24

27 Mar '24

Hi All, We will be conducting the Cinder 2024.2 (Dalmatian) PTG in a couple of weeks from Tuesday April 9th to Friday April 12th from 1300-1700 UTC[1]. The etherpad and schedule for Cinder PTG is here[2]. [1] https://ptg.opendev.org/ptg.html [2] https://etherpad.opendev.org/p/dalmatian-ptg-cinder Please add any topics or ideas you wish to propose for discussion to the "planning" section of the etherpad. Once we have the final set of topics, they will be distributed across our available days. Following are the details of the event: Dates: 9 April (Tuesday) - 12 April (Friday), 2024 Time: 1300 - 1700 UTC Room: Newton Video conference Tool: Zoom (Link can be found on the PTG page[1] by clicking on Cinder slot) Thanks! -- Jon

2 1

[cinder] This week's meeting (today) will be in video+IRC
by Rajat Dhasmana 27 Mar '24

27 Mar '24

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (today) will be held in video + IRC mode with the following details: Date: 27th March, 2024 Time: 1400 UTC Meeting link: https://meet.google.com/zya-oxpp-qre IRC Channel: #openstack-meeting-alt Make sure you're connected to both the gmeet meeting and IRC as discussion can happen at both places depending on how the author wants to conduct it. Thanks Rajat Dhasmana

1 0

Network would be shown to a member but IP allocation would be denied?
by Mika Saari 27 Mar '24

27 Mar '24

Hi, I am currently testing kolla-ansible using the latest release. During the creation of an external/provider network ("public"), I have observed that a non-admin project ("test") can view the network and allocate IP addresses for routers, for example. I would like to restrict this behavior so that the external network is listable (openstack network list), but IP allocation is denied. I have experimented with RBAC rules, creating a new role ("view-only") and assigning it to a user ("user") in the "test" project. I modified the policy.yaml files in both Neutron and Horizon as outlined in the documentation ( https://docs.openstack.org/kolla-ansible/latest/admin/advanced-configuratio… ). Below are the snippets from my neutron/policy.yaml and horizon/neutron_policy.yaml files created following the sample https://docs.openstack.org/neutron/2023.2/configuration/policy-sample.html policy.yaml get_network: "(rule:admin_only) or (role:view_only)" get_subnet: "(rule:admin_only) or (role:view_only)" get_port: "(rule:admin_only) or (role:view_only)" get_router: "(rule:admin_only) or (role:view_only)" neutron_policy.yaml get_network: "(rule:admin_only) or (role:view_only)" get_subnet: "(rule:admin_only) or (role:view_only)" get_port: "(rule:admin_only) or (role:view_only)" get_router: "(rule:admin_only) or (role:view_only)" After deploying Neutron and Horizon, I adjusted the default RBAC policy so that the "External Network" action only affects the "admin" project, not "*". While the admin can still see the public network, the test project user with the "view_only" role cannot see the "public" network. Enabling the RBAC policy for the "test" project allows the network to be visible, but it also enables the member of the project ("user") to reserve IP addresses for network components. I'm seeking guidance on where to find more information about policies to achieve the desired functionality. Should I redeploy all the services, or is depolying Neutron and Horizon sufficient? Am I on the right track with my policy tests, or is there a simpler way to achieve this functionality? Thank you very much for your assistance!

2 6

[ansible][aio][bobcat] How to contract on AWS EC2 instance (Only one instance)
by Tatsuro Makita 27 Mar '24

27 Mar '24

Hi I try to contract using openstack-ansible aio on AWS EC2 instance (only one node). refer to construction steps: https://docs.openstack.org/openstack-ansible/latest/user/aio/quickstart.html but it will occurred some problems with below, i can't proceed on this way. https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… My purpose is what it checks any functions(version = 28.0.1 or 27.0.1). anyone tell me an easy way to build on a single instance on AWS EC2? Or is there a procedure to build on several instances without VLANs? EC2 does not allow VLANs. Could you support / share any information? Thanks regards.

2 2

[Openstack] [shibboleth] Seeking Advice: Shibboleth Integration with OpenStack
by Abubakur Sait 25 Mar '24

25 Mar '24

Hello, I'm currently engaged in PhD research focused on integrating Shibboleth with OpenStack. I've encountered a challenge as many of the available resources seem to be outdated, with the most recent OpenStack version mentioned being Queens. I'm reaching out to the community for assistance: - Which operating system version are you using for this setup? - What version of OpenStack are you currently running with Shibboleth? Additionally, if you have any up-to-date tutorials or books on Shibboleth that you could recommend, I would greatly appreciate it. Thank you in advance for your help. Best regards, Abubakur Sait

2 1

[nova][ptg] Etherpad for next April vPTG
by Sylvain Bauza 25 Mar '24

25 Mar '24

Hi folks, As a reminder, we'll have another round of nova sessions at the PTG. You'll find all the connection details and the timeslots in the etherpad but you'll also have the opportunity to chime on the discussions by providing your own subjects in the etherpad. Feel free to add your topics with your IRC name at the bottom of https://etherpad.opendev.org/p/nova-dalmatian-ptg The more, the merrier. Thanks, -Sylvain

1 0

[tc][ptg] Topic proposals: Re-visioning OpenStack; Raising the bar for Activity
by Jay Faulkner 25 Mar '24

25 Mar '24

Hi all, I added two semi-related PTG topics to the TC etherpad that I wanted to evangelize to the community. Both have details on https://etherpad.opendev.org/p/apr2024-ptg-os-tc, starting around line 65. The first topic, 'Re-visioning OpenStack aka "What is OpenStack Now?"', is centered around a couple of related things; the last time we made a vision document for OpenStack was 2019 -- five years ago. We need to revisit what our vision for OpenStack is, better defining what projects are in and out of scope of OpenStack. There are more details on the linked etherpad; I look forward to your comments there. The second topic, "Raising the bar for Activity", is centered around a singular focus: preventing us from having another situation where there is a severe security vulnerability in an OpenStack project which cannot be fixed. In fact, when reviewing the OpenInfra Foundation's Project Confirmation Guidelines ( https://board.openinfra.dev/en/ProjectConfirmationGuidelines ) -- a standard OpenStack in the aggregate is supposed to meet -- we have many projects that would not pass this if viewed more singularly. There are more details on the linked etherpad; I look forward to your comments there. Thanks, Jay Faulkner OpenStack TC Chair

1 0

[ironic] canceling meetings April 1st and April 8th
by Riccardo Pittau 25 Mar '24

25 Mar '24

Hello ironicers! We're canceling the ironic weekly meetings for the next 2 weeks: - April 1st is bank holiday in many countries in Europe and America and most of the cores won't be available - April 8th is the first day of the PTG Next meeting will be held on April 15th Ciao Riccardo

1 0

[tc] Next TC Meeting Tomorrow, March 26, 1800 UTC
by Jay Faulkner 25 Mar '24

25 Mar '24

Hi all, The next TC meeting is scheduled for tomorrow at 1800 UTC in #openstack-tc on OFTC. The proposed agenda is: - Roll call - Follow up on tracked action items - Gate health check - Implementation of Unmaintained branch statuses - 2024.2 Dalmatian TC Election - Election results cannot be merged due to affiliation diversity policy https://review.opendev.org/c/openstack/governance/+/913912 - TC vPTG 2024.2 - https://etherpad.opendev.org/p/apr2024-ptg-os-tc - Open Discussion and Reviews Thanks, Jay Faulkner OpenStack TC Chair

1 0

[nova] Instance migration/resize changes availability zone
by Marc Vorwerk 25 Mar '24

25 Mar '24

Dear OpenStack Community, I am reaching out for support with an issue that is specifically affecting a single instance during migration or resize operations in our OpenStack environment. I want to emphasize that this problem is isolated and does not reflect a broader issue within our cloud setup. The issue arises when attempting a resize of the instance's flavor, which only differs in RAM+CPU specification. Unexpectedly, the instance attempts to switch its availability zone from az1 to az2, which is not the intended behavior. The instance entered an error state during the resize or migration process, with a fault message indicating 'ImageNotFound', because after the availability zone change the volume cant be reached. We use seperate ceph clusters per az. To debug this issue we enabled debug logs for the nova scheduler and found that the scheduler does not filter out any node with any of our enabled filter plugins. As a quick test we disabled a couple of compute nodes and could also verify that the ComputeFilter of the nova-scheduler still just returns the full list of all nodes in the cluster. So it seems to us that for some reason the nova-scheduler just ignores all enabled filter plugins for mentioned instance. It's worth noting that other instances with the same flavor on the same compute node do not exhibit these issues, highlighting the unique nature of this problem. Furthermore we checked all relevant database tables to see if for some reason something strange is saved for this instance but it seems to us that the instance has exactly the same attributes as other instances on this node. We are seeking insights or suggestions from anyone who might have experienced similar issues or has knowledge of potential causes and solutions. What specific logs or configuration details would be helpful for us to provide to facilitate further diagnosis? We greatly appreciate any guidance or assistance the community can offer. Best regards, Marc Vorwerk + Maximilian Stinsky

5 6

[neutron] Bug Deputy Report March 18 - March 24
by Lajos Katona 25 Mar '24

25 Mar '24

Hi Neutron Team, I was the bug deputy for Neutron from 18March to 24 March, here comes my report for the week. - https://bugs.launchpad.net/neutron/+bug/2058400 ([ovn-octavia-provider] functional jobs are unstable) - Fernando Royo started to investigate the issues - https://bugs.launchpad.net/neutron/+bug/2058400/comments/2 - https://bugs.launchpad.net/neutron/+bug/2058378 ([devstack-tobiko-neutron] stable/2023.2 periodic broken with ERROR: Cannot install tox==4.13.0, tox==4.14.0 and tox==4.14.1) - https://review.opendev.org/c/x/devstack-plugin-tobiko/+/913746 fixed the failure. - https://bugs.launchpad.net/neutron/+bug/2058712 ([openvswitch-agent] Trunk extension should not be loaded if service plugin is disabled) - In progress: https://review.opendev.org/c/openstack/neutron/+/913979 - https://bugs.launchpad.net/neutron/+bug/2055419 (network autoallocation fails for non-admin user) - Incomplete: It seems something is missing for the reproduction - https://bugs.launchpad.net/neutron/+bug/2058433 (a public network with multi subnets , but based on ovn, They can't communicate with each other) - Incomplete: I try to collect some configurations, but somebody with more OVN background should check it also. Best wishes Lajos Katona (lajoskatona)

1 0

Please Help To Setup Bumblebee VDI project based on DevStack
by Matthew Swigart 24 Mar '24

24 Mar '24

Hello, I'm trying to install the VDI project on my Ubuntu 22.04 LTS Desktop VMware workstation. So I chose Bumblebee(https://github.com/NeCTAR-RC/bumblebee) and went through several steps like configuring the devstack, installing docker, and Bumblebee project. And then, I tried to create a virtual desktop from Bumblebee and I got the below error: ValueError: badly formed hexadecimal UUID string Attached error screenshot: [image: image.png] Anybody has already experienced a similar issue or does anybody have any idea to solve this problem? Then please help me. Looking forward to hearing from you. Much appreciated. Matthew

3 2

[all][elections][ptl] 2024.2 Dalmatian: PTL Election Conclusion & Results
by Ian Y. Choi 24 Mar '24

24 Mar '24

Thank you to the electorate, to all those who voted and to all candidates who put their name forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. Now for the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Adjutant - Dale Smith (dalees) * Barbican - Grzegorz Grasza (xek) * Blazar - Pierre Riteau (priteau) * Cinder - Jon Bernard () * Cloudkitty - Rafael Weingartner () * Cyborg - alex song (songwenping) * Designate - Michael Johnson (johnsom) * Glance - Pranali Deore (pdeore) * Heat - Takashi Kajinami (tkajinam) * Horizon - Tatiana Ovchinnikova (tmazur) * Ironic - Riccardo Pittau (rpittau) * Keystone - Dave Wilde (d34dh0r53) * Kolla - Michal Nasiadka (mnasiadka) * Magnum - Jake Yip (jakeyip) * Manila - Carlos Silva (carloss) * Masakari - sam sue () * Mistral - axel vanzaghi () * Monasca - Hasan Acar () * Neutron - Brian Haley (haleyb) * Nova - Sylvain Bauza (bauzas) * Octavia - Gregory Thiemonge (gthiemonge) * OpenStack Helm - Vladimir Kozhukalov (kozhukalov) * OpenStackAnsible - Dmitriy Rabotyagov (noonedeadpunk) * OpenStackSDK - Artem Goncharov (gtema) * Puppet OpenStack - Takashi Kajinami (tkajinam) * Quality Assurance - Martin Kopec (kopecmartin) * Rally - Andrey Kurilin (andreykurilin) * Storlets - Takashi Kajinami (tkajinam) * Sunbeam - Hemanth Nakkina () * Swift - Tim Burke (timburke) * Tacker - Yasufumi Ogawa (yasufum) * Telemetry - Erno Kuvaja (jokke_) * Venus - Eric Zhang () * Vitrage - Dmitriy Rabotyagov (noonedeadpunk) * Zaqar - Hao Wang (wanghao) * Zun - Hongbin Lu () Elections: no election required. For remaining projects (without PTL candidates), TC will work on the appointment. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all involved in the PTL election process, Ian Y. Choi, on behalf of the OpenStack Technical Election Officials

1 0

Accessing virsh in openstack wallaby | tripleo
by Swogat Pradhan 24 Mar '24

24 Mar '24

Hi, Can someone please tell me how can i access the virsh utility on the compute node on openstack wallaby? Previously we used nova_libvirt but in wallaby there are multiple containers and i am unable to use virsh utility to edit my domain.xml file. List of containers: [root@dcn01-hci-2 ~]# podman ps | grep nova 10d981158842 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtlogd_wrapper e91667516afc 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtsecretd a4b07fe0e833 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtnodedevd d7e1db393e9c 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtstoraged 5308a171793e 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 2 months ago nova_virtqemud f490a6249ba1 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo kolla_start 2 months ago Up 6 weeks ago nova_virtproxyd ab0441e56957 172.25.201.68:8787/tripleomaster/openstack-nova-compute:current-tripleo kolla_start 2 months ago Up 2 months ago (healthy) nova_migration_target f35fbba5b690 172.25.201.68:8787/tripleomaster/openstack-nova-compute:current-tripleo kolla_start 2 months ago Up 6 weeks ago (unhealthy) nova_compute 82bc01993106 172.25.201.68:8787/tripleomaster/openstack-nova-libvirt:current-tripleo /usr/sbin/virtlog... 2 months ago Up 2 months ago Can someone please suggest how I can i edit an instance xml file in this setup? With regards, Swogat Pradhan

2 5

Openstack trove Error launching instance
by Shameem Farhath 23 Mar '24

23 Mar '24

Hi Team, Myself Shameem, on behalf of NerveDigital i am writing this mail. We are provisioning the trove database as a service in our existing infrastructure, and we got an ERROR on launching a DB instance. We have been troubleshooting it for a while and find no hope. Please help us to find a proper resolution for the issue. Please find the attached ERROR while launching the instance. Openstack version: yoga Operating system used: Ubuntu 22.04 Guest operating system: ubuntu jammy (downloaded from opendev tarball) Configuration files: Attached ERROR from the log: Attached *Regards,* *Shameem Farhath A* *9562440781* *www.NerveDigital.net* <http://www.NerveDigital.net>

1 0

[openstack-ansible][horizon][keystone] multidomain - LDAP admins unable to see Horizon Admin Dashboard
by Janet 'Saoirse' Sullivan 22 Mar '24

22 Mar '24

Hi, I have a multi-domain setup (LDAP and Default) and while LDAP users can see the Projects and Identity tabs in the Horizon dashboard, they can't see the Admin tab, even if they are assigned the admin role. The Default domain admin user can see this dashboard just fine. Is there a policy that needs to be changed so LDAP users with the admin role can see the Admin tab in Horizon? Openstack 2023.2.

1 0

[TC][all] Recheck analysis
by Sławek Kapłoński 22 Mar '24

22 Mar '24

Hi Stackers, Some time ago I started monitoring something what we have called "bare rechecks" which are "recheck" comments without any reason given. I was also asking various teams to improve that, try to check failures of the CI jobs and put some kind of reason in the recheck comment. That went pretty well and currently most of the teams are doing pretty good job there. See stats from last 30 days: +--------------------+---------------+--------------+-------------------+ | Team | Bare rechecks | All Rechecks | Bare rechecks [%] | +--------------------+---------------+--------------+-------------------+ | OpenStackSDK | 8 | 8 | 100.0 | | OpenStack-Helm | 41 | 41 | 100.0 | | cloudkitty | 1 | 1 | 100.0 | | monasca | 6 | 6 | 100.0 | | skyline | 2 | 2 | 100.0 | | trove | 1 | 1 | 100.0 | | rally | 1 | 1 | 100.0 | | watcher | 1 | 1 | 100.0 | | mistral | 5 | 8 | 62.5 | | kuryr | 1 | 2 | 50.0 | | zaqar | 1 | 2 | 50.0 | | horizon | 6 | 15 | 40.0 | | swift | 9 | 25 | 36.0 | | manila | 5 | 14 | 35.71 | | kolla | 14 | 68 | 20.59 | | cinder | 15 | 77 | 19.48 | | ironic | 10 | 53 | 18.87 | | glance | 11 | 59 | 18.64 | | requirements | 13 | 73 | 17.81 | | Telemetry | 2 | 12 | 16.67 | | nova | 16 | 105 | 15.24 | | OpenStackAnsible | 5 | 40 | 12.5 | | magnum | 1 | 9 | 11.11 | | neutron | 13 | 118 | 11.02 | | Quality Assurance | 3 | 30 | 10.0 | | Release Management | 1 | 12 | 8.33 | | octavia | 2 | 34 | 5.88 | | keystone | 0 | 1 | 0.0 | | OpenStack Charms | 0 | 1 | 0.0 | | oslo | 0 | 8 | 0.0 | | Puppet OpenStack | 0 | 95 | 0.0 | | barbican | 0 | 2 | 0.0 | | designate | 0 | 4 | 0.0 | | heat | 0 | 7 | 0.0 | | tacker | 0 | 63 | 0.0 | | tripleo | 0 | 4 | 0.0 | +--------------------+---------------+--------------+-------------------+ Now I though that it's time for the "next step" so I spent some time looking at the reasons of the rechecks done in last 30 days. I collected those reasons with script [1] and here are some top reasons found: +----------------------------------------------------------+----------------------+ | Recheck comment | Number of occurences | +----------------------------------------------------------+----------------------+ | recheck unrelated failure | 48 | | recheck irrelevant failure | 45 | | recheck unrelated test failure | 9 | | recheck testing | 9 | | recheck infra-failure | 9 | | recheck tempest-slow-py3 | 8 | | recheck nova-next | 8 | | recheck timeout | 7 | | recheck neutron-functional-with-uwsgi | 7 | | recheck failure not related to this change | 7 | | recheck ovn-octavia-provider-functional-master unrelated | 7 | | recheck jobs running too early | 6 | | recheck dependency updated | 5 | | recheck random failure | 5 | | recheck - bifrost bug | 5 | +----------------------------------------------------------+----------------------+ Those comments as they were put in the gerrit. Of course there was much more different comments there. I just wanted to highlight here some of the most common ones. I also asked ChatGPT to group all of them in some common groups. Below are some of the main categories of the reason found by the ChatGPT: CI/Testing Issues: Timeouts in various tests (e.g., tempest tests, tox tests). Infrastructure failures impacting CI. Kernel panics or guest panics during testing. Dependency-related failures (merged or updated). Unexpected failures or intermittent issues. Dependency Management: Dependency patches merged or updated. Dependency-related failures. Release/Documentation Updates: Release note fixes or updates. Content cleanup or removal. Documentation-related failures. Infrastructure/Tooling: Infrastructure mirror issues. Tooling updates or fixes (e.g., grub2-tools, proliantutils). Issues related to mirror servers. Specific Project/Component Issues: Nova-related failures (e.g., nova-ceph-multistore). Cinder-related failures (e.g., cinder-plugin-ceph-tempest). OpenStack SDK related failures. Configuration/Setup Problems: Problems with deployment or setup (e.g., grub2-tools missing, bifrost bug). Issues with configurations (e.g., host patterns). Network/Connection Problems: DNS resolution issues. Timeout errors related to network operations. Post-Failure Analysis: Attempts to reproduce failures. Investigation into infrastructural problems. Finally some conclusion from this analysis. It seems that our most common reason of the gate instability is something called "unrelated/irrelevant failure" and also things like "infra failure". In both cases we can't really do much to try to improve that as this information is not enough. So I would like to ask all of You to try to be more precise in the recheck comments and give more detailed reasons why You recheck Your patch. If for example You have to recheck the patch due to "unrelated failure", please write there also bug number which cause failure or simply give there name of the unrelated failed test or something like that. That way when I will do similar analysis in e.g. month from now maybe it will be easier to identify most common bugs which are causing "unrelated failures" and try to prioritize somehow work on fix of that bug. [1] https://github.com/slawqo/rechecks-stats/blob/main/rechecks_stats/rechecks_… -- Slawek Kaplonski Principal Software Engineer Red Hat

8 16

[ironic]Server does not accept power operations when running OpenStack Ironic on Redfish
by Junya Noguchi (Fujitsu) 22 Mar '24

22 Mar '24

To whom it may concern. My name is Junya Noguchi. We have the following problems and questions. Please respond. 1. Problems and Questions When we use OpenStack Ironic Redfish driver to manage Redfish capable server, the server may not accept power on operations. Server may or may not power on. We want to clarify whether this is a server-specific issue or an OpenStack Ironic bug. Occurrence event ・Auto-cleaning or instance startup failed. ・Ironic does not power on via Redfish driver (see log) ・We tried increasing the power_state_change in ironic.conf to 30 minutes, but it didn't resolved. ・It does not happen when changing Redfish to IPMI 2. Server information R272-P31 (GIGABYTE Arm Server) CPU : Ampere Altra Max 2.8GHz-3.0GHz 1/128 Memory : 256GB Disk : 1TB/SSDx3/RAID1 Server firmware : MegaRac SP-X：https://www.ami.com/megarac/ ※It states that it is compatible with IPMI/Redfish Openstaack ver : Zed Hardware interface : redfish Power interface : redfish Boot interface : pxe Deploy interface : direct Network interface : flat 3. Log File : /var/log/ironic/ironic-conductor.log 2023-12-19 10:24:47.677 384940 DEBUG sushy.connector [-] HTTP request: GET "Server FQDN"/redfish/v1/Systems/Self; headers: {'OData-Version': '4.0'}; body: None; blocking: False; timeout: 60; session arguments: {}; _op /usr/lib/python3.9/site-packages/sushy/connector.py:118 2023-12-19 10:24:49.975 384940 DEBUG sushy.connector [-] HTTP response for GET "Server FQDN"/redfish/v1/Systems/Self: status code: 200 _op /usr/lib/python3.9/site-packages/sushy/connector.py:226 2023-12-19 10:24:49.976 384940 DEBUG sushy.resources.base [-] Received representation of System /redfish/v1/Systems/Self: {'_actions': {'reset': {'allowed_values': None, 'operation_apply_time_support': {'_maintenance_window_resource': {'resource_uri': '/redfish/v1/Systems/Self'}, 'maintenance_window_duration_in_seconds': 600, 'maintenance_window_start_time': None, 'mapped_supported_values': [<ApplyTime.IMMEDIATE: 'Immediate'>, <ApplyTime.AT_MAINTENANCE_WINDOW_START: 'AtMaintenanceWindowStart'>], 'supported_values': ['Immediate', 'AtMaintenanceWindowStart']}, 'target_uri': '/redfish/v1/Systems/Self/Actions/ComputerSystem.Reset'}}, '_oem_vendors': ['Gbt'], '_settings': None, 'asset_tag': 'Free form asset tag', 'bios_version': 'F31h (SCP: 2.10.20220531)', 'boot': {'allowed_values': ['None', 'Pxe', 'Floppy', 'Cd', 'Usb', 'Hdd', 'BiosSetup', 'Utilities', 'UefiShell', 'UefiTarget', 'SDCard', 'UefiHttp', 'RemoteDrive', 'UefiBootNext'], 'enabled': <BootSourceOverrideEnabled.ONCE: 'Once'>, 'mode': <BootSourceOverrideMode.UEFI: 'UEFI'>, 'target': <BootSource.PXE: 'Pxe'>}, 'description': 'System Self', 'hostname': None, 'identity': 'Self', 'indicator_led': <IndicatorLED.OFF: 'Off'>, 'links': {'oem_vendors': None}, 'maintenance_window': None, 'manufacturer': 'GIGABYTE', 'memory_summary': {'health': 'OK', 'size_gib': 256}, 'name': 'System', 'part_number': '000000000001', 'power_state': <PowerState.OFF: 'Off'>, 'serial_number': 'XXXXXXXXXXXXXX', 'sku': '01234567890123456789AB', 'status': {'health': <Health.OK: 'OK'>, 'health_rollup': <Health.CRITICAL: 'Critical'>, 'state': <State.ENABLED: 'Enabled'>}, 'system_type': <SystemType.PHYSICAL: 'Physical'>, 'uuid': '00000000-0000-4000-8000-D85ED387A8B3'} refresh /usr/lib/python3.9/site-packages/sushy/resources/base.py:689 2023-12-19 10:24:49.976 384940 ERROR oslo.service.loopingcall [-] Dynamic backoff interval looping call 'ironic.conductor.utils.node_wait_for_power_state.<locals>._wait' failed: oslo_service.loopingcall.LoopingCallTimeOut: Looping call timed out after 1490.91 seconds 2023-12-19 10:24:49.976 384940 ERROR oslo.service.loopingcall Traceback (most recent call last): 2023-12-19 10:24:49.976 384940 ERROR oslo.service.loopingcall File "/usr/lib/python3.9/site-packages/oslo_service/loopingcall.py", line 154, in _run_loop 2023-12-19 10:24:49.976 384940 ERROR oslo.service.loopingcall idle = idle_for_func(result, self._elapsed(watch)) 2023-12-19 10:24:49.976 384940 ERROR oslo.service.loopingcall File "/usr/lib/python3.9/site-packages/oslo_service/loopingcall.py", line 349, in _idle_for 2023-12-19 10:24:49.976 384940 ERROR oslo.service.loopingcall raise LoopingCallTimeOut( 2023-12-19 10:24:49.976 384940 ERROR oslo.service.loopingcall oslo_service.loopingcall.LoopingCallTimeOut: Looping call timed out after 1490.91 seconds 2023-12-19 10:24:49.976 384940 ERROR oslo.service.loopingcall 2023-12-19 10:24:49.977 384940 ERROR ironic.conductor.utils [None req-60791dc1-85c6-44c6-a3b7-a60e3242607d 4cb102fe974543b19c3e39916c7e61c1 00cfc520ffcb4533861e005a9a1e694f - - default default] Timed out after 1200 secs waiting for power on on node a357fdab-d8d5-4260-8e72-b444fa7c5cb9.: oslo_service.loopingcall.LoopingCallTimeOut: Looping call timed out after 1490.91 seconds 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils [None req-60791dc1-85c6-44c6-a3b7-a60e3242607d 4cb102fe974543b19c3e39916c7e61c1 00cfc520ffcb4533861e005a9a1e694f - - default default] Failed to prepare node a357fdab-d8d5-4260-8e72-b444fa7c5cb9 for cleaning: Failed to set node power state to power on.: ironic.common.exception.PowerStateFailure: Failed to set node power state to power on. 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils Traceback (most recent call last): 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/conductor/utils.py", line 183, in node_wait_for_power_state 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils return timer.start(initial_delay=1, timeout=retry_timeout).wait() 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/eventlet/event.py", line 125, in wait 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils result = hub.switch() 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/eventlet/hubs/hub.py", line 313, in switch 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils return self.greenlet.switch() 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/oslo_service/loopingcall.py", line 154, in _run_loop 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils idle = idle_for_func(result, self._elapsed(watch)) 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/oslo_service/loopingcall.py", line 349, in _idle_for 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils raise LoopingCallTimeOut( 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils oslo_service.loopingcall.LoopingCallTimeOut: Looping call timed out after 1490.91 seconds 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils oslo_service.loopingcall.LoopingCallTimeOut: Looping call timed out after 1490.91 seconds 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils During handling of the above exception, another exception occurred: 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils Traceback (most recent call last): 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/conductor/cleaning.py", line 91, in do_node_clean 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils prepare_result = task.driver.deploy.prepare_cleaning(task) 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic_lib/metrics.py", line 59, in wrapped 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils result = f(*args, **kwargs) 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/drivers/modules/agent_base.py", line 726, in prepare_cleaning 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils result = deploy_utils.prepare_inband_cleaning( 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/drivers/modules/deploy_utils.py", line 732, in prepare_inband_cleaning 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils manager_utils.node_power_action(task, states.REBOOT) 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/conductor/task_manager.py", line 153, in wrapper 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils return f(*args, **kwargs) 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/conductor/utils.py", line 341, in node_power_action 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils notify_utils.emit_power_set_notification( 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils self.force_reraise() 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils raise self.value 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/conductor/utils.py", line 329, in node_power_action 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils task.driver.power.reboot(task, timeout=timeout) 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/conductor/task_manager.py", line 153, in wrapper 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils return f(*args, **kwargs) 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/drivers/modules/redfish/power.py", line 166, in reboot 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils _set_power_state(task, system, next_state, timeout=timeout) 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/drivers/modules/redfish/power.py", line 68, in _set_power_state 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils cond_utils.node_wait_for_power_state(task, target_state, 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils File "/usr/lib/python3.9/site-packages/ironic/conductor/utils.py", line 189, in node_wait_for_power_state 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils raise exception.PowerStateFailure(pstate=new_state) 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils ironic.common.exception.PowerStateFailure: Failed to set node power state to power on. 2023-12-19 10:24:49.989 384940 ERROR ironic.conductor.utils 2023-12-19 10:24:49.991 384940 DEBUG ironic.conductor.utils [None req-60791dc1-85c6-44c6-a3b7-a60e3242607d 4cb102fe974543b19c3e39916c7e61c1 00cfc520ffcb4533861e005a9a1e694f - - default default] Node a357fdab-d8d5-4260-8e72-b444fa7c5cb9 is not fast-track-able because it has an error: Failed to change power state to 'power on' by 'rebooting': Failed to set node power state to power on. is_fast_track /usr/lib/python3.9/site-packages/ironic/conductor/utils.py:1146 ---------------------------------------------------------------- 富士通株式会社先端技術開発本部ソフトウェア開発統括部基盤ソフト開発部野口惇矢(Noguchi Junya) 外線：070-3052-0998 内線：72-6042-3844 mail：noguchi.junya(a)jp.fujitsu.com

3 2

[Trove][kolla] trove db instance failed
by jayesh chaudhari 22 Mar '24

22 Mar '24

Hi All, I have enabled trove in my kolla ansible yoga setup. But my trove database instance is getting stuck in build state and then eventually failed after some time with polling timeout error. I have created trove management network which is my vlan network, also my control plane and data plane traffic is segregated through different interfaces. Now when I am creating db instance in admin tenant, my openstack instance in service tenant which is getting created do not have any network. I have tested trove-guest-image manually which is working fine. Am I missing something here ? Please suggest Thanks, Jayesh

1 0