March 2022 - openstack-discuss - lists.openstack.org

[ironic][tripleo][kayobe][tenks][vbmc] Do you also experience random issues with vbmc?
by Radosław Piliszek 07 Mar '22

07 Mar '22

Dear fellow upstream OpenStackers, I tagged the main projects that use vbmc intensively because I have a question regarding the stability of vbmc. I have been working on adding baremetal testing in Kolla Ansible using Tenks and thus also VirtualBMC. I am encountering random failures that I am at the moment unable to debug. It seems vbmc likes to reject the "chassis bootdev pxe" ipmitool command from time to time (the command is issued when trying to deploy a host). This seems permanent per case as ironic retries this call several times only to fail. The error message is "Error setting Chassis Boot Parameter 5". I can't see any trace in vbmc logs (with DEBUG enabled). Other ipmitool commands seem to work fine (like periodic power status). I was wondering if any of you also experienced this issue. I am providing a link to an excerpt from the logs. [1] It also shows a raw ipmitool command succeeding only to let the next one fail. [1] https://paste.ubuntu.com/p/MgHHpDvVGf/ -yoctozepto

2 2

[Triple0] Upgrade Error
by Lokendra Rathour 05 Mar '22

05 Mar '22

Hi Team, we are trying to upgrade Triple0 Train to Ussuri. Undercloud upgrade prepare is done successfully and when we are going for overcloud upgrade getting below error: * len(inspect.getargspec(type_).args) > 1)2022-02-23 16:49:50.959 187217 INFO tripleoclient.utils.utils [-] Running Ansible playbook: /usr/share/ansible/tripleo-playbooks/cli-update-params.yaml, Working directory: /tmp/tripleoj7rvp51m, Playbook directory: /usr/share/ansible/tripleo-playbooksPLAY [Update Parameters] *******************************************************2022-02-23 16:49:51.858966 | 5254007d-0040-f631-88e7-000000000008 | TASK | Check for required inputs2022-02-23 16:49:51.895961 | 5254007d-0040-f631-88e7-000000000008 | SKIPPED | Check for required inputs | localhost2022-02-23 16:49:51.897803 | 5254007d-0040-f631-88e7-000000000008 | TIMING | Check for required inputs | localhost | 0:00:00.096595 | 0.04s2022-02-23 16:49:51.901827 | 5254007d-0040-f631-88e7-000000000009 | TASK | Set parameters fact2022-02-23 16:49:51.949091 | 5254007d-0040-f631-88e7-000000000009 | OK | Set parameters fact | localhost2022-02-23 16:49:51.951583 | 5254007d-0040-f631-88e7-000000000009 | TIMING | Set parameters fact | localhost | 0:00:00.150375 | 0.05s2022-02-23 16:49:51.956146 | 5254007d-0040-f631-88e7-00000000000b | TASK | Update parameters2022-02-23 16:50:12.542028 | 5254007d-0040-f631-88e7-00000000000b | FATAL | Update parameters | localhost | error={"changed": false, "error": "Error validating environment for plan overcloud: ERROR: Property error: resources.InternalApiVirtualIP.properties: Unknown Property DnsName\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 891, in __call__\n request, **action_args)\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 964, in dispatch\n return method(*args, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/util.py\", line 56, in handle_stack_method\n return handler(controller, req, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/stacks.py\", line 633, in validate_template\n raise exc.HTTPBadRequest(result['Error'])\n", "msg": "Error updating parameters for plan overcloud: Error validating environment for plan overcloud: ERROR: Property error: resources.InternalApiVirtualIP.properties: Unknown Property DnsName\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 891, in __call__\n request, **action_args)\n File \"/usr/lib/python3.6/site-packages/heat/common/wsgi.py\", line 964, in dispatch\n return method(*args, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/util.py\", line 56, in handle_stack_method\n return handler(controller, req, **kwargs)\n File \"/usr/lib/python3.6/site-packages/heat/api/openstack/v1/stacks.py\", line 633, in validate_template\n raise exc.HTTPBadRequest(result['Error'])\n", "success": false}2022-02-23 16:50:12.544560 | 5254007d-0040-f631-88e7-00000000000b | TIMING | Update parameters | localhost | 0:00:20.743350 | 20.59s* Command used to run the overcloud upgrade prepare: *(undercloud) [stack@undercloud ~]$ cat upgrade_overcloud_prepare.shopenstack overcloud upgrade prepare --templates \ -r /home/stack/templates/roles_data.yaml \ -n /home/stack/templates/network_data.yaml \ -e /home/stack/templates/environment.yaml \ -e /home/stack/templates/environments/network-isolation.yaml \ -e /home/stack/templates/environments/network-environment.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-conductor.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-overcloud.yaml \ -e /home/stack/templates/ironic-config.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/templates/init-repo.yaml \ -e /home/stack/containers-prepare-parameter.yaml(undercloud) [stack@undercloud ~]$* *Document referred:*Upgrading to a Next Major Release — TripleO 3.0.0 documentation (openstack.org) <https://docs.openstack.org/project-deploy-guide/tripleo-docs/wallaby/post_d…> Any support here, please. -- ~ Lokendra skype: lokendrarathour

2 5

[tc][ptl] TC + Community Leaders interaction in Zed Virtual PTG
by Ghanshyam Mann 04 Mar '22

04 Mar '22

Hello Everyone, We had successful TC+Community leaders interaction sessions in the last PTG, and we will continue the same for Zed cycle PTG also. I have created the below etherpad with the draft agenda, If you as PTL or project representatives or SIG Chair and would like to attend this session, please add your name: - https://etherpad.opendev.org/p/tc-ptl-interaction-zed Also, I have created the doodle poll to select the best suitable time. It will be for two hours (single or two sessions) either on Monday or Tuesday. Please add your preference in the below doodle poll (including TC members): - https://doodle.com/poll/dcer6i3wk2b8eim3 -gmann

1 1

[release] Release countdown for week R-3, Mar 07 - 11
by Előd Illés 04 Mar '22

04 Mar '22

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, March 10th, 2022. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/yoga branch will be cut. This branch will track the Yoga release. Once stable/yoga has been created, the master branch will be ready to switch to Zed development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing Yoga plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/yoga branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/yoga branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be Zed) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any Yoga release so far. Finally, now is a good time to finalize release highlights if you have not already done so. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 10th, 2022 (R-3 week) Final RC deadline: March 24th, 2022 (R-1 week) Final Yoga release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) Előd Illés irc: elodilles

1 0

[requirements][release][rfe] sushy 4.1.1 for Yoga
by Iury Gregory 04 Mar '22

04 Mar '22

Hello Stackers, I would like to request a new release for sushy before creating the yoga branch, It contains some important fixes (e.g it will fix a problem when build sushy in Debian). The sushy lib is only used by ironic, so it shouldn't cause any problems updating the version in requirements. Thanks! -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

3 3

[Ironic] No suitable device was found for deployment
by 韩光宇 04 Mar '22

04 Mar '22

Dear all, I have a OpenStack Victoria environment, and tried to use ironic manage bare metal. But I got "- root device hints were not provided and all found block devices are smaller than 4294967296B." in deploy stage. 2022-02-09 17:57:56.492 3908982 ERROR ironic.drivers.modules.agent_base [-] Agent returned error for deploy step {'step': 'write_image', 'priority': 80, 'argsinfo': None, 'interface': 'deploy'} on node cc68c450-ce54-4e1c-be04-8b0a6169ef92 : No suitable device was found for deployment - root device hints were not provided and all found block devices are smaller than 4294967296B.. I used "openstack server create --flavor my-baremetal-flavor --nic net-id=$net_id --image $image testing" to deploy bare metal node. I download deploy images(ipa-centos8-master.kernel and ipa-centos8-master.initramfs) in https://tarballs.opendev.org/openstack/ironic-python-agent/dib/files/. The baremetal node info and flavor info as following: https://paste.opendev.org/show/bV7lgO6RkNQY6ZGPbT2e/ Ironic configure file as following: https://paste.opendev.org/show/bTgY9Kpn7KWqwQl73aEa/ Ironic-conductor log: https://paste.opendev.org/show/bFKZYlXmccxNxU8lEogk/ The log of ironic-python-agent in bare metal node: https://paste.opendev.org/show/btAuaMuV2IutV2Pa7YIa/ I see some old discussion about this, such as: https://bugzilla.redhat.com/show_bug.cgi?id=1312187. But those discussions took place a long time ago, not version V, and no solution was seen. Does anyone know how to solve this problem? I would appreciate any kind of guidance or help. Thank you, Han Guangyu

3 14

[nova][placement] Zed PTG preparation
by Sylvain Bauza 04 Mar '22

04 Mar '22

Hey folks, We have until Mar 11th [1]to communicate about our needs for the Zed PTG (I've already signed up our presence by the survey) .As you can see in [2], there are already projects that booked some timeslots. This time, I won't ask you to tell me over Doodle which times you can be around, but I'd rather propose you 3 options : Option A "The short one" : we ask for 3 days from Wednesday to Friday with 4 hours each (13UTC-17UTC) Option B "The week used": we ask for 4 days from Tuesday to Friday with 3 hours each (14UTC-17UTC) Option C "The largest one" : we ask for 4 days from Tuesday to Friday with 4 hours each (13UTC-17UTC) Option D "The Asian-nice one" : we ask for Wed to Friday with 3 hours each (14UTC-17UTC) but we also ask for Thursday with 2 hours (6UTC-8UTC) Please start to think about those options as we'll discuss this on next Tuesday meeting [3] and eventually we will vote on it. I also created a new etherpad for our PTG : https://etherpad.opendev.org/p/nova-zed-ptg If you want, you can start to collect some topics but also if you aren't able to attend next Nova meeting, you can also start to vote on the option above in there. Voila, that's it. Thanks and let's discuss it again on next meeting, -Sylvain [1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027051… [2] https://ethercalc.openstack.org/7yxdas7suqnd [3] https://meetings.opendev.org/#Nova_Team_Meeting

1 0

[neutron] Drivers meeting agenda - 04.03.2022.
by Lajos Katona 03 Mar '22

03 Mar '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. * Gratuitous ARPs are not sent during master transition: ( https://bugs.launchpad.net/neutron/+bug/1952907) ** For this one there are a few wip patches: ** https://review.opendev.org/c/openstack/neutron/+/821434 ** https://review.opendev.org/c/openstack/neutron/+/821433 ** https://review.opendev.org/c/openstack/neutron/+/712474 * On Demand agenda: (ralonsoh): https://bugs.launchpad.net/neutron/+bug/1962465. I want to discuss the scope of this bug and the possible fix. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

Openstack HPC storage suggestion
by Satish Patel 03 Mar '22

03 Mar '22

Folks, I built a 30 node HPC environment on openstack using mellanox infiniband nic for high speed MPI messaging. So far everything works. Now I am looking for a HPC PFS (parallel file system) similar to Luster which I can mount on all HPC vms to run MPI jobs. I was reading on google and saw some CERN videos and they are using Ceph (cephfs) for PFS. Also i was reading CephFS + Manila is a good choice for HPC on openstack design. Does anyone have any experience with HPC storage for Openstack? Please advice or share your experience :) Thanks in advance. ~S

4 4

[TripleO] Gate blocker for Centos 9 Wallaby
by Dariusz Smigiel 03 Mar '22

03 Mar '22

Currently TripleO gate is experiencing issues with building images [1] We're aware of the problem, and we're trying to resolve this issue. Please withhold from rechecking RDO Third Party CI. Thank you, Dariusz Smigiel (dasm) [1]: https://bugs.launchpad.net/tripleo/+bug/1962786

1 1