December 2021 - openstack-discuss

[tempest] Extending tempest for mixed-architecture stacks
by James LaBarre 03 Jan '22

03 Jan '22

Recently I had been running Tempest on my setup testing a mixed-architecture deployment (x86_64 ans ppc64le compute nodes at the same time). It seems that some of the migration and affinity tests will check if there's more than one Compute node before they run. However, it would seem that's as far as they check, without checking if they are in fact compatible or even of the same architecture. (my test cluster is very small, and normally includes two ppc64le Compute nodes, and sometimes one x86_64 Compute node. Currently one ppc64le machine is down for repair). Because the two compute nodes are different architectures, I am getting failures in various migration and affinity tests, maybe more if I tested a larger subset. Now granted my particular setup is a special case, but it does bring to mind some extensions that may be needed for Tempest in the future. I could see it being possible to have x86_64 and ARM mixed together in one stack, maybe even tossing in RISC-v someday. I'm thinking we need to start adding in extra test images, flavors, etc into the Tempest configurations (as in defining multiple options so that each architecture can have test images, etc assigned to it, rather than the current primary and alt image for just one architecture) Additionally, there should be testcases taking into account the architectures involved (such as seeing that an instance on one arch cannot be migrated to the other, as an example). I know this involves a bit of refactoring, I didn't know if it had even been considered yet. -- James LaBarre Software Engineer, OpenStack MultiArch Red Hat <https://www.redhat.com> jlabarre(a)redhat.com <mailto:jlabarre@redhat.com> <https://www.redhat.com>

3 2

[tc][all] Follow up pain point discussion
by Rico Lin 03 Jan '22

03 Jan '22

Dear all The pain point collection etherpad [1] seems to get good attention from teams. We plan to host a one-hour video meeting to keep the discussion going. Please fill in the doodle to select your preferred time if you can join us: https://doodle.com/poll/kur2mfywceerqcvh?utm_source=poll&utm_medium=link The discussion will be hosted in video format. Here are some items (but not limited to) I expect we will discuss and hopefully put some actions/efforts on. - General Pain point: RabbitMQ - General Pain point: OpenStackClient support - General project pain point discussion: How to encourage teams to work/reply on pain points. Meanwhile, we encourage all to check the etherpad and provide your feedback. Also if teams can help to answer questions/concerns on etherpad (like Nova team does) will be greatly appreciated. [1] https://etherpad.opendev.org/p/pain-point-elimination *Rico Lin*

7 11

[octavia] Management Network Issue
by Ammad Syed 03 Jan '22

03 Jan '22

Hi, I am using octavia 9.0. I have created a neutron vlan based management network of octavia. I am creating a loadbalancer with a subnet in the tenant network, its getting created successfully. Then added a listener and created a pool, both created successfully. Now a weird situation is happening. Now when I add a member in the pool, the management network interface get detached automatically from the AMPHORA instance and amphora keeps in PENDING_UPDATE state. I have created a dedicated service-project for octavia and management network and subnet resides there. Any advise how to fix it ? Ammad

2 2

[release] Release countdown for week R-12, Jan 03-07
by Előd Illés 31 Dec '21

31 Dec '21

Development Focus ----------------- Happy new year! The Yoga-2 milestone is next week, on January6th, 2022. Yoga-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/ <https://releases.openstack.org/yoga/schedule.html>yoga <https://releases.openstack.org/yoga/schedule.html>/schedule.html <https://releases.openstack.org/yoga/schedule.html>for details. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library that has not been otherwise released since milestone 1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. Next week is also the deadline to freeze the contents of the final release. All new 'Yoga' deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables <https://opendev.org/openstack/releases/src/branch/master/deliverables> and need to have done a release by milestone-2. Changes proposing missingdeliverables for inclusion in Yogahave been posted, so if you have one in your project team please update them with an actual release request before the milestone-2 deadline if you plan on including that deliverable in Yoga, or -1 if you need one more cycle to be ready. Upcoming Deadlines & Dates -------------------------- Yoga-2 Milestone:January6th, 2022 Előd Illés irc: elodilles

1 0

[cinder] proposing Simon Dodsley for cinder-specs-core
by Brian Rosmaita 31 Dec '21

31 Dec '21

As everyone is painfully aware, we have review bandwidth issues in the Cinder project. I propose to address this issue with respect to cinder specs, at least, by adding a contributor who is not currently a cinder-core as a member of the cinder-specs-core team. (Right now, the only members of cinder-specs-core are the cinder-core team.) Simon Dodsley (simondodsley on IRC) has been a cinder contributor for a long time, and has been especially active in PTGs and midcycle meetings over the past few cycles. He's done quality reviews, especially of specs, this cycle. As a vendor representative, he brings a useful perspective to reviews that affect drivers, as well as general deployment and usability issues. Additionally, given that the current core team has reviewing responsibilities spread over multiple repositories, having a person focused primarily on specs should help us to get more timely feedback for specs proposers. Finally, don't forget that it is thanks to Simon that the Cinder mascot finally has a name ("Argo"), which in turn has given the Cinder team the really cool name "The Argonauts". In the absence of objections, I'll add Simon to the cinder-specs-core team shortly after 1500 UTC on Friday 31 December. Please communicate any concerns to me before that time. cheers, brian

4 4

PTR records in Designate
by Albert Braden 30 Dec '21

30 Dec '21

We have hacked Designate to add PTR records and it is a mess. Every upgrade turns into a bug hunt. I'd like to advocate for going back to vanilla kolla-ansible but then we wouldn't have PTR records. How are other Designate users dealing with the PTR issue?

2 2

[neutron] Do I need to replace NetworkManager with network.service in centos8?
by 韩光宇 29 Dec '21

29 Dec '21

Dear all, I am deploing OpenStack Victoria. I want to ask a question. Do I need to replace NetworkManager with network-scripts in centos8? I saw that "OpenStack Networking does not work on systems that have the Network Manager service enabled" in past redhat documentation and some other places. But I don't see this in latest documentation of OpenStack community（ https://docs.openstack.org/install-guide/environment-packages-rdo.html）. And If NetworkManager is confit will OpenStack network, Do anyone know where I can see the reason of confit. I would appreciate any kind of guidance. Thanks, Han Guangyu. Past redhat documentation: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11…

2 1

[cinder] Bug deputy report for week of 12-29-2021
by Sofia Enriquez 29 Dec '21

29 Dec '21

No meeting today. This is a bug report from 12-22-2021 to 12-29-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1955670 "Unable to delete a group volume after transfer". Unassigned. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[TripleO] Unable to deploy Overcloud Machines
by Anirudh Gupta 28 Dec '21

28 Dec '21

Hi Team, I am trying to deploy TripleO Train with 3 controller and 1 Compute. For overcloud images, I have a registry server at undercloud only. I executed the following command to deploy overcloud openstack overcloud deploy --templates \ -r /home/stack/templates/roles_data.yaml \ -e /home/stack/templates/node-info.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/containers-prepare-parameter.yaml The command ran for around 1.5 hrs and initially stack got successfully created and after that for 45 mins, ansible tasks were getting executed. It then gave following error in overcloud-controller-0 2021-12-27 11:12:27,507 p=181 u=mistral n=ansible | 2021-12-27 11:12:27.506838 | 525400b1-b522-2a06-ea9d-00000000356f | OK | Debug output for task: Start containers for step 2 | overcloud-novacompute-0 | result={ "changed": false, "failed_when_result": false, "start_containers_outputs.stdout_lines | default([]) | union(start_containers_outputs.stderr_lines | default([]))": [ "f206c31a781641313aa4a0499c62475efc335de6faea785cd4e855dc32ebb571", "", "Info: Loading facts", "Notice: Compiled catalog for overcloud-novacompute-0.localdomain in environment production in 0.05 seconds", "Info: Applying configuration version '1640604309'", "Notice: /Stage[main]/Tripleo::Profile::Base::Neutron::Ovn_metadata_agent_wrappers/Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]/File[/var/lib/neutron/ovn_metadata_haproxy_wrapper]/ensure: defined content as '{md5}5bb050ca70c01981975efad9d8f81f2d'", "Info: Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]: Unscheduling all events on Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]", "Info: Creating state file /var/lib/puppet/state/state.yaml", "Notice: Applied catalog in 0.01 seconds", "Changes:", " Total: 1", "Events:", " Success: 1", "Resources:", " Changed: 1", " Out of sync: 1", " Skipped: 7", " Total: 8", "Time:", " File: 0.00", " Transaction evaluation: 0.01", " Catalog application: 0.01", " Config retrieval: 0.09", " Last run: 1640604309", " Total: 0.01", "Version:", " Config: 1640604309", " Puppet: 5.5.10", * "Error executing ['podman', 'container', 'exists', 'nova_compute_init_log']: returned 1", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=nova_compute_init_log', '--filter', 'label=config_id=tripleo_step2', '--format', '{{.Names}}']\" - retrying without config_id", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=nova_compute_init_log', '--format', '{{.Names}}']\"", "Error executing ['podman', 'container', 'exists', 'create_haproxy_wrapper']: returned 1", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=create_haproxy_wrapper', '--filter', 'label=config_id=tripleo_step2', '--format', '{{.Names}}']\" - retrying without config_id", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=create_haproxy_wrapper', '--format', '{{.Names}}']\""* ] } I am also attaching ansible.log file for more information. Note: On Centos 8, there is no docker, so I didn't pass docker-ha.yml Can someone please help in resolving my issue Regards Anirudh Gupta

2 9

[neutron] bug deputy report of week 2021-12-20
by Bence Romsics 27 Dec '21

27 Dec '21

Hi Team, We only had a few new bugs last week, here they are: High: * https://bugs.launchpad.net/neutron/+bug/1955478 Scenario test failed due to metadata service not available slaweq investigated this gate failure, but did not find enough information in the logs. * https://bugs.launchpad.net/neutron/+bug/1955546 [stable only] Logging service plugin expects wrong arguments in the callback function fixes mostly merged: https://review.opendev.org/q/I0003bd566dc769436ad1342351ad058394bd52da * https://bugs.launchpad.net/neutron/+bug/1955578 OVN transaction could not be completed due to a race condition proposed fix: https://review.opendev.org/c/openstack/neutron/+/821401 * https://bugs.launchpad.net/neutron/+bug/1955775 Error when l3-agent get filter id for ip proposed fix: https://review.opendev.org/c/openstack/neutron/+/822987 Medium: * https://bugs.launchpad.net/neutron/+bug/1955639 Performance of mariadb's neutron.agents table unassigned Incomplete: * https://bugs.launchpad.net/neutron/+bug/1955503 [ovn] OVN agents showing as dead until neutron services restarted If ovn folks have an intuition what may go wrong with agent caching, then please look at it, but we don't have reproduction steps, so marked as Incomplete. Other: * https://bugs.launchpad.net/neutron/+bug/1955765 Devstack - Can no longer enable qos with neutron-qos Now that we un-deprecated the legacy plugin what do we want to do with the new plugin? Possible discussion point for the next meeting. Cheers, Bence

1 0