January 2022 - openstack-discuss - lists.openstack.org

[neutron] Bug deputy December 27
by Rodolfo Alonso Hernandez 04 Jan '22

04 Jan '22

Hello: These are the bugs opened during the last week: https://bugs.launchpad.net/neutron/+bug/1956034: "ovn load balancer health monitor cause mac address conflict". Unassigned. https://bugs.launchpad.net/neutron/+bug/1956035: "ovn load balancer member failover not working when accessed from floating ip". Unassigned. https://bugs.launchpad.net/neutron/+bug/1955799: "Not changing floatingip status while deleting instance that had floatingip assocciate (Showing ACTIVE)". Patch: https://review.opendev.org/c/openstack/neutron/+/822091 Regards.

1 0

[neutron] CI meeting agenda - 4.01.2022
by Slawek Kaplonski 04 Jan '22

04 Jan '22

Hi, It's just reminder that we will today have Neutron CI meeting. It will be at 3pm UTC time. Meeting will be on the #openstack-neutron channel and on jiitsi: https://meetpad.opendev.org/neutron-ci-meetings Agenda is in the etherpad https://etherpad.opendev.org/p/neutron-ci-meetings See You there :) -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

[nova] Getting away from cdrkit / genisoimage
by Thomas Goirand 04 Jan '22

04 Jan '22

Hi, Please see: https://bugs.debian.org/982241 It looks like cdrkit / genisoimage wont be available in the next Debian 12 (and therefore probably it will also be dropped in Ubuntu). As per the bug report: "I'm told xorriso and libburnia are alternatives and are alive and doing well." Would it be possible to switch to that? Cheers, Thomas Goirand (zigo)

2 1

cpu pinning
by open infra 04 Jan '22

04 Jan '22

3 7

[all][qa][triplo] Help need to maintain OpenStack health dashboard
by Ghanshyam Mann 04 Jan '22

04 Jan '22

Hello Everyone, In the QA meeting[1], we discussed the help needed to maintain the OpenStack health dashboard which is broken currently and the QA team does not have the JS developer and bandwidth to fix it. While discussing it meeting, we found that the TripleO team might be working on a similar dashboard for their CI results. If that is the case, can we collaborate on maintaining the existing dashboard? OpenStack health dashboard: https://opendev.org/openstack/openstack-health Repo: http://status.openstack.org/openstack-health/#/ [1] https://meetings.opendev.org/meetings/qa/2021/qa.2021-11-16-15.00.log.html#… -gmann

5 7

[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

[Diversity] D&I WG Meeting Cancellation and Poll Reminder
by Amy Marrich 02 Jan '22

02 Jan '22

Just a reminder that tomorrow's meeting is canceled and to participate in the Meeting Time and IRC vs Video Poll! https://doodle.com/poll/mnzxkauzwf2isssm?utm_source=poll&utm_medium=link Thanks, Amy (spotz)

1 0