September 2022 - openstack-discuss

[ironic] Stable & Bugfix branch maintenance and retirement
by Jay Faulkner 29 Sep '22

29 Sep '22

Hi folks, I'm letting you all know it's my intention to, very soon, perform the following actions on all Ironic projects: 1) Perform a release for any maintained stable and bugfix branches (EM stable branches excluded by policy) 2) Retire all stable branches for releases prior to stable/train (For Ironic; this is queens, rocky, and stein -- I have not enumerated them yet for other projects). If you either have code you'd like to ensure gets in the stable release or want to step up and volunteer to maintain the older branches -- including backporting existing bugfixes that did not make it back that far and maintaining CI -- please let me know within the next couple of days. Thanks, Jay Faulkner OpenStack Ironic PTL OpenStack TC member

1 0

[neutron] Drivers meeting agenda -30.09.2022.
by Lajos Katona 29 Sep '22

29 Sep '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. We have the following RFE to discuss: * [RFE] Expose Open vSwitch other_config column in the API (#link https://bugs.launchpad.net/neutron/+bug/1990842 ) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[kolla][centos][rdo] NOTICE: OVS version mismatch between Wallaby and later
by Radosław Piliszek 29 Sep '22

29 Sep '22

Dears, This is a notice to users of OVS with Kolla with CentOS-Stream-8-based images or RDO directly. It seems that RDO Wallaby currently installs OVS 2.17 while later ones install OVS 2.15. The problem is that currently: *** Upgrades from Wallaby to Xena will cause OVS to misbehave and lose all network connectivity until host reboot. *** This is because downgrades of running OVS are not supported. We are investigating this issue, please stay tuned to this topic. The solution we believe to be the correct one now is to bump OVS to 2.17 also in later branches of RDO. Kind regards, Radek -yoctozepto

1 1

[Glance] Weekly Meeting Cancelled
by Pranali Deore 29 Sep '22

29 Sep '22

Hello, This week's upstream meeting is cancelled, since there is nothing on agenda for today. Thanks & Regards, Pranali Deore

1 0

[kolla][ssl] Deploy third-party SSL for HAProxy
by Satish Patel 29 Sep '22

29 Sep '22

Folks, I have GoDaddy SSL cert and trying to deploy with kolla but little big confused with this doc https://docs.openstack.org/kolla-ansible/latest/admin/tls.html I have a single interface for internal/external vip and try following config to deploy SSL/TLS for haproxy and other services. --- openstack_release: "wallaby" kolla_internal_vip_address: "10.73.0.180" kolla_external_vip_address: "{{ kolla_internal_vip_address }}" network_interface: "eth0" neutron_external_interface: "eth1" # TLS kolla_enable_tls_internal: "yes" kolla_certificates_dir: "/etc/kolla/certificates" kolla_internal_fqdn_cert: "{{ kolla_certificates_dir }}/my_company_cert.pem" When i run "kolla-ansible -i multinode certificates" command it deploy something but then i found it generated certificate itself (self-sign) in /etc/kolla/cacertificates directory and override my third-party cert When I tried in the browser https://foobar.com it didn't connect to 443 port that means it did not enable SSL. Am I missing something here?

2 8

(no subject)
by fereshteh loghmani 29 Sep '22

29 Sep '22

in kolla ansible (release: victoria) when i run command: " kolla-ansible -i ./multinode bootstrap-servers --limit compute1 " i receive this error: TASK [baremetal : Enable docker apt repository] * fatal: [R5DG1.cpaas.ir]: FAILED! => {"changed": false, "msg": "apt cache update failed"} could you please help me how could i fix this? ( my compute1 has the ubuntu20 )

2 1

[all][tc] Technical Committee next weekly meeting on 2022 Sept 29 at 1500 UTC
by Ghanshyam Mann 28 Sep '22

28 Sep '22

Hello Everyone, Below is the agenda for Tomorrow's TC meeting scheduled at 1500 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting * Roll call * Follow up on past action items * Gate health check ** Bare 'recheck' state *** https://etherpad.opendev.org/p/recheck-weekly-summary * 2023.1 cycle PTG Planning ** TC + Leaders interaction sessions *** https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 ** TC PTG etherpad *** https://etherpad.opendev.org/p/tc-2023-1-ptg ** Schedule 'operator hours' *** https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… * 2023.1 cycle Technical Election & Leaderless projects ** Leaderless projects *** https://etherpad.opendev.org/p/2023.1-leaderless ** TC Chair election * Open Reviews ** https://review.opendev.org/q/projects:openstack/governance+is:open -gmann

1 0

[cinder][outreachy] Internship proposal 💻
by Sofia Enriquez 28 Sep '22

28 Sep '22

Hello Argonauts, As discussed in Cinder Meeting two weeks ago[1], I've created the internship proposal Etherpad[2]. Please, feel free to add comments and in particular, if you have any suggestions on the benefits please add them. The deadline is this Friday. Thanks in advance, Cheers, Sofi [1] https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-09-21-14.00.l… [2] https://etherpad.opendev.org/p/outreachy-cinder-dec-2022-to-march-2023 -- 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

[kolla-ansible] Error while upgrading from xena to yoga
by wodel youchi 28 Sep '22

28 Sep '22

Hi, I am trying to upgrade from xena to yoga. I have created a test environment that resembles the production one using VMs. The deployment consists of 03 controllers and 03 compute/storage nodes. I am using Rokcy 8 as my base OS and I am using another VM as a deployer with a local registry. I followed the documentation here : https://docs.openstack.org/kolla-ansible/yoga/user/operating-kolla.html The precheks went well, but when deploying I got the following error : fatal: [ctrl02]: FAILED! => {"changed": true, "msg": "'Traceback (most > recent call last):\\n > File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line > 268, in _raise_for_status\\n > response.raise_for_status()\\n File > \"/usr/local/lib/python3.6/site-packages/requests/models.py\", line 960, > in raise_for_status\\n raise HTTPError(http_error_msg, response=self)\\n > requests.exceptions.HTTPError: 404 Client Error: Not Found for url: > http+docker://localhost/v1.41/images/create?tag=yoga& > fromImage=10.50.0.252%3A4000%2Fopenstack.kolla%2Fcentos-source-rabbitmq\\n\\nDuring > handling of the above exception, > another exception occurred:\\n\\nTraceback (most recent call last):\\n > File > \"/tmp/ansible_kolla_docker_payload_8hum8og4/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", > line 381, > in main\\n File > \"/tmp/ansible_kolla_docker_payload_8hum8og4/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", > > line 660, in recreate_or_restart_container\\n self.pull_image()\\n > File > \"/tmp/ansible_kolla_docker_payload_8hum8og4/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", > > line 451, in pull_image\\n repository=image, tag=tag, stream=True\\n > File \ > "/usr/local/lib/python3.6/site-packages/docker/api/image.py\", line 430, > in pull\\n self._raise_for_status(response)\\n > File \"/usr/local/lib/python3.6/site-packages/docker/api/client.py\", line > 270, in _raise_for_status\\n > raise create_api_error_from_http_exception(e)\\n File > \"/usr/local/lib/python3.6/site-packages/docker/errors.py\", > line 31, in create_api_error_from_http_exception\\n raise cls(e, > response=response, explanation=explanation)\\n > docker.errors.NotFound: 404 Client Error for > http+docker://localhost/v1.41/images/create?tag=yoga > &fromImage=10.50.0.252%3A4000%2Fopenstack.kolla%2Fcentos-source-rabbitmq: > Not Found > *(\"manifest for > 10.50.0.252:4000/openstack.kolla/centos-source-rabbitmq:yoga > <http://10.50.0.252:4000/openstack.kolla/centos-source-rabbitmq:yoga> not > found: manifest unknown: manifest unknown\")\\n'"}* > [deployer@deployer yoga]$ sudo docker images | grep yoga | grep rabbit quay.io/openstack.kolla/centos-source-rabbitmq yoga 4ea3207bfef3 33 hours ago 920MB 10.50.0.252:4000/openstack.kolla/centos-source-rabbitmq yoga 4ea3207bfef3 33 hours ago 920MB Any ideas? Regards.

2 2

[release][requirements][oslo][nova] How to fix a bug and release the fix in oslo.concurrency 4.5.x series
by Balazs Gibizer 28 Sep '22

28 Sep '22

Hi, So we have a bug[1] that was fixed in oslo.concurrency on master[2] and released as 5.0.1 and Zed is released with 5.0.1. The issue is present in stable/yoga as well. There we have oslo.concurrency upper constraint pinned to 4.5.0 [3]. 1) How can I backport [2] to the 4.5.x series of oslo.concurrency to release 4.5.2 with the fix? I don't see a branch that I could use for this. 2) If #1) is solved and 4.5.2 is released can I propose an upper constraint bump on stable/yoga from 4.5.0 to 4.5.2? 3) If #1) and #2) is done. Can I propose a minimum requirement bump in nova's requirements.txt from >= 4.5.0 to >= 4.5.2 on stable/yoga? Cheers, gibi [1] https://bugs.launchpad.net/nova/+bug/1988311 [2] https://review.opendev.org/c/openstack/oslo.concurrency/+/855714 [3] https://github.com/openstack/requirements/blob/e64217c9f9316675f57e14ff559b…

4 5