December 2022 - openstack-discuss

[neutron] Bug deputy report for week of December 5th
by Brian Haley 12 Dec '22

12 Dec '22

Hi, I was Neutron bug deputy last week. Below is a short summary about the reported bugs. -Brian Critical bugs ------------- * https://bugs.launchpad.net/neutron/+bug/1999249 - neutron-tempest-plugin jobs timing out on nested-virt nodes - Needs owner Medium bugs ----------- * https://bugs.launchpad.net/neutron/+bug/1998749 - [L3][DVR][vlan] east-west traffic flooding on physical bridges - Needs owner * https://bugs.launchpad.net/neutron/+bug/1998751 - [L3][DVR][vlan] HA VRRP traffic flooding on physical bridges on compute nodes - Needs owner * https://bugs.launchpad.net/neutron/+bug/1998952 - The static route removes the local route from qrouter-namespace - Adding/removing route same as attached interface subnet causes issue - Possible user error, the neutron API will let you "break" things - https://bugzilla.redhat.com/show_bug.cgi?id=1836870 has link to note - Needs discussion/owner * https://bugs.launchpad.net/neutron/+bug/1999154 - ovs/ovn source deployment broken with ovs_branch=master - https://review.opendev.org/c/openstack/neutron/+/867004 Low bugs -------- * https://bugs.launchpad.net/neutron/+bug/1998833 - [OVN] "MetadataAgentOvnSbIdl" should implement "post_connect" method - https://review.opendev.org/c/openstack/neutron/+/866601 Misc bugs --------- * https://bugs.launchpad.net/neutron/+bug/1999170 - Package names missing in neutron openvswitch setup guide - Added note that this information is in the install guide, closed * https://bugs.launchpad.net/neutron/+bug/1999209 - [ovn]dnat_adn_snat will not changed if updated fixed_ips of internal port - Asked for more information * https://bugs.launchpad.net/neutron/+bug/1999238 * https://bugs.launchpad.net/neutron/+bug/1999239 * https://bugs.launchpad.net/neutron/+bug/1999240 - Functional test failures - Related to https://review.opendev.org/c/openstack/neutron/+/867075

1 0

[openstack-ansible] Environment variable overflow on Ubuntu 20,04
by Taltavull Jean-François 12 Dec '22

12 Dec '22

Hello, The 'lxc_container_create' role appends the content of the 'global_environment_variables' OSA variable to '/etc/environment', which is used by the library 'libpam'. On Ubuntu 20.04 and 'libpam-runtime' library version 1.3.1, this works fine unless one of the environment variables content size exceeds 1024 char. In this case, the variable content is truncated. In our OpenStack deployment, this is the variable 'no_proxy' that overflows. This limit has been raised to 8192 with 'libpam-runtime' version 1.4 but there is no backport available in Ubuntu 20.04 repositories. So what would you think of the following workaround: instead of using '/etc/environment' to store the global variables, the role would create a shell script in '/etc/profile.d' thus avoiding the variable truncation issue related to the 'libpam' library ? This works on Ubuntu, Debian and CentOS hosts and containers. Cheers, JF

2 2

[Image Encryption] No meetings until next year
by Josephine Seifert 12 Dec '22

12 Dec '22

Hi, due to an injury and upcoming vacation, the next meeting for the image encrpyption team will be on Monday the 9th of Jannuary. greetings and happy holidays Luzi

2 1

Kolla-ansible [nova | Ensure RabbitMQ users exist] task error
by A Monster 12 Dec '22

12 Dec '22

I'm trying to deploy openstack xena on centos stream 8 on 2 controller nodes, 8 compute and a storage cluster, using kolla-ansible but I keep getting the following error, any workaround I could do to avoid this problem ? thank you. TASK [service-rabbitmq : nova | Ensure RabbitMQ users exist] ******************************************* skipping: [Controller-02] => (item=None) skipping: [Controller-02] FAILED - RETRYING: nova | Ensure RabbitMQ users exist (5 retries left). FAILED - RETRYING: nova | Ensure RabbitMQ users exist (4 retries left). FAILED - RETRYING: nova | Ensure RabbitMQ users exist (3 retries left). FAILED - RETRYING: nova | Ensure RabbitMQ users exist (2 retries left). FAILED - RETRYING: nova | Ensure RabbitMQ users exist (1 retries left). failed: [Controller-01 -> Controller-01] (item=None) => {"attempts": 5, "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false} fatal: [Controller-01 -> {{ service_rabbitmq_delegate_host }}]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}

2 1

auto switch of glance-api containers to other controllers
by pradeep 12 Dec '22

12 Dec '22

Hello All, I understand that glance-api container run only one controller always. I have tried to check if the glance-api container to switch over to the next available controller by means of rebooting and stopping the containers, but nothing happened. Is there a way to make sure that glance-api container switches to other controllers if controller 1 is not available. Thanks for you help Regards Pradeep

3 4

[ops] Migration from CentOS streams to Ubuntu and fast forward updates
by Massimo Sgaravatto 12 Dec '22

12 Dec '22

Dear all Dear all We are now running an OpenStack deployment: Yoga on CentOS8Stream. We are now thinking about a possible migration to Ubuntu for several reasons in particular: a- 5 years support for both the Operating System and OpenStack (considering LTS releases) b- Possibility do do a clean update between two Ubuntu LTS releases c- Easier procedure (also because of b) for fast forward updates (this is what we use to do) Considering the latter item, my understanding is that an update from Ubuntu 20.04 Ussuri to Ubuntu 22.04 Yoga could be done in the following way (we have two controller nodes and n compute nodes): - Update of first controller node from Ubuntu 20.04 Ussuri to Ubuntu 20.04 Victoria (update OpenStack packages + dbsync) - Update of first controller node from Ubuntu 20.04 Victoria to Ubuntu 20.04 Wallaby (update OpenStack packages + dbsync) - Update of first controller node from Ubuntu 20.04 Wallaby to Ubuntu 20.04 Xena (update OpenStack packages + dbsync) - Update of first controller node from Ubuntu 20.04 Xena to Ubuntu 20.04 Yoga (update OpenStack packages + dbsync) - Update of first controller node from Ubuntu 20.04 Yoga to Ubuntu 22.04 Yoga (update Ubuntu packages) - Update of second controller node from Ubuntu 20.04 Ussuri to Ubuntu 22.04 Yoga (update OpenStack and Ubuntu packages) - Update of the compute nodes from Ubuntu 20.04 Ussuri to Ubuntu 22.04 Yoga (update OpenStack and Ubuntu packages) We would do the same when migrating from Ubuntu 22.04 Yoga to Ubuntu 24.04 and the OpenStack xyz release (where xyz is the LTS release used in Ubuntu 24.04) Is this supposed to work or am I missing something ? If we decide to migrate to Ubuntu, the first step would be the reinstallation with Ubuntu 22.04/Yoga of each node currently running CentOS8 stream/Yoga. I suppose there are no problems having in the same OpenStack installation nodes running the same Openstack version but different operating systems, or am I wrong ? Thanks, Massimo

4 8

[dev][infra][qa][tact-sig] Tox 4.0.0 breaking changes
by Jeremy Stanley 11 Dec '22

11 Dec '22

Tox 4.0.0, a major rewrite, just appeared on PyPI in the past couple of hours, so jobs are breaking right and left. We're going to try pinning to latest 3.x in zuul-jobs for the near term while we work through some of the more obvious issues with it, but until then lots of tox-based Zuul jobs are going to be broken. I'll follow up to this thread once we think things should be stabilized and we can start trying to pick through what's going to need fixing for the new tox version. -- Jeremy Stanley

4 12

openstack 504 Gateway
by f.loghmani 11 Dec '22

11 Dec '22

hello I use Kolla ansible multi-region. in one of my regions that is not keystone and horizon on it, sometimes I receive the error Gateway Timeout. how could I solve this problem? (in the same time I could open other region panels and it works correctly) thanks in advance. Gateway Timeout The gateway did not receive a timely response from the upstream server or application

1 0

[Magnum] Technology and Ubuntu Driver.
by Nguyễn Hữu Khôi 11 Dec '22

11 Dec '22

Hello guys, Can you tell me which tools Magnum used to build the k8s cluster. I do a lot of research but I still have not figured it out. And one more thing, Why it does not support Ubuntu Distro? Thank you. Nguyen Huu Khoi

3 5

Re: [cinder] Problem with restoring purestorage volume backup
by Ришат Азизов 10 Dec '22

10 Dec '22

Hello, Thanks. We use cinder 18.2.0-1 Wallaby. Can we use this patch? Or does it need to be improved? сб, 10 дек. 2022 г. в 17:54, Ришат Азизов <rishat.azizov(a)gmail.com>: > Hello, > > Thanks. We use cinder 18.2.0-1 Wallaby. Can we use this patch? Or does it > need to be improved? > > ср, 26 окт. 2022 г. в 23:12, Sofia Enriquez <senrique(a)redhat.com>: > >> Hello, >> This is a major bug in Cinder that has been reported. Please check >> https://launchpad.net/bugs/1895035. >> The bug has a fix proposed to master to haven't merged yet [2]. >> I'll mention it again in next week's Cinder meeting. >> Regards, >> Sofia >> [2] https://review.opendev.org/c/openstack/cinder/+/750782 >> >> On Wed, Oct 26, 2022 at 9:45 AM Ришат Азизов <rishat.azizov(a)gmail.com> >> wrote: >> >>> Hello! >>> >>> We have a problem with cinder-backup with cephbackup driver and volume >>> on purestorage. When backing up purestorage volume with cinder-backup with >>> cephbackup driver it creates in ceph pool and everything is ok. But >>> when we try to restore the backup, it is not restored with an error >>> "rbd.ImageNotFound" in the screenshot attached to this email. This happens >>> because the original image is not in rbd, it is in purestorage. It is >>> not clear why the cinder is trying to look for a disk in the ceph. Could >>> you please help with this? >>> >>> Thanks. Regards. >>> >> >> >> -- >> >> 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> >> >>

2 1