December 2024 - openstack-discuss

[Nova] Nova-compute service flapping on Antelope
by Jakub Darmach 24 Dec '24

24 Dec '24

Hello, Recently I encountered an interesting issue - nova-compute service started to temporarily lose Rabbit connectivity to regain it after a few seconds on Antelope. The issue was replicated on the test environment, without specific steps to replicate though - it just starts to happen after some time. I pasted a log example in the bug I opened [1]. First we can see rabbit logging closing AMQP connection, followed by nova-compute reporting rabbit server being unreachable, with next message being successful reconnection. Restarting nova-compute services helps temporarily, the issue starts to manifest after a few days. Initially disconnects once every few hours, each time in shorter intervals, to the point it happens every minute or so. Did anyone encounter something similar? [1] https://bugs.launchpad.net/nova/+bug/2092297 Pozdrawiam / Best regards, *Jakub Darmach*

2 1

[tacker] Cancelling the next two weekly meetings
by Yasufumi Ogawa 24 Dec '24

24 Dec '24

Hi all, Due to the holidays, I'd skip the next two meetings. So, the next our meeting is Jan 14th. Thanks, Yasufumi

1 1

ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat.| Openstack tripleo wallaby version
by Swogat Pradhan 24 Dec '24

24 Dec '24

Hi, I am currently trying to deploy openstack wallaby using tripleo arch. I created the network jinja templates, ran the following commands also: #openstack overcloud network provision --stack overcloud --output networks-deployed-environment.yaml custom_network_data.yaml # openstack overcloud network vip provision --stack overcloud --output vip-deployed-environment.yaml custom_vip_data.yaml # openstack overcloud node provision --stack overcloud --overcloud-ssh-key /home/stack/sshkey/id_rsa overcloud-baremetal-deploy.yaml and used the environment files in the openstack overcloud deploy command: (undercloud) [stack@hkg2director ~]$ cat deploy.sh #!/bin/bash THT=/usr/share/openstack-tripleo-heat-templates/ CNF=/home/stack/ openstack overcloud deploy --templates $THT \ -r $CNF/templates/roles_data.yaml \ -n $CNF/workplace/custom_network_data.yaml \ -e ~/containers-prepare-parameter.yaml \ -e $CNF/templates/node-info.yaml \ -e $CNF/templates/scheduler-hints.yaml \ -e $CNF/workplace/networks-deployed-environment.yaml \ -e $CNF/workplace/vip-deployed-environment.yaml \ -e $CNF/workplace/overcloud-baremetal-deployed.yaml \ -e $CNF/workplace/custom-net-bond-with-vlans.yaml Now when i run the ./deploy.sh script i encounter an error stating: ERROR openstack [-] Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat. The generated environments from 'openstack overcloud baremetal provision' and 'openstack overcloud network provision' must be included with the deployment command.: tripleoclient.exceptions.InvalidConfiguration: Resource OS::TripleO::Network::Ports::ControlPlaneVipPort maps to type OS::Neutron::Port and the Neutron service is not available when using ephemeral Heat. The generated environments from 'openstack overcloud baremetal provision' and 'openstack overcloud network provision' must be included with the deployment command. 2022-04-19 13:47:16.582 735924 INFO osc_lib.shell [-] END return value: 1 Can someone tell me where the mistake is? With regards, Swogat Pradhan

4 4

[all] Installation guide for openSUSE and SUSE Linux Enterprise
by Takashi Kajinami 23 Dec '24

23 Dec '24

Hello, As you may know, we have been maintaining installation guide for three linux distributions below. - oepnSUSE and SUSE Linux Enterprise - Red Hat Enterprise Linux and CentOS - Ubuntu However, as far as I know, the packages for openSUSE and SLES haven't been built/updated for some time. Also openSUSE was removed from tested runtimes in wallaby and hasn't been tested. So I doulbt that users can use these operating systems to install OpenStack nowadays. Can/Should we remove the guide for openSUSE/SLES Now ? I'm not very sure if we can maintain the guide for these with no details available nowadays. Thank you, Takashi -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit

2 1

[neutron] Bug deputy Dec 16 - Dec 22
by Rodolfo Alonso Hernandez 23 Dec '24

23 Dec '24

Hello Neutrinos: This is the bug list from last week: HIGH * api slow due to missing LRP index ( https://bugs.launchpad.net/neutron/+bug/2092133) Assigned and patch proposed: https://review.opendev.org/c/openstack/ovsdbapp/+/938004 MEDIUM * [RFE] OVN: allow to configure activation-strategy (change it to a different strategy from rarp; or disable completely) ( https://bugs.launchpad.net/neutron/+bug/2092250) Assigned and patch proposed: https://review.opendev.org/c/openstack/neutron/+/938106 LOW * [OVN] Migrate the OVN L3 scheduler to use HA_Chassis_Group ( https://bugs.launchpad.net/neutron/+bug/2092271) Assigned. * Deprecate and remove vlan_transparent config option ( https://bugs.launchpad.net/neutron/+bug/2092174) *NOT ASSIGNED*. Regards.

1 0

[freezer][freezer-dr] Proposal to retire Freezer DR project
by Dmitriy Rabotyagov 23 Dec '24

23 Dec '24

Hi folks, As an ongoing effort to return Freezer project back to the list of Active projects and recovering gate health for repositories owned by Freezer, I've come across freezer-dr[1] Freezer DR is a separate from freezer/freezer-api instance-ha project which is highly pluggable by design with the main goal to evacuate instances from the compute node once service detects that the serving compute node is down. And that is what is currently achieved by the Masakari project. While pluggable design for the service, can be treated as a good benefit in favor of it. Another relatively valuable benefit of freezer-dr, is that it uses nova service state to detect if the compute is down, rather then require 3rd party cluster tooling to independently evaluate hypervisor health. Regardless, I don't see enough value to keep maintenance of that project and instead it's better to keep focus on Masakari maintenance/development instead. With that being said, I suggest the retirement of the freezer-dr project. If someone feels in favor of keeping maintenance of a separate project for instance evacuation - please feel free to reply in thread until December 10, 2024. After that date I will initiate the project retirement process. [1] https://opendev.org/openstack/freezer-dr

2 2

[magnum][cluster api] Heads-up - Octavia OVN driver and latest CAPO
by Stig Telfer 20 Dec '24

20 Dec '24

Hi Magnum folks - Heads up - we wanted to make people aware of a recent upstream CAPO change that could break your Magnum setup if using Cluster API and the Octavia OVN driver. What we've seen is that a recent contribution to CAPO tightens the security group rules for NodePorts to the local tenant network. This works fine for Octavia's Amphora driver, in which HAproxy becomes the source for all back-end API requests. The Octavia OVN driver doesn't have that behaviour, which results in inbound requests getting filtered. The CAPO release is v0.11.0 (https://github.com/kubernetes-sigs/cluster-api-provider-openstack/releases/…) The issue is described here: https://github.com/kubernetes-sigs/cluster-api-provider-openstack/issues/23… The Magnum drivers will pin CAPO driver versions so it's more of a developer / power-user concern than for conventional operators. Cheers, Stig

1 0

[masakari] is this project still active and can be used in production environment
by luckydog xf 20 Dec '24

20 Dec '24

Hi, list, I saw this project hasn't been active for months. So I'm wondering if it is still actively developed and can it be used in production? Are there any use cases ? Thanks.

4 8

Openstack ansible Upgrades
by engineer2024 20 Dec '24

20 Dec '24

Is it possible to upgrade openstack ansible from one major release to another, along with the os distribution upgrade all in one flow ? I mean, as of now we are doing the upgrade as two step process. first we are upgrading the os of the hosts and then the os of the lxc containers and then re running the existing openstack version playbooks. Next , we are upgrading to major release of OSA. This two step process is doubling our effort and time to upgrade to a major version. Is it possible to download and run the major release playbooks soon after the os upgrades ? instead of rerunning the existing playbook again and then download and running next version playbooks ?

2 1

[openstack][magnum] user who created cluster was deleted from keystone
by Nguyễn Hữu Khôi 20 Dec '24

20 Dec '24

Hello. I have a case: What will we do if the user who created the cluster was deleted from the keystone? In this case, we cannot add or remove node groups or use autoscale and autoheal. I tried to create a new application credential and patch my cluster. Then I can add or remove node groups but new node groups cannot join the cluster(nodes not ready) Thank you. Regards Nguyen Huu Khoi

2 2