- openstack-discuss - lists.openstack.org

[cinder] Bug Report from 12-21-2022
by Sofia Enriquez 21 Dec '22

21 Dec '22

This is a bug report from 12-14-2022 to 12-21-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/1999706 "Cinder fails to automatically map availability zones to volume types." Unassigned. Medium - https://bugs.launchpad.net/cinder/+bug/1999766 "Retype VM root Volume Cause VM failed to boot." Unassigned. Cheers, Sofia -- 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

Magnum private docker registry (insecure_registry) not working?
by Oliver Weinmann 21 Dec '22

21 Dec '22

Hi,I can't seem to get magnum (k8s) to accept my private docker registry. I wanted to have a central registry so not all hosts pull the images during deployment.For this I configured a registry:v2 docker container, pulled the images and pushed them to the local registry and added the following label to my k8s template:container_infra_prefix=172.28.7.140:4000/At first this seems to be working fine and when deploying a new k8s cluster using magnum I can see that it pulls the heat-container-agent image from my local registry:[core@k8s-admin-test-local-reg-6c4hx7gxbdhr-master-0 ~]$ sudo podman ps -aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES2d08559b9cdc 172.28.7.140:4000/heat-container-agent:wallaby-stable-1 /usr/bin/start-he... 1 second ago Up 1 second ago heat-container-agentBut then it fails to pull the next container:tail -f /var/log/heat-config/heat-config-script/64d35aad-5453-4da4-97c7-45abb640fc90-k8s-admin-test-local-reg-6c4hx7gxbdhr-kube_masters-h3wbcqgm6qv4-0-sfagopiu52se-master_config-2f5lhvr32z7j.logWARNING Attempt 8: Trying to install kubectl. Sleeping 5s+ ssh -F /srv/magnum/.ssh/config root@localhost '/usr/bin/podman run --entrypoint /bin/bash --name install-kubectl --net host --privileged --rm --user root --volume /srv/magnum/bin:/host/srv/magnum/bin 172.28.7.140:4000/hyperkube:v1.23.3-rancher1 -c '\''cp /usr/local/bin/kubectl /host/srv/magnum/bin/kubectl'\'''Trying to pull 172.28.7.140:4000/hyperkube:v1.23.3-rancher1...Error: initializing source docker://172.28.7.140:4000/hyperkube:v1.23.3-rancher1: pinging container registry 172.28.7.140:4000: Get "https://172.28.7.140:4000/v2/": http: server gave HTTP response to HTTPS clientI don't know why but there is no /etc/docker/daemon.json and the /etc/sysconfig/docker also doesn'T contain the line for my insecure registry:root@k8s-admin-test-local-reg-6c4hx7gxbdhr-master-0 ~]# cat /etc/sysconfig/docker# /etc/sysconfig/docker# Modify these options if you want to change the way the docker daemon runsOPTIONS="--selinux-enabled \ --log-driver=journald \ --live-restore \ --default-ulimit nofile=1024:1024 \ --init-path /usr/libexec/docker/docker-init \ --userland-proxy-path /usr/libexec/docker/docker-proxy \"As soon as I manually add my insecure registry here it works just fine. I looked at the magnum code and there is indeed some lines that should actually handle this, but it doesn't seem to be working. What is also weird is that while there is the Option in the Horizon WebUI to set an insecure registry, the openstack coe command doesn't offer this.Best Regards,Oliver

1 1

[kolla] Cancelling meetings on 21 and 28 Dec
by Michał Nasiadka 21 Dec '22

21 Dec '22

Hello Koalas, Cancelling this and next weekly meeting due to Christmas/New Year period. See you next year! Best regards, Michal

1 0

horizon policy
by Parsa Aminian 21 Dec '22

21 Dec '22

Hello is it possible to prevent access to delete instance on horizon for some users ? I want to access only admin user to delete instances from dashboard

1 0

Instance console works only if opened from one of the deployment nodes
by A Monster 21 Dec '22

21 Dec '22

I've deployed openstack yoga using kolla ansible, in three controller nodes, a storage cluster and multiple compute nodes. The deployment included using haproxy, keepalived and hacluster. everything seems to work fine, I can launch instances and networking is doing great, however I found out a problem that I didn't get in all the deployment tests that i've run before. I've combien openstack networks under the same network 10.10.10.0/24 and used the same ip address for both : *kolla_internal_vip_address* and *kolla_external_vip_interface *which is 10.10.10.254, and used an ip route to access to the openstack cluster from an external pc > ip route add 10.10.10.0/24 via 192.168.129.29 dev eth0 where *192.168.129.29* is the address of one of my controllers, however when I try to login to the horizon dashboard using *10.10.10.254 *i don't get a response from the web page, and when I log to the dashboard using the ip address of one of my controller nodes, I cannot use the instance console since it is under the ip address of 10.10.10.254 which is assigned to both *kolla_internal_vip_address* and *kolla_external_vip_interface.* although i can ping 10.10.10.254 from the external network using ip route.

1 0

[all][tc] Technical Committee next weekly meeting on 2022 Dec 21 at 1600 UTC
by Ghanshyam Mann 20 Dec '22

20 Dec '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2022 Dec 21, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Dec 20 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[horizon] Cancelling next three weekly meetings
by vishal manchanda 20 Dec '22

20 Dec '22

Hello Team, As agreed, during the last weekly meeting, we are canceling our weekly meeting on 21st, 28th December and 4th January. The next weekly meeting will be on 11th January. Happy holidays and a happy new year in advance! Thanks & Regards, Vishal Manchanda

1 0

[neutron] Bug deputy report for week of December 12th
by Rodolfo Alonso Hernandez 20 Dec '22

20 Dec '22

Hello Neutrinos: This is the bug report from last week. * Critical: ** https://bugs.launchpad.net/neutron/+bug/2000150: "Fullstack dhcp test test_multiple_agents_for_network is failing intermittently". *Not assigned* * High: ** https://bugs.launchpad.net/neutron/+bug/1999558: "tox4 is breaking Neutron CI (most of the jobs)". To be discussed during the weekly Neutron meeting. ** https://bugs.launchpad.net/neutron/+bug/2000071: "[ovn-octavia-provider] Do not make the status of a newly HM conditional on the status of existing members". Patch: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/868092 * Medium: ** https://bugs.launchpad.net/neutron/+bug/1999392: "Some events which are supposed to be run AFTER changes are committed are performed BEFORE commit". Assigned ** https://bugs.launchpad.net/neutron/+bug/1999678: "Static route can get stuck in the router snat namespace". Patch: https://review.opendev.org/c/openstack/neutron/+/867678 ** https://bugs.launchpad.net/neutron/+bug/1999774: "SDK: Neutron stadiums use python bindings from python-neutronclient which will be deprecated". This bug is a container for any patch on any project deprecating "python-neutronclient". ** https://bugs.launchpad.net/neutron/+bug/1999813: "[ovn-octavia-provider] when a HM is created/deleted the listener remains in PENDING_UPDATE". Patch: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/867974. ** https://bugs.launchpad.net/neutron/+bug/2000078: "neutron-remove-duplicated-port-bindings doesn't remove binding_levels". Assigned/ * Low ** https://bugs.launchpad.net/neutron/+bug/1999390: "TypeError raised in neutron-dhcp-agent due to missing argument in clean_devices method". *Not assigned.* ** https://bugs.launchpad.net/neutron/+bug/1999391: "Attribute error in neutron-ovs-agent".* Not assigned.* * Incomplete: ** https://bugs.launchpad.net/neutron/+bug/1999400: "neutron-metadata-agent does not sometimes provide instance-id". The issue seems to be an error during the cloud-init route assignment. Must be confirmed first. ** https://bugs.launchpad.net/neutron/+bug/1999540: "Tempest test test_two_vms_fips failed due to port binding on instance failing". Missing logs (not accessible). ** https://bugs.launchpad.net/neutron/+bug/1999677: "Defunct nodes are reported as happy in network agent list". This issue is already solved in newer versions (latest Ussuri release 16.4.2). Also newer releases allow the removal of the OVN agents using the CLI. Regards.

1 0

[Openstack Heat] - Problems to find right Heat syntax to declare static route in a router template
by ddorra＠t-online.de 20 Dec '22

20 Dec '22

Hi, I want extend my router HOT template by adding a static route. In the Openstack cli this would be openstack router add route --route destination='1.2.3.4/17',gateway='10.0.0.66' myrouter >From the OS::Neutron::Router resource description I guess this belongs into the value_specs section as a map, but all my attempts failed, e.g. router1: type: 'OS::Neutron::Router' properties: external_gateway_info: network: provider name: myrouter value_specs: route: destination: '0.0.0.0/0' gateway: '10.0.0.62' Can somebody help me with the correct syntax? Thanks & best regards, Dieter

2 1

OpenStack Release Name Voting Now Open!
by Erin Disney 19 Dec '22

19 Dec '22

Hey everyone- It’s that time again to vote for the next OpenStack release name! Here are the finalists: 1. Bandicoot 2. Basalt 3. Bobcat 4. Boomerang Please submit your vote by January 3rd at 11:59pm PT (January 4th at 7:59 UTC). https://civs1.civs.us/cgi-bin/vote.pl?id=E_9c7f7a20a8871b09&akey=5b974247f9… <https://civs1.civs.us/cgi-bin/vote.pl?id=E_9c7f7a20a8871b09&akey=5b974247f9…> Happy voting! Thanks, Erin

2 1

Kolla-ansible openstack deployment with High Availability
by A Monster 18 Dec '22

18 Dec '22

Do I need to deploy and configure PaceMaker and HAproxy or something similar in order to get a HA kolla-ansible openstack deployment? or is it something done automatically? If so, what are the steps I should be taking?

3 2

[cinder] Extending specs deadline to 23rd December
by Rajat Dhasmana 16 Dec '22

16 Dec '22

Hello Argonauts, As per the schedule[1], cinder spec deadline was 16th December, 2022. However, due to unavailability of some core members, less review bandwidth throughout the week (including me) and other factors like bringing cinderlib to a release-able state, we couldn't get the sufficient reviews done and hence will be extending the deadline for all the open specs proposed for 2023.1 (Antelope) release. The new deadline for cinder specs will be 23rd December, 2022. Please make sure your specs are updated and in a reviewable state. [1] https://releases.openstack.org/antelope/schedule.html#a-cinder-spec-freeze Thanks Rajat Dhasmana

1 0

[all][TC] Bare rechecks stats week of 25.07
by Slawek Kaplonski 16 Dec '22

16 Dec '22

Hi, Here are fresh data about bare rechecks. +--------------------+---------------+--------------+-------------------+ | Team | Bare rechecks | All Rechecks | Bare rechecks [%] | +--------------------+---------------+--------------+-------------------+ | requirements | 2 | 2 | 100.0 | | keystone | 1 | 1 | 100.0 | | OpenStackSDK | 3 | 3 | 100.0 | | tacker | 3 | 3 | 100.0 | | freezer | 1 | 1 | 100.0 | | rally | 1 | 1 | 100.0 | | OpenStack-Helm | 14 | 15 | 93.33 | | cinder | 6 | 7 | 85.71 | | kolla | 20 | 25 | 80.0 | | neutron | 4 | 5 | 80.0 | | Puppet OpenStack | 10 | 13 | 76.92 | | OpenStack Charms | 3 | 6 | 50.0 | | nova | 11 | 22 | 50.0 | | tripleo | 8 | 19 | 42.11 | | ironic | 1 | 3 | 33.33 | | Quality Assurance | 1 | 3 | 33.33 | | octavia | 0 | 1 | 0.0 | | OpenStackAnsible | 0 | 1 | 0.0 | | designate | 0 | 1 | 0.0 | | Release Management | 0 | 1 | 0.0 | | horizon | 0 | 1 | 0.0 | +--------------------+---------------+--------------+-------------------+ Those data should be more accurate as my script now counts only comments from last 7 days, not all comments from patches updated in last 7 days. Reminder: "bare rechecks" are recheck comments without any reason given. If You need to do recheck for patch due to failed job(s), please first check such failed job and try to identify what was the issue there. Maybe there is already opened bug for that or maybe You can open new one and add it as explanation in the recheck comment. Or maybe it was some infra issue, in such case short explanation in the comment would also be enough. -- Slawek Kaplonski Principal Software Engineer Red Hat

6 10

[all][tc] What's happening in Technical Committee: summary 2022 Dec 16: Reading: 5 min
by Ghanshyam Mann 16 Dec '22

16 Dec '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Dec 14. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-14-16.00.log.html * Next TC weekly meeting will be on Dec 21 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Dec 20. 2. What we completed this week: ========================= * The technical elections dates for next cycle is finalized[2], please plan your nominations for open leaderships roles accordingly. 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[3]. Open Reviews ----------------- * Three open reviews for ongoing activities[4]. IMPORTANT: Tox 4 failure and time to fix them -------------------------------------------------------- You might know about Tox 4 failure and currently it is capped as <4 in ensure-tox role. This is going to be uncapped on Dec 21[5] and you might see tox based unit/functional tests job (or any job using ensure-role except devstack based) will start failing. Please plan the testing and fix accordingly. Calling out here as holiday seasons or fixing it in early cycle will help to plan the smooth development cycle and release. Change in Inactive project timeline ----------------------------------------- The proposal for this is under review[6] and positive response so far. Mistral release and more maintainers ------------------------------------------- avanzagh joined TC meeting and updates us that new maintainers from OVHCloud have been added as Core members to help maintaining Mistral. And we also discussed and agreed to continue Mistral in DPL model for this cycle. As next step, avanzagh will discuss the required work to release Mistral or what are the expectations from the release team to consider it as release item. This seems like good progress. We will keep monitor the situation until proposal for Mistral release deprecation is closed[7]. Renovate translation SIG i18 ---------------------------------- * No updates this week and we will track it in TC tracker and update on ML if there is any update. Project updates ------------------- * Add Cinder Huawei charm[8] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[9]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [10] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://governance.openstack.org/election/ [3] https://etherpad.opendev.org/p/tc-2023.1-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/03144… [6] https://review.opendev.org/c/openstack/governance/+/867062 [7] https://review.opendev.org/c/openstack/governance/+/866562 [8] https://review.opendev.org/c/openstack/governance/+/867588 [9] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [10] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[keystone] Holiday Meeting Schedule
by Dave Wilde 16 Dec '22

16 Dec '22

Hello, For the upcoming holidays I’m setting the Keystone meeting schedule as follows: 2022: - 20-Dec: Keystone weekly meeting on IRC - 23-Dec: Keystone Reviewathon on Google Meet - 27-Dec: Cancelled - Keystone weekly meeting - 30-Dec: Cancelled - Keystone Reviewathon on Google Meet 2023: - 03-Jan: Keystone weekly meeting on IRC as usual - 06-Jan: Keystone Reviewathon on Google Meet As always please let me know if you need anything. I hope you have a nice holiday and safe and happy new year! Thanks, /Dave

1 0

Could I deploy openstack in openstack instance
by 韩光宇 15 Dec '22

15 Dec '22

Hello, Could I deploy openstack in openstack instance? When I use a instance just with one network interface. After ip move to brq(using linuxbridge) or br-ex(uring openvswitch), the instance lost connection.  Does anyone know how to set it up? Or suggest me some documentation. I would appreciate any kind of guidance or help. Thank you.

2 1

Re: auto switch of glance-api containers to other controllers
by pradeep 15 Dec '22

15 Dec '22

Hello All Any help is highly appreciated. On Thu, 15 Dec 2022 at 01:41, pradeep <pradeep8985(a)gmail.com> wrote: > Hi Danny, > > Yes, i did, All of them are mounted in all the 3 controllers as well. > > # cat /etc/kolla/globals.yml | egrep > "glance_backend_file|glance_file_datadir_volume" > #glance_backend_file: "yes" > glance_file_datadir_volume: "/glanceimages" > > root@ctrl-1:~# df -h /glanceimages/ > Filesystem Size Used Avail Use% Mounted on > <IPaddress>:/Openstack_fileshare1 150G 888M 150G 1% /glanceimages > > root@ctrl-2:~# df -h /glanceimages/ > Filesystem Size Used Avail Use% Mounted on > <IPaddress>:/Openstack_fileshare1 150G 888M 150G 1% /glanceimages > > root@ctrl-3:~# df -h /glanceimages/ > Filesystem Size Used Avail Use% Mounted on > <IPaddress>:/Openstack_fileshare1 150G 888M 150G 1% /glanceimages > > > On Wed, 14 Dec 2022 at 17:54, Danny Webb <Danny.Webb(a)thehutgroup.com> > wrote: > >> did you change the glance_file_datadir_volume variable? that is >> required for kolla to deploy multiples: >> >> >> https://github.com/openstack/kolla-ansible/blob/ae3de342e48bc4293564a3b532a… >> >> ------------------------------ >> *From:* pradeep <pradeep8985(a)gmail.com> >> *Sent:* 14 December 2022 10:19 >> *To:* Danny Webb <Danny.Webb(a)thehutgroup.com> >> *Subject:* Re: auto switch of glance-api containers to other controllers >> >> >> * CAUTION: This email originates from outside THG * >> ------------------------------ >> Thanks Danny, All >> >> I have found the glance-api containers not deployed in control2 and >> control3 hosts although I have used NFS as my backend and share is enabled >> in all my controllers. >> >> I have tried to deploy the containers in control 2 and 3 as below but see >> some failures. I hope I am not using the wrong command. Am i missing >> something? Please let me know. >> >> *Command used* >> kolla-ansible -i multinode deploy --tags "glance" --limit >> control02.lab,control03.lab -vv >> >> *Errors in deployment* >> >> RUNNING HANDLER [glance : Restart glance-api container] >> ********************************************************************************* >> task path: >> /root/kolla-ansible/venv/share/kolla-ansible/ansible/roles/glance/handlers/main.yml:2 >> >> fatal: [control02.lab]: FAILED! => {"changed": true, "msg": "'Traceback >> (most recent call last):\\n File >> \"/usr/local/lib/python3.8/dist-packages/docker/api/client.py\", line 268, >> in _raise_for_status\\n response.raise_for_status()\\n File >> \"/usr/lib/python3/dist-packages/requests/models.py\", line 940, in >> raise_for_status\\n raise HTTPError(http_error_msg, >> response=self)\\nrequests.exceptions.HTTPError: 500 Server Error: Internal >> Server Error for url: >> http+docker://localhost/v1.41/images/create?tag=yoga&fromImage=quay.io%2Fopenstack.kolla%2Fubuntu-source-glance-api\\n\\nDuring >> handling of the above exception, another exception occurred:\\n\\nTraceback >> (most recent call last):\\n File >> \"/tmp/ansible_kolla_docker_payload_iltg71bi/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", >> line 381, in main\\n File >> \"/tmp/ansible_kolla_docker_payload_iltg71bi/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 651, in recreate_or_restart_container\\n self.start_container()\\n >> File >> \"/tmp/ansible_kolla_docker_payload_iltg71bi/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 669, in start_container\\n self.pull_image()\\n File >> \"/tmp/ansible_kolla_docker_payload_iltg71bi/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 450, in pull_image\\n json.loads(line.strip().decode(\\'utf-8\\')) >> for line in self.dc.pull(\\n File >> \"/usr/local/lib/python3.8/dist-packages/docker/api/image.py\", line 430, >> in pull\\n self._raise_for_status(response)\\n File >> \"/usr/local/lib/python3.8/dist-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.8/dist-packages/docker/errors.py\", line 31, >> in create_api_error_from_http_exception\\n raise cls(e, response=response, >> explanation=explanation)\\ndocker.errors.APIError: 500 Server Error for >> http+docker://localhost/v1.41/images/create?tag=yoga&fromImage=quay.io%2Fopenstack.kolla%2Fubuntu-source-glance-api: >> Internal Server Error (\"Get \"https://quay.io/v2/\ >> <https://quay.io/v2//>": net/http: request canceled while waiting for >> connection (Client.Timeout exceeded while awaiting headers)\")\\n'"} >> fatal: [control03.lab]: FAILED! => {"changed": true, "msg": "'Traceback >> (most recent call last):\\n File >> \"/usr/local/lib/python3.8/dist-packages/docker/api/client.py\", line 268, >> in _raise_for_status\\n response.raise_for_status()\\n File >> \"/usr/lib/python3/dist-packages/requests/models.py\", line 940, in >> raise_for_status\\n raise HTTPError(http_error_msg, >> response=self)\\nrequests.exceptions.HTTPError: 500 Server Error: Internal >> Server Error for url: >> http+docker://localhost/v1.41/images/create?tag=yoga&fromImage=quay.io%2Fopenstack.kolla%2Fubuntu-source-glance-api\\n\\nDuring >> handling of the above exception, another exception occurred:\\n\\nTraceback >> (most recent call last):\\n File >> \"/tmp/ansible_kolla_docker_payload_kkez0k31/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", >> line 381, in main\\n File >> \"/tmp/ansible_kolla_docker_payload_kkez0k31/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 651, in recreate_or_restart_container\\n self.start_container()\\n >> File >> \"/tmp/ansible_kolla_docker_payload_kkez0k31/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 669, in start_container\\n self.pull_image()\\n File >> \"/tmp/ansible_kolla_docker_payload_kkez0k31/ansible_kolla_docker_payload.zip/ansible/module_utils/kolla_docker_worker.py\", >> line 450, in pull_image\\n json.loads(line.strip().decode(\\'utf-8\\')) >> for line in self.dc.pull(\\n File >> \"/usr/local/lib/python3.8/dist-packages/docker/api/image.py\", line 430, >> in pull\\n self._raise_for_status(response)\\n File >> \"/usr/local/lib/python3.8/dist-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.8/dist-packages/docker/errors.py\", line 31, >> in create_api_error_from_http_exception\\n raise cls(e, response=response, >> explanation=explanation)\\ndocker.errors.APIError: 500 Server Error for >> http+docker://localhost/v1.41/images/create?tag=yoga&fromImage=quay.io%2Fopenstack.kolla%2Fubuntu-source-glance-api: >> Internal Server Error (\"Get \"https://quay.io/v2/\ >> <https://quay.io/v2//>": net/http: request canceled while waiting for >> connection (Client.Timeout exceeded while awaiting headers)\")\\n'"} >> META: ran handlers >> >> Regards >> Pradeep >> >> >> On Mon, 12 Dec 2022 at 14:54, Danny Webb <Danny.Webb(a)thehutgroup.com> >> wrote: >> >> Kolla only uses a single controller if you use file based backend by >> default. If you want to continue using the file backend, you can use >> something like an NFS share to share images between controllers and then >> change the glance_file_datadir_volume parameter which will result in the >> api being deployed on all controllers >> ------------------------------ >> *From:* pradeep <pradeep8985(a)gmail.com> >> *Sent:* 12 December 2022 04:53 >> *To:* Dmitriy Rabotyagov <noonedeadpunk(a)gmail.com> >> *Cc:* openstack-discuss <openstack-discuss(a)lists.openstack.org> >> *Subject:* Re: auto switch of glance-api containers to other controllers >> >> >> * CAUTION: This email originates from outside THG * >> ------------------------------ >> Any help is highly appreciated. >> >> Thank you! >> >> On Fri, 9 Dec 2022 at 21:46, pradeep <pradeep8985(a)gmail.com> wrote: >> >> Hi Dmitriy, Thanks for the response. Sorry, I forgot to mention that i >> used kolla ansible for deployment. As per kolla docs, glance-api container >> runs only in one controller. So i am looking from kolla perspective if it >> can automatically switch it over other available controllers. >> >> Regards >> Pradeep >> >> On Fri, 9 Dec 2022 at 14:51, Dmitriy Rabotyagov <noonedeadpunk(a)gmail.com> >> wrote: >> >> Hi, >> >> I'm not sure if you used any deployment tool for your environment, but >> usually for such failover there's a load balancer in conjunction with VRRP >> or Anycast, that able to detect when controller1 is down and forward >> traffic to another controller. >> >> As example, OpenStack-Ansible as default option installs haproxy to each >> controller and keepalived to implement VRRP and Virtual IPs. So when glance >> is down on controller1, haproxy will detect that and forward traffic to >> other controllers. If controller1 is down as a whole, keepalived will >> detect that and raise VIP on controller2, so all client traffic will go >> there. Since controller2 also have haproxy, it will pass traffic to >> available backends based on the source IP. >> >> >> пт, 9 дек. 2022 г., 09:06 pradeep <pradeep8985(a)gmail.com>: >> >> 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 >> >> >> >> >> -- >> ----------------------- >> Regards >> Pradeep Kumar >> >> >> >> -- >> ----------------------- >> Regards >> Pradeep Kumar >> >> *Danny Webb* >> Principal OpenStack Engineer >> Danny.Webb(a)thehutgroup.com >> [image: THG Ingenuity Logo] >> www.thg.com >> <https://www.linkedin.com/company/thg-ingenuity/?originalSubdomain=uk> >> <https://twitter.com/thgingenuity?lang=en> >> >> Danny Webb >> Principal OpenStack Engineer >> The Hut Group <http://www.thehutgroup.com/> >> >> Tel: >> Email: Danny.Webb(a)thehutgroup.com >> >> >> For the purposes of this email, the "company" means The Hut Group >> Limited, a company registered in England and Wales (company number 6539496) >> whose registered office is at Fifth Floor, Voyager House, Chicago Avenue, >> Manchester Airport, M90 3DQ and/or any of its respective subsidiaries. >> >> *Confidentiality Notice* >> This e-mail is confidential and intended for the use of the named >> recipient only. If you are not the intended recipient please notify us by >> telephone immediately on +44(0)1606 811888 or return it to us by e-mail. >> Please then delete it from your system and note that any use, >> dissemination, forwarding, printing or copying is strictly prohibited. Any >> views or opinions are solely those of the author and do not necessarily >> represent those of the company. >> >> *Encryptions and Viruses* >> Please note that this e-mail and any attachments have not been encrypted. >> They may therefore be liable to be compromised. Please also note that it is >> your responsibility to scan this e-mail and any attachments for viruses. We >> do not, to the extent permitted by law, accept any liability (whether in >> contract, negligence or otherwise) for any virus infection and/or external >> compromise of security and/or confidentiality in relation to transmissions >> sent by e-mail. >> >> *Monitoring* >> Activity and use of the company's systems is monitored to secure its >> effective use and operation and for other lawful business purposes. >> Communications using these systems will also be monitored and may be >> recorded to secure effective use and operation and for other lawful >> business purposes. >> hgvyjuv >> >> >> >> -- >> ----------------------- >> Regards >> Pradeep Kumar >> >> *Danny Webb* >> Principal OpenStack Engineer >> Danny.Webb(a)thehutgroup.com >> [image: THG Ingenuity Logo] >> www.thg.com >> <https://www.linkedin.com/company/thg-ingenuity/?originalSubdomain=uk> >> <https://twitter.com/thgingenuity?lang=en> >> > > > -- > ----------------------- > Regards > Pradeep Kumar > -- ----------------------- Regards Pradeep Kumar

1 0

[qa] Cancelling next office hours
by Martin Kopec 15 Dec '22

15 Dec '22

Hi everyone, we're cancelling office hours for the next 3 weeks due to the holidays. The next office hour is gonna be on January 10th. Thank you. Enjoy your holidays! -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 0

kolla-ansible deploy glance with file as a backend on multiple nodes
by A Monster 15 Dec '22

15 Dec '22

I have made a deployment of openstack on multiple centos stream 8 nodes, and used files as a backend for glance service, but according to the documentation, when using file as a glance backend, It can only be deployed on a single node, what can I do to deploy it on multiple servers at once. Thank you.

3 2

reconfiguring the external interface to multiple interfaces doesn't work
by pradeep 14 Dec '22

14 Dec '22

Hello All, I have deployed OpenStack Yoga using kolla ansible with a single external interface initially. Later we realized that we wanted to use multiple interfaces. I have followed the docs to modify the external interface in the globals.yml file as below. *Before:* *globals.yml* neutron_external_interface: "bond2" *After:* *globals.yml* neutron_external_interface: "bond2,enp6s0f1" neutron_bridge_name: "br-ex,br-ex2" *Command used:* kolla-ansible -i multinode reconfigure --tags "common,horizon,neutron" -vv br-ex2 doesn't show up in the neutron nodes. I also noticed that my neutron-openvswitch-agent is continuously restating in both the neutron nodes. neutron-openvswitch-agent.log says as below 2022-12-15 02:12:35.121 7 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [-] Bridge br-int has datapath-ID 0000be5c93241c4f 2022-12-15 02:12:36.040 7 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Mapping physical network physnet1 to bridge br-ex 2022-12-15 02:12:36.041 7 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Bridge br-ex datapath-id = 0x0000801844eaf971 2022-12-15 02:12:36.057 7 INFO neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ovs_bridge [-] Bridge br-ex has datapath-ID 0000801844eaf971 2022-12-15 02:12:36.063 7 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Mapping physical network physnet2 to bridge br-ex2 2022-12-15 02:12:36.063 7 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Bridge br-ex2 for physical network physnet2 does not exist. Agent terminated! Here is the config file. cat /etc/kolla/neutron-openvswitch-agent/openvswitch_agent.ini [agent] tunnel_types = vxlan l2_population = true arp_responder = true extensions = qos,sfc [securitygroup] firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver [ovs] bridge_mappings = physnet1:br-ex,physnet2:br-ex2 datapath_type = system ovsdb_connection = tcp:127.0.0.1:6640 ovsdb_timeout = 10 local_ip = <IP_Address> Also, i tried to change the bridge name from br-ex to br-ex1 but it still shows up br-ex (this can be perceived as my second issue). How can I resolve both issues? Kindly help.

1 0

stackalytics is stop update,
by 韩光宇 14 Dec '22

14 Dec '22

Hi, all I see stackalytics[1] is stop update. The page show "The data was last updated on 09 Nov 2022 12:44:22 UTC". Does anyone know why? And If you want to check the contribution statistics, is there still a way? Thank you for any help. Cheers, Han [1]: www.stackalytics.io

5 6

[manila][release] Proposing to EOL Stein
by Carlos Silva 14 Dec '22

14 Dec '22

Hello! Recently in a weekly meeting we chatted about EOLing stable/stein and all the attendants were found to be in favor of this [0]. As the procedures go [1], we need to make it formal through a post in this mailing list, and see if there are objections. In case of concerns or objections, please reach out through email or the #openstack-manila IRC channel. This will impact all branched manila repositories (manila, python-manilaclient and manila-ui). If there aren't objections or strong concerns, I will be proposing the patches to EOL stable/stein within one week. [0] https://meetings.opendev.org/meetings/manila/2022/manila.2022-11-03-15.00.l… [1] https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-l… Thanks, carloss

1 1

[cinder] Festival of XS reviews?
by Rajat Dhasmana 14 Dec '22

14 Dec '22

Hello Argonauts, I've come to know informally that people might not be around during this time due to the holiday season. Based on this, I would like to ask the cinder team if we would like to have the festival of XS reviews this friday or not? Date: 16 December, 2022 Time: 1400-1600 UTC Please reply with your feedback and if we've enough people joining, we can continue with the session. Thanks Rajat Dhasmana

2 1

[cinder] Bug Report from 12-14-2022
by Sofia Enriquez 14 Dec '22

14 Dec '22

This is a bug report from 12-07-2022 to 12-14-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinder/+bug/1999252 "[RBD -> SolidFire] Cache mode was not updated after volume retype." Unassigned. Medium - https://bugs.launchpad.net/nova/+bug/1999125 "cinder retype volume raise exception with shutoff vm." Unassigned. Cheers, Sofia -- 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

[neutron] Neutron drivers meeting Friday Dec 16
by Rodolfo Alonso Hernandez 14 Dec '22

14 Dec '22

Hello Neutrinos: Please check the Neutron drivers meeting agenda: https://wiki.openstack.org/wiki/Meetings/NeutronDrivers. So far we have two topics to discuss: * https://bugs.launchpad.net/neutron/+bug/1998609 * https://bugs.launchpad.net/neutron/+bug/1998608 See you next Friday.

1 0

[neutron] Neutron meetings cancelled last week of December
by Rodolfo Alonso Hernandez 14 Dec '22

14 Dec '22

Hello Neutrinos: The Neutron meetings (team, CI and drivers) will be cancelled the last week of December. Enjoy your holidays!

1 0

[nova][placement] Spec review day on Dec 14th
by Sylvain Bauza 14 Dec '22

14 Dec '22

Hey folks, As agreed on a previous meeting [1] we will have a second Spec review day on Wed Dec 14th. Now you're aware, prepare your specs in advance so they're reviewable and ideally please be around on that day in order to reply to any comments and eventually propose a new revision, ideally the same day. As a side note, we'll have an Implementation review day on Jan 10th which will focus on reviewing feature changes related to accepted specs and we also plan to review a few implementation patches by Dec 15th. Thanks, -Sylvain [1] https://meetings.opendev.org/meetings/nova/2022/nova.2022-11-29-16.00.log.h…

1 1

[all][tc] Technical Committee next weekly meeting on 2022 Dec 14 at 1600 UTC
by Ghanshyam Mann 13 Dec '22

13 Dec '22

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2022 Dec 14, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Dec 13 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[Keystone] member role with access rule can not list hypervisors details
by Hemant Sonawane 13 Dec '22

13 Dec '22

Hello, Does application credentials created as member role with access rule need any special permissions to list hypervisors via cli? Here is the access rule i created for my application credentials [ { "path": "/v2.1/**", "method": "GET", "service": "compute" } ] +--------------------------------+---------+--------+-------------------+ | ID | Service | Method | Path | +--------------------------------+---------+--------+-------------------+ | f2417b29f8394281aaa088d7c01059 | compute | POST | /v2.1/hypervisors | | 0cacd63becc04db086cd070db978c5 | compute | POST | /v2.1/servers | | 366abc32faf543b9ab047a83eafe83 | compute | GET | /v2.1/servers | | 4a4258b6a37c49f3816b708efa179f | compute | GET | /v2.1/** | +--------------------------------+---------+--------+-------------------+ I tried to use other access rule too. After sourcing the credentials if i would like to list any of the openstack resources it simply does not work *openstack volume list openstack The request you have made requires authentication. (HTTP 401)openstack hypervisor list The request you have made requires authentication. (HTTP 401) (Request-ID: req-c4532458-5606-4c85-8f93-20e61f57e2c9)* i think this could be a bug in keystone or it might need any special permissions with access rule. Please help will be really appreciated. -- Thanks and Regards, Hemant Sonawane

1 0

[cinder] volume_attachement entries are not getting deleted from DB
by Hemant Sonawane 13 Dec '22

13 Dec '22

Hello I am using wallaby release openstack and having issues with cinder volumes as once I try to delete, resize or unshelve the shelved vms the volume_attachement entries do not get deleted in cinder db and therefore the above mentioned operations fail every time. I have to delete these volume_attachement entries manually then it works. Is there any way to fix this issue ? nova-compute logs: cinderclient.exceptions.ClientException: Unable to update attachment.(Invalid volume: duplicate connectors detected on volume Help will be really appreciated Thanks ! -- Thanks and Regards, Hemant Sonawane

3 6

[barbican] Meeting cancelled today
by Grzegorz Grasza 13 Dec '22

13 Dec '22

Hi all, I won't be able to host the Barbican meeting today. As there are no outstanding topics to discuss, I'm cancelling it. / Greg

1 0

[all] many Python 3.11 failures in OpenStack components
by Thomas Goirand 12 Dec '22

12 Dec '22

Hi, The below bugs have been reported against the OpenStack components in Debian. I would greatly appreciate help fixing these before Bookworm is in freeze (in January). If you fix a bug, it'd be great to add a link in the Debian bug, so I can see the URL of the review (even if the patch isn't merged yet). As a reminder: to write to a Debian bug, simply write to <bugnumber>@bugs.debian.org (the Debian BTS is email driven). networking-mlnx: https://bugs.debian.org/1021924 FTBFS test failures: sqlalchemy.exc.InvalidRequestError: A transaction is already begun on this Session. networking-l2gw: https://bugs.debian.org/1023764 autopkgtest failure: module 'neutron.common.config' has no attribute 'register_common_config_options' ironic: https://bugs.debian.org/1024783 needs update for python3.11: Cannot spec a Mock object ironic-inspector: https://bugs.debian.org/1024952 needs update for python3.11: Failed to resolve the hostname (meow) for node uuid1 mistral-dashboard: https://bugs.debian.org/1024958 needs update for python3.11: module 'inspect' has no attribute 'getargspec'. Did you mean: 'getargs'? murano: https://bugs.debian.org/1025013 needs update for python3.11: 'NoneType' object has no attribute 'object_store' python-cinderclient: https://bugs.debian.org/1025028 needs update for python3.11: conflicting subparser: another-fake-action python-novaclient: https://bugs.debian.org/1025110 needs update for python3.11: conflicting subparser python-sushy: https://bugs.debian.org/1025124 needs update for python3.11: AssertionError: expected call not found python-taskflow: https://bugs.debian.org/1025126 needs update for python3.11: MismatchError Cheers, Thomas Goirand (zigo)

7 8

[neutron][devstack][qa] Dropping lib/neutron module
by Slawek Kaplonski 12 Dec '22

12 Dec '22

Hi, As You maybe know (or not as this was very long time ago) there are 2 modules to deploy Neutron in devstack: * old one called lib/neutron-legacy * new one called lib/neutron The problem is that new module lib/neutron was really never finished and used widely and still everyone is using (and should use) old one lib/neutron-legacy. We discussed that few times during PTGs and we finally decided to drop "new" module lib/neutron and have then rename old "lib/neutron-legacy" to be "lib/neutron" again. Decision was made because old module works fine and do its job, and as there is nobody who would like to finish really new module. Also having 2 modules from which "legacy" one is the only one which really works can be confusing and we want to avoid that confusion. So I proposed patches [1] and [2] to drop this unfinished module. I also proposed DNM patches for Neutron [3] and Tempest [4] to test that all jobs will work fine. But if You are maybe relaying on the Neutron modules from Devstack, please propose some test patch in Your project too and check if everything works fine for You. In patch [2] I didn't really removed "lib/neutron-legacy" yet because there are some projects which are sourcing that file in their devstack module. As [1] and [2] will be merged I will be proposing patches to change that for those projects but any help with that is welcome :) [1] https://review.opendev.org/c/openstack/devstack/+/865014 [2] https://review.opendev.org/c/openstack/devstack/+/865015 [3] https://review.opendev.org/c/openstack/neutron/+/865822 [4] https://review.opendev.org/c/openstack/tempest/+/865821 -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

[neutron][ironic] Distributed routers and SNAT
by Arnaud Morin 12 Dec '22

12 Dec '22

Hello team, When using router in DVR (+ HA), we end-up having the router on all computes where needed. So far, this is nice. We want to introduce Ironic baremetal servers, with a private network access. DVR won't apply on such baremetal servers, and we know floating IP are not going to work. Anyway, we were thinking that SNAT part would be OK. After doing few tests, we noticed that all distributed routers are answering to ARP and ICMP, thus creating duplicates in the network. $ arping -c1 192.168.43.1 ARPING 192.168.43.1 60 bytes from fa:16:3f:67:97:6a (192.168.43.1): index=0 time=634.700 usec 60 bytes from fa:16:3f:dc:67:91 (192.168.43.1): index=1 time=750.298 usec --- 192.168.43.1 statistics --- 1 packets transmitted, 2 packets received, 0% unanswered (1 extra) Is there anything possible on neutron side to prevent this? FYI, I did a comparison with routers in centralized mode (+ HA). In that situation, keepalived is putting the qr-xxx interface down in qrouter namespace. In distributed mode, keepalives is running in snat- namespace and cannot manage the router interface. Any help / tip would be appreciated. Thanks! Arnaud.

4 7

[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 10 Dec '22

10 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 10 Dec '22

10 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

openstack 504 error
by fereshteh loghmani 10 Dec '22

10 Dec '22

hello i use Kolla ansible multi-region. in one of my regions that is not keystone and hypervisor on it. some times I receive the error Gateway Timeout. how could i solve this problem? thanks is advance. Gateway Timeout The gateway did not receive a timely response from the upstream server or application.

1 0

[all][tc] What's happening in Technical Committee: summary 2022 Dec 09: Reading: 5 min
by Ghanshyam Mann 09 Dec '22

09 Dec '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Dec 7. Most of the meeting discussions are summarized in this email. Meeting recording and summary logs are available @ https://www.youtube.com/watch?v=JQYzoJV35Xw @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-12-07-16.00.log.html * Next TC weekly meeting will be on Dec 14 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Dec 13. 2. What we completed this week: ========================= * Technical Election changes: extending the period for nomination and voting to two weeks You might have observed in elections that a lot of candidates miss the nomination deadline. To improve the situation, TC discussed it in the election retrospective in PTG and decided to extend the nomination and the voting period to two weeks. This has been updated in the TC charter[2]. This change will be applicable from the next (2023.2 cycles) technical elections. Another update to the next elections is that ianychoi and tonyb will be serving as election officials[3]. Thanks to both to volunteer for it. * Added Adjutant to inactive project list[4] Dale Smith (current PTL) is in sync with this and already started working on the pending things to mark it Active. For example, he fixed the gate[5]. * Added the infinidat-tools subordinate charm to OpenStack charms[6] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[7]. Open Reviews ----------------- * Two open reviews for ongoing activities[8]. Change in Inactive project timeline ----------------------------------------- While proposing the Adjutant project in the Inactive list, the release team pointed out that we should have the final list of deliverables to release by milestone 2 instead of the final release time. This is a valid point and TC is reflecting the same in Inactive project timeline where TC will take the final decision on inactive projects to move back to active again and consider for release by milestone 2. The change in TC documentation is up for review[9] Mistral release and more maintainers ------------------------------------------- The release team identified the Mistral needs more work to be considered for release and proposing to mark Mistral release deprecated [10]. The good thing is that there are more volunteers from OVHcloud to help maintain it[11]. TC will monitor the situation and decide on the Mistral release before milestone 2. Renovate translation SIG i18 ---------------------------------- * Brian on behalf of TC presented it in the Board meeting on Dec 6th and the budget for the Weblate tool license seems ok but we still need an engineer to do the translation migration and maintenance. Here is the proposal discussed in the Board meeting[12] Project updates ------------------- * None 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-November/03124… [2] https://review.opendev.org/c/openstack/governance/+/865367 [3] https://governance.openstack.org/election/#election-officials [4] https://review.opendev.org/c/openstack/governance/+/849153 [5] https://review.opendev.org/c/openstack/adjutant/+/866823 [6] https://review.opendev.org/c/openstack/governance/+/864067 [7] https://etherpad.opendev.org/p/tc-2023.1-tracker [8] https://review.opendev.org/q/projects:openstack/governance+status:open [9] https://review.opendev.org/c/openstack/governance/+/867062 [10] https://review.opendev.org/c/openstack/governance/+/866562 [11] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/03142… [12] https://docs.google.com/document/d/1PwGASync8blZoFOlqaIe3xwJkOc1iByHKVbGDTb… [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-14, Dec 12 - 16
by Elõd Illés 09 Dec '22

09 Dec '22

Development Focus ----------------- The Antelope-2 milestone will happen next month, on January 5th, 2023. 2023.1 Antelope-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/antelope/schedule.html for details. General Information ------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other 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. (Note: cycle-with-rc release model does not suit for every project) At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/antel… You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/antelope/schedule.html#a-mf Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates -------------------------- Antelope-2 Milestone: January 5th, 2023 Final 2023.1 Antelope release: March 22nd, 2023 Előd Illés irc: elodilles @ #openstack-release

1 0

[gate][stable][qa] Hold recheck: Devstack based job using tox4 are broken (especially greande, stable jobs)
by Ghanshyam Mann 09 Dec '22

09 Dec '22

Hi All, As you might know, the devstack-based job fails on the tempest command with the below error: Error- venv: failed with tempest is not allowed, use allowlist_externals to allow it It is failing where jobs are using the tox4 (in grenade job or stable branch job or some master branch job like focal job using tox4[1]). This is another issue of mix match of tox version in stable and master jobs which we are discussing in a separate thread[2]. On tempest command or allowlist_externals failure, we are testing one fix for that but please hold recheck until it gets fixed or any workaround is merged - https://review.opendev.org/q/Ifc8fc6cd7aebda147043a52d6baf99a2bacc009c I have opened a bug also to track it https://bugs.launchpad.net/devstack/+bug/1999183 [1] https://zuul.opendev.org/t/openstack/build/aaad7312f68246c0979e1a43cfe96c3b… [2] https://lists.openstack.org/pipermail/openstack-discuss/2022-December/03144… -gmann

1 1

[sahara][sahara-cores] Combined patch that recovers CI tests
by Dmitriy Rabotyagov 09 Dec '22

09 Dec '22

Hi sahara cores, As you might know Sahara has been broken for quite some time now due to multiple reasons, and didn't have passing tests for Zed release at all. I have come up with a patch [1] that fixes major issues, including: * Zuul Queus definition * Adapting new jsonschema version * Replacing usage of iteritems with six As a result Zuul is happy, all tempest and tox tests are passing it the moment. It would be great if you could review these changes and land other important patches to unblock other contributors in the project and prevent it from falling under "inactive" projects list. [1] https://review.opendev.org/c/openstack/sahara/+/864728

1 0

[neutron] Drivers meeting cancelled
by Rodolfo Alonso Hernandez 09 Dec '22

09 Dec '22

Hello Neutrinos: Due to the lack of agenda, today's meeting is cancelled. If you want to add any topic to this meeting, please check [1] and use the "on demand agenda" section. Regards. [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers

1 0