February 2022 - openstack-discuss

[TripleO] centos9 jobs only for master, centos 8 & 9 for wallaby
by Marios Andreou 02 Mar '22

02 Mar '22

Hello TripleO o/ During the last period the tripleo-ci team has been working on getting tripleo CI jobs to run centos-9. On master branches across all TripleO repos we now run C9 exclusively (since [1]). On Wallaby branches, after the work at [2] (in particular after https://review.opendev.org/c/openstack/tripleo-ci/+/830132 merges) we will run both C8 and C9 jobs. I started an etherpad at [3] thinking this would be a PTG topic, but I think we'll want to have this conversation way before then. There is a tripleo-heat-templates example in the etherpad that shows what we can expect from the job runs (note the exact jobs that run will vary per repo and even between changes depending on the files touched - but generally there will be duplication between 8 and 9 jobs). The current proposal is that we keep a minimal subset on C8 Wallaby, with C9 wallaby having the full set of jobs. Two factors that will affect our decisions are (there may be more?) i) Upgrades requirements - are we supporting upgrading to Wallaby on 8? For example, the coming undercloud-upgrade-ffu job will be train 8 to wallaby 8. In which case we definitely need to keep at least some subset of 8 jobs (and can't entertain the removal of 8 from Wallaby completely). ii) Are we importing from Wallaby 8 or Wallaby 9? Currently it is 8 but this will soon switch. For the wallaby c8 'subset of jobs' e.g. multinode, vanilla standalone (no scenarios? some subset of them?), undercloud-ffu, minor update. This is just to start the conversation so please reply if you have thoughts or comments about any of the above. We are planning to discuss this in the coming tripleo-ci community call this coming Tuesday at 1330 UTC - meeting link at [4] so please join us if you can and would like to participate, regards, marios [1] https://review.opendev.org/q/topic:c8_teardown_master [2] https://review.opendev.org/q/topic:c9_wallaby_gates [3] https://etherpad.opendev.org/p/tripleoci-wallaby-centos-8-9 [4] https://meet.google.com/bqx-xwht-wky

4 7

[horizon][customization]
by Mathilde Hermet 02 Mar '22

02 Mar '22

Hello Openstack team, I'm currently working on customizing the Horizon (xena) dashboard to use the OVHcloud assets: logo.svg and logo-splash.svg. I've been following this documentation https://docs.openstack.org/horizon/latest/configuration/themes.html I added the ovhcloud theme in horizon/openstack_dashboard/local/local_settings.py in AVAILABLE_THEMES, I created the subdir ovhcloud in horizon/openstack_dashboard/themes and I created a ovhcloud/img with logo.svg and logo-splash.svg in it. I put a _variables.scss and a _styles.scss in /themes/ovhcloud/ Then I executed python manage.py collectstatic It put all the files in horizon-sources/horizon.../static/themes/ovhcloud But then when trying to connect with the session cookie theme="ovhcloud", I have a 500 error. i don't think it comes from images because i've been puting it in /horizon-souurces/horizon.../static/dashbaord.img and they were displayed correctly. Do you have any idea about the misconfiguration I've done ? Best regards, Mathilde Hermet

4 3

[nova][octavia][masakari][designate][oslo][requirements] oslo.context>=4.0.0 seems to need updated tests
by Matthew Thode 01 Mar '22

01 Mar '22

The update to see what's breaking is here https://review.opendev.org/829599 Feel free to make that patch depend on your fix to test (with rechecks) -- Matthew Thode

4 6

Fluentd error with Kolla ansible deployment
by A Monster 01 Mar '22

01 Mar '22

I'm getting the following error while trying to deploy openstack using kolla-ansible. I've set up a local docker registry and enabled insecure registries in daemon.json file and I even tried to pull fluentd docker image but I still get the following error TASK [common : Ensure fluentd image is present for label check] fatal: [localhost]: 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/lib/python3.6/site-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=xena&fromImage=quay.io%2Fkolla%2Fcentos-source-fluentd\\n\\nDuring handling of the above exception, another exception occurred:\\n\\nTraceback (most recent call last):\\n File \"/tmp/ansible_kolla_docker_payload_xizndx9s/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1241, in main\\n File \"/tmp/ansible_kolla_docker_payload_xizndx9s/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 1116, in ensure_image\\n File \"/tmp/ansible_kolla_docker_payload_xizndx9s/ansible_kolla_docker_payload.zip/ansible/modules/kolla_docker.py\", line 692, in pull_image\\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)\\ndocker.errors.APIError: 500 Server Error for http+docker://localhost/v1.41/images/create?tag=xena&fromImage=quay.io%2Fkolla%2Fcentos-source-fluentd: Internal Server Error (\"unauthorized: access to the requested resource is not authorized\")\\n'"}

2 2

[qa][devstack] Proposing Dan Smith to devstack core
by Martin Kopec 28 Feb '22

28 Feb '22

Hi all, we would like to propose Dan Smith (IRC: dansmith) to devstack core. Dan is an experienced contributor who has been contributing to several openstack projects. We are glad Dan volunteered to help us in the Devstack project as well. You can vote/feedback in this email thread. If no objection by 17th of February, we will add Dan to the core list. Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

3 3

[cinder] Yoga FEATURE FREEZE in effect
by Harsha Ailani 28 Feb '22

28 Feb '22

Hello Argonauts, Having passed Milestone-3 this week (and yes, it was painful), let's evaluate where we are with cinder Yoga features: - https://blueprints.launchpad.net/cinder/yoga Note: You must apply for a Feature Freeze Exception (FFE) by 17:00 UTC on Tuesday 1 March. Features granted an FFE must be in the gate by 20:00 UTC on Monday 7 March. Being granted an FFE is not a guarantee that your feature will be included in Yoga. FFE Details: ------------------ ibm-svf-portset - https://blueprints.launchpad.net/cinder/+spec/ibm-svf-portset - https://review.opendev.org/c/openstack/cinder/+/817351 - no +2s because third-party CI isn't passing - let's face it, no one is going to review this with failing CI even if it gets an FFE - must apply for an FFE The Third-Party CI for this review is IBM Storage CI. As the storage was done last week the CI failed. But today Zuul and IBM Storage CI both passed successfully. The portset has been tested throughly and reviewed by several reviewers in the last 2 months. All the comments are addressed and tested. The review has received a +2 from Rajat and +1 from Eric and Brian. The review is ready to be merged. Thanks and Regards, Harsh Ailani

2 1

[PTLs][release] Yoga Cycle Highligts
by Előd Illés 28 Feb '22

28 Feb '22

Hi, This is a reminder, that *this week* is the week for Cycle highlights [1][2]! They need to be added to deliverable yamls so that they can be included in release marketing preparations. (See the details about how to add them at the project team guide [3].) [1] https://releases.openstack.org/yoga/schedule.html [2] https://releases.openstack.org/yoga/schedule.html#y-cycle-highlights [3] https://docs.openstack.org/project-team-guide/release-management.html#cycle… Thanks, Előd Illés irc: elodilles

2 1

[neutron] Bug deputy report for week of 21. 02. 2022
by Lajos Katona 28 Feb '22

28 Feb '22

Hi Neutron Team I was bug deputy in neutron last week. It was a very quiet week again. Needs More attention ================= * Duplicate IP address on LSPs in the same LS lead to unpredictable flow output (https://bugs.launchpad.net/neutron/+bug/1961046 ) * [ovn-octavia-provider] OVN NB DB timeouts ( https://bugs.launchpad.net/neutron/+bug/1961874 ) ** perhaps not Neutron related, but more a pkg version problem. Critical ====== * Network interface not found in namespace https://bugs.launchpad.net/neutron/+bug/1961740 ** In progress: https://review.opendev.org/c/openstack/neutron/+/830622 High ==== * Transition to SQLAlchemy 2.0 ( https://bugs.launchpad.net/neutron/+bug/1962153) * [Prefix Delegation] router add segment fails with Subnet for router interface must have a gateway IP ( https://bugs.launchpad.net/neutron/+bug/1962306 ) * [ntp] "test_network_attached_with_two_routers" randomly failing ( https://bugs.launchpad.net/neutron/+bug/1962167) ** In progress: https://review.opendev.org/c/openstack/neutron/+/830813 Low ==== * There may be a typo in the neutron document whose the title is 'Manual install & Configuration' (https://bugs.launchpad.net/neutron/+bug/1962324) Invalid ====== * generate_config_file_samples.sh fails with invalid literal for int() with base 10 (https://bugs.launchpad.net/neutron/+bug/1961906) Regards Lajos Katona (lajoskatona)

1 0

[ops][nova] How to update from N to N+3 (and manage nova services that don't start because they find too old compute nodes...)
by Massimo Sgaravatto 28 Feb '22

28 Feb '22

Dear all When we upgraded our Cloud from Rocky to Train we followed the following procedure: 1) Shutdown of all services on the controller and compute nodes 2) Update from Rocky to Stein of controller (just to do the dbsyncs) 3) Update from Stein to Train of controller 4) Update from Rocky to Train of compute nodes We are trying to do the same to update from Train to Xena, but now there is a problem because nova services on the controller node refuse to start since they find too old compute nodes (this is indeed a new feature, properly documented in the release notes). As a workaround we had to manually modify the "version" field of the compute nodes in the nova.services table. Is it ok, or is there a cleaner way to manage the issue ? Thanks, Massimo

5 10

[devstack][openstack-qa] DevStack upgrade betweem major releases
by Eduardo Santos 27 Feb '22

27 Feb '22

Hello folks, What is the procedure for upgrading a DevSack deployment from one major release to another? I didn't find any information on this in the official documentation. [1] My team maintains DevStack deployments used to provision virtual machines to developers. How can we, let's say, upgrade a stable/xena DevStack to stable/yoga, when it's released? Best regards, Eduardo Santos [1] https://docs.openstack.org/devstack/latest/

3 2