September 2022 - openstack-discuss

Fwd: DPDK+OVS with OpenStack
by Mark Wittling 23 Apr '25

23 Apr '25

Looking for someone who knows OpenStack with OpenVSwitch, and in addition to that, DPDK with OpenStack and OVS.I am using OpenStack Queens, with OpenVSwitch. The architecture I am using is documented here: https://docs.openstack.org/neutron/queens/admin/deploy-ovs-provider.htmlThe OVS I am using on the Compute Node, is compiled with DPDK, and I have enabled the datapath to netdev (DPDK) on br-prv (provider network bridge), and br-tun (tunneling bridge). But these two bridges, br-tun and br-prv, are patched into another OpenStack bridge, called br-int. I wasn’t actually sure about whether to tinker with this bridge, and wondered what datapath it was using.Then, I realized there is a parameter in the openvswitch_agent.ini file, which I will list here: # OVS datapath to use. 'system' is the default value and corresponds to the # kernel datapath. To enable the userspace datapath set this value to 'netdev'. # (string value) # Possible values: # system - <No description provided> # netdev - <No description provided> #datapath_type = system datapath_type = netdev So in tinkering with this, what I realized, is that when you set this datapath_type to system or netdev, it will adjust the br-int bridge to that datapath type.So here is my question. How can I launch a non-DPDK VM, if all of the bridges are using the netdev datapath type?Here is another question. What if one of the flavors don’t have the largepages property set on them? I assumed OpenStack would revert to a system datapath and not use DPDK for those VM interfaces. Well, I found out in testing, that is not the case. If you set all your bridges up for netdev, and you don’t set the property on the Flavor of the VM (largepages), the VM will launch, but it simply won’t work.Is there no way, on a specific Compute Host, to support both DPDK (netdev datapaths) and non-DPDK (system datapaths)?Either on a VM interface level (VM has one interface that is netdev DPDK and another that is system datapath non-DPDK)?Or on a VM by VM basis (VM 1 has 1 or more netdev datapath interfaces and VM 2 has 1 or more system datapath interfaces)?Am I right here? Once you set up a Compute Host for DPDK, it’s DPDK or nothing on that Compute Host? (edited)

3 2

How to config DPDK compute in OVN
by dangerzone ar 22 Apr '25

22 Apr '25

Hi....as far I understand ovs does support dpdk compute to be deployed. I'm referring to the guideline ' *https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html <https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html>* ' ... It's too brief.. May I know how to config dpdk compute in OVN networking openstack? Hope someone could help what is the config to be done.... Currently compute is run without dpdk over openstack train ovn based. Please need some info on how I can proceed. Thank you

2 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

Live migration fails
by Szabo, Istvan (Agoda) 07 Aug '24

07 Aug '24

Hi, I have couple of compute nodes where the live migration fails with existing vms. When I quickly spawn a vm and try live migration it works so I assume shouldn't be a big problem with the compute node. However I have many existing vms where it fails with a servername not found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 ERROR nova.conductor.tasks.migrate [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Unable to find record for source node servername on servername: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Failed to compute_task_migrate_server: Compute host servername could not be found.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Setting instance to ACTIVE state.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.672 227612 ERROR oslo_messaging.rpc.server [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Exception during message handling: ComputeHostNotFound: Compute host am-osfecn-4025 Tried with this command: nova live-migration --block-migrate id. Any idea? Thank you. ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 16

[puppet] Proposing core team clean up
by Takashi Kajinami 23 Aug '23

23 Aug '23

Hello, I went through the current core reviewers and found out that the current list includes some people no longer working in the OpenStack community. I'd like to propose removing the following persons from the core reviewer team as we haven't seen these people making any activity in the community recently. * Pradeep Kilambi - puppet-aodh, puppet-ceilometer, puppet-gnocchi, puppet-panko * Richard Megginson - puppet-keystone * Denis Egorenko - puppet-murano * Serg Melikyan - puppet-murano * Sergey Kolekonov - puppet-neutron * David Moreau Simard - puppet-openstack-integration * Yu xingchao - all modules Also, I confirmed that Wes Hayutin is no longer working for OpenStack and he agreed to retire from the core reviewer position. Thus I'll remove him as well. I'll be open for any feedback for one week to hear any thoughts/feedback about this removal. I'd like to take this moment to thank all people for their past work. We always welcome them back if they resume their work in this project. Thank you, Takashi KAJINAMI

3 4

Re: [all] [oslo.messaging] Interest in collaboration on a NATS driver
by Tobias Urdin 22 Jul '23

22 Jul '23

Hello Kai, Great to hear that you’re interested! I’m currently just testing this as a POC directly in devstack so there is real-world testing (not should it yet I think, needs more development first). Best regards Tobias > On 30 Aug 2022, at 18:32, Kai Bojens <kb(a)kbojens.de> wrote: > > Am 29.08.22 um 15:46 schrieb Tobias Urdin: > >> If anybody, or any company, out there would be interested in collaborating in a project to bring this support and maintain it feel free to >> reach out. I’m hoping somebody will bite but atleast I’ve put it out there for all of you. > > Hi, > I am very much interested to take a closer look at your work and maybe contribute to it. Although I'm working with OpenStack for my employer at the moment, I'd do this in my spare time as I'm not sure that I can convince him to add another staging system with a full OpenStack installation just for developing a RabbitMQ replacement. That's not on our agenda as we are mostly users and not developers of OpenStack. > > As I'm pretty new to the messaging topic and had just heard of NATS and your idea, I'll first would have to dive into NATS and then I would take a closer look at your code and maybe try to create some documentation or tests. So, I can't promise anything but as I said I'm very interested in your approach as I also see the massive load from RabbitMQ. > > This brings me to the most important question: Where do you run and test your code? > > Greetings, > Kai

8 30

live resize
by Parsa Aminian 15 Mar '23

15 Mar '23

hello on openstack with ceph backend is it possible to live resize instances ? I want to change flavor without any down time .

5 6

[charms] Team Delegation proposal
by Chris MacNaughton 08 Feb '23

08 Feb '23

Hello All, <tl;dr> I would like to propose some new ACLs in Gerrit for the openstack-charms project: - openstack-core-charms - ceph-charms - network-charms - stable-maintenance </tl;dr> With an increasing focus split among the openstack-charmers team, I'm observing that people are focused on more specific subsets of the charms, and would like to propose that new ACLs are created to allow us to recognize that officially. I've chosen the breakdown above as it aligns neatly with where the focus lines are at this point, letting developers work on their specific focus areas. This proposal would not reduce permissions for anybody who is currently a core on the openstack-charms project and, in fact, future subteam core members could aspire to full openstack-charmers core as well. Ideally, this approach will let us escalate developers to "core" developers for the subteam(s) where they have demonstrated the expertise we expect in a core-charmer. It also allows a more gradual escalation to being a core in the openstack-charms project, making it a progression rather than a single destination. As a related addition, I'm appending to this proposal the creation of a stable-maintenance ACL which would allow members to manage backports without a full core-charmer grant. --- Chris MacNaughton

5 7

[cinder][drivers] third-party CI for os-brick changes
by Brian Rosmaita 04 Jan '23

04 Jan '23

To all third-party CI maintainers, As you are aware, cinder third-party CI systems are required to run on all cinder changes. However, the os-brick library used in cinder CI testing is the latest appropriate *released* version of os-brick. Thus, it is possible for changes to be happening in os-brick development that might impact the functionality of your driver. If you aren't testing os-brick changes, you won't find out about these until *after* the next os-brick release, which is bad news all around. Therefore, at last week's cinder midcycle [0], the cinder project team agreed to require that cinder third-party CI systems run on all os-brick changes in addition to all cinder changes. This is a nice-to-have for the current (Zed) development cycle, but will be required in order for a driver to be considered 'supported' in the 2023.1 (Antelope) release [1]. If you have comments or concerns about this policy, please reply on the list to this email or put an item on the agenda [2] for the cinder weekly meeting. [0] https://etherpad.opendev.org/p/cinder-zed-midcycles [1] https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#What_changes… [2] https://etherpad.opendev.org/p/cinder-zed-meetings

2 1

Glance api deployed only on a single controller on multi-controller deployment [kolla]
by A Monster 30 Dec '22

30 Dec '22

I've deployed openstack xena using kolla ansible on a centos 8 stream cluster, using two controller nodes, however I found out after the deployment that glance api is not available in one node, I tried redeploying but I got the same behavior, although the deployment finished without displaying any error. Thank you. Regards

4 4

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

17 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

[neutron] Switching the ML2 driver in-place from linuxbridge to OVN for an existing Cloud
by Christian Rohmann 26 Nov '22

26 Nov '22

Hello openstack-discuss and neutron experts, I'd like to ask for your input and discussion on the idea of changing the ML2 driver for an existing cloud, read: changing a tire while still riding the bike. I actually like to find out if it's feasible to switch from the trusted Linuxbridge driver to the more modern SDN stack of OVN - in place. With all existing user networks, subnets, security groups and (running) instances in the database already. And while I know there a push of migrating from OVS to OVN and a clear migration path documented (https://docs.openstack.org/neutron/latest/ovn/migration.html) but they are much more similar in their data plane. And to get this out of the way: I am not asking to do be able to do this without downtime, interruptions, migrations or any active orchestration of the process. I just want to know all the possible options apart from setting up a new cloud and asking folks to migrate all of their things over... 1) Are the data models of the user managed resources abstract (enough) from the ML2 used? So would the composition of a router, a network, some subnets, a few security group and a few instances in a project just result in a different instantiation of packet handling components, but be otherwise transparent to the user? 2) What could be possible migration strategies? While it might be a little early to think about the actual migration steps. But just to consider more than a full cloud shutdown following a cold start with modified neutron config then using the OVN ML2. I know there is more than just the network and getting a virtual layer 2 network. There are DHCP, DNS and the metadata service and last but not least the gateway / router and the security groups. But if using VXLAN for OVN (as Linuxbridge uses currently) could the shift from one implementation to the other potentially be done node by node? Or project by project by changing the network agents over to nodes already running OVN? If not, is there any other hot cut-over approach that would avoid having to shutdown all the instances, but only cause them some network downtime (until the next DHCP renew or similar?) Has anybody ever done something similar or heard about this being done anywhere? Thanks for your time and input, Christian

3 5

[designate] How to avoid NXDOMAIN or stale data during cold start of a (new) machine
by Christian Rohmann 23 Nov '22

23 Nov '22

Hello openstack-discuss, I have a designate setup using bind9 as the user-serving DNS server. When starting a machine with either very old or no zones at all, NXDOMAIN or other actually stale data is sent out to clients as designate is not done doing an initial full sync / reconciliation. * What is the "proper" way to tackle this cold-start issue and to keep the bind from serving wrong data? ** Did I miss on any options to handle this startup case? * What is the usual runtime for an initial sync that you observe in case the backend DNS server has no zones at all anymore? Regards Christian

2 7

Zun connector for persistent shared files system Manila
by Vaibhav 13 Nov '22

13 Nov '22

Hi, I am using zun for running containers and managing them. I deployed cinder also persistent storage. and it is working fine. I want to mount my Manila shares to be mounted on containers managed by Zun. I can see a Fuxi project and driver for this but it is discontinued now. With Cinder only one container can use the storage volume at a time. If I want to have a shared file system to be mounted on multiple containers simultaneously, it is not possible with cinder. Is there any alternative to Fuxi. is there any other mechanism to use docker Volume support for NFS as shown in the link below? https://docs.docker.com/storage/volumes/ Please advise and give a suggestion. Regards, Vaibhav

2 4

[all][tc] 2023.1 Antelope TC-PTG Planning
by Ghanshyam Mann 20 Oct '22

20 Oct '22

Hello Everyone, As you already know that the 2023.1 cycle virtual PTG will be held between Oct 17th - 21[1]. I have started the preparation for the Technical Committee PTG sessions. Please do the following: 1. Fill the below poll as per your availability. - https://framadate.org/yi8LNQaph5wrirks 2. Add the topics you would like to discuss to the below etherpad. - https://etherpad.opendev.org/p/tc-2023-1-ptg NOTE: this is not limited to TC members only; I would like all community members to fill the doodle poll and, add the topics you would like or want TC members to discuss in PTG. [1] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030041.… -gmann

2 4

[ovn][neutron] RE: OVN BGP Agent query
by Ihtisham ul Haq 18 Oct '22

18 Oct '22

Hi Luis and Daniel, Please see inline response. > From: Daniel Alvarez Sanchez <dalvarez(a)redhat.com> > Sent: 29 September 2022 11:37 > Subject: Re: OVN BGP Agent query > > Hi Ihtisham and Luis, > > On Thu, Sep 29, 2022 at 7:42 AM Luis Tomas Bolivar <ltomasbo(a)redhat.com> wrote: > > Some comments and questions inline > > > > On Tue, Sep 27, 2022 at 1:39 PM Ihtisham ul haq <ihtisham.uh(a)hotmail.com> wrote: > > > Hi Luis, > > > > > > Thanks for your work on the OVN BGP Agent. We are planning > > > to use it in our OVN deployment, but have a question regarding it. > > > > Great to hear! Can you share a bit more info about this environment? like > > openstack version, target workload, etc. We plan to use this with Yoga version. Our workload consist of enterprise users with VMs running on Openstack and connected to their enterprise network via transfer network(to which the customer neutron router is attached to). And we also have public workload but with the ovn-bgp we only want to we want to advertise the former. > > > > > The way our current setup with ML2/OVS works is that our customer VM IP routes > > > are announced via the router IP(of the that customer) to the leaf switch instead of > > > the IP of the host where the neutron BGP agent runs. And then even if the > > > router fails over, the IP of the router stays the same and thus the BGP route > > > doesn't need to be updated. > > > > Is this with Neutron Dynamic Routing? When you say Router IP, do you mean the virtual neutron router and its IP associated with the provider network? What type of IPs are you announcing with BGP? IPs on provider network or on tenant networks (or both)? Yes, that's with Neutron DR agent, and I meant virtual neutron router with IP from the provider network. We announce IPs of our tenant network via the virtual routers external address. > > If the router fails over, the route needs to be updated, doesn't it? Same IP, but exposed in the new location of the router? Correct. > The route to the tenant network doesn't change, ie. > 192.168.0.0 via 172.24.4.100 (this route remains the same regardless of where 172.24.4.100 is). > If there's L2 in the 172.24.4.0 network, the new location of 172.24.4.100 will be learnt via GARP announcement. In our case, this won't happen as we don't have L2 so we expose directly connected routes to overcome this "limitation". Right, in our case we have a stretched L2 transfer network(mentioned above) to which our gateway nodes and customer routers are connected to, so we can advertise the IPs from the tenant network via the virtual router external IP and thus the location of the router isn't relevant in case of failover as its address will be relearned. > In the case of Neutron Dynamic Routing, there's no assumption that everything is L3 so GARPs are needed to learn the new location. > > > > We see that the routes are announced by the ovn-bgp-agent via the host IP(GTW) in our > > > switch peers. If that's the case then how do you make sure that during failover > > > of a router, the BGP routes gets updated with the new host IP(where the router > > > failed over to)? > > > > The local FRR running at each node is in charge of exposing the IPs. For the IPs on the provider network, the traffic is directly exposed where the VMs are, without having to go through the virtual router, so a router failover won't change the route. > > In the case of VMs on tenant networks, the traffic is exposed on the node where the virtual router gateway port is associated (I suppose this is what you refer to with router IP). In the case of a failover the agent is in charge of making FRR to withdraw the exposed routes on the old node, and re-advertise them on the new router IP location > > > > > Can we accomplish the same route advertisement as our ML2/OVS setup, using the ovn-bgp-agent? > > I think this is technically possible, and perhaps you want to contribute that functionality or even help integrating the agent as a driver of Neutron Dynamic Routing? Sounds good, our plan currently is to add this to the ovn-bgp-agent, so we can announce our tenant routes via virtual routers external address on a stretched L2 network, to make it work with our use case. -- Ihtisham ul Haq Diese E Mail enthält möglicherweise vertrauliche Inhalte und ist nur für die Verwertung durch den vorgesehenen Empfänger bestimmt. Sollten Sie nicht der vorgesehene Empfänger sein, setzen Sie den Absender bitte unverzüglich in Kenntnis und löschen diese E Mail. Hinweise zum Datenschutz finden Sie hier<https://www.datenschutz.schwarz>.

3 5

Re: How do I disable replication in swift
by Alvaro Soto 13 Oct '22

13 Oct '22

question: Do you want to delete replicas of old objects? o just disable it for future objects until you get more disk/nodes? for the second did you try to stop the object replicator service? On Fri, Sep 23, 2022 at 9:04 AM Paladox <thomasmulhall410(a)yahoo.com> wrote: > Thanks! But that doesn’t tell you how to disable as the value must be one > or higher? Unless it’s not 1+1 (or what ever you set as the replica value). > > On Thursday, 22 September 2022 at 19:58:41 BST, Alvaro Soto < > alsotoes(a)gmail.com> wrote: > > > Check changing the replica counts > > > https://docs.openstack.org/swift/xena/admin/objectstorage-ringbuilder.html#… > > --- > Alvaro Soto. > > Note: My work hours may not be your work hours. Please do not feel the > need to respond during a time that is not convenient for you. > ---------------------------------------------------------- > Great people talk about ideas, > ordinary people talk about things, > small people talk... about other people. > > On Thu, Sep 22, 2022, 6:54 AM Paladox <thomasmulhall410(a)yahoo.com> wrote: > > Hello, I would like Swift to only have 1 file not any copies of it, how do > I disable replication as you must set the value to 1 when you create the > rings? > > (We don’t have the disk space to have replication / copies of the files) > > -- Alvaro Soto *Note: My work hours may not be your work hours. Please do not feel the need to respond during a time that is not convenient for you.* ---------------------------------------------------------- Great people talk about ideas, ordinary people talk about things, small people talk... about other people.

3 7

[qa][ptg] Virtual PTG Planning
by Martin Kopec 11 Oct '22

11 Oct '22

Hello everyone, here is [1] our etherpad for Antelope PTG. Please, add your topics there if there is anything you would like to discuss / propose ... You can also vote for time slots of our sessions so that they fit your schedule at [2]. We will go with 3 maybe 4 one hour slots, depending on the number of topics. [1] https://etherpad.opendev.org/p/qa-antelope-ptg [2] https://framadate.org/dC2AEBTq8b5rAkvv Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA IM: kopecmartin

1 2

[ptl][tc][ops][ptg] Operator + Developers interaction (operator-hours) slots in 2023.1 Antelope PTG
by Ghanshyam Mann 11 Oct '22

11 Oct '22

Hello Everyone/PTL, As you know, one of the challenges we are facing nowadays is less interaction/feedback from operators. To solve that, OpenStack TC has been discussing it in various forum/places (Board, TC meetings). One of the ideas that came from those discussions was to bring operator and developer together in events like summit, PTG etc. On that idea, we are trying to invite more operators (especially form ops meetup attendees) in next virtual PTG. Idea is to have operators join the project PTG slots. To make it easy for operators and less conflict among projects, TC has booked a few slots as 'operator hours' in different time/day. Currently those are booked as 'operator-hour-placeholder'[1]. Project can convert/reserve them to their project operator-hour, for example 'operator-hour-nova'. How project can reserve/book these 'operator hour' (Action item for projects PTL/PTG planner): ----------------------------------------------------------------------------------------------------------------- 1. Request Kendal or Fungi (in #openinfra-events IRC channel) to register the new track 'operator-hour-<your project name>' for example, 'operator-hour-nova' 2. Once track is registered, pick one of the available 'operator-hour-placeholder' slot and book it with newly registered track 'operator-hour-<your project name>'. For example #operator-hour-nova book essex-WedB1 * Idea to book these slots as 'operator-hour-<your project name>' is to give operators a easy way to find and join. Otherwise it will be difficult for them to find such slot/time from etherpads. We request every projects to book at least one 'operator hours' slot for operators to join your PTG slot. Ping me in #openstack-tc or #openinfra-events IRC channel for any query. [1] https://ptg.opendev.org/ptg.html -gmann

1 1

[Ceilometer] Pollster cannot get RadosGW metrics when API endpoints are based on URL instead of port number
by Taltavull Jean-François 10 Oct '22

10 Oct '22

Hi All, In our OpenStack deployment, API endpoints are defined by using URLs instead of port numbers and HAProxy forwards requests to the right bakend after having ACLed the URL. In the case of our object-store service, based on RadosGW, the internal API endpoint is "https://<FQDN>/object-store/swift/v1/AUTH_<tenant_id>" When Ceilometer RadosGW pollster tries to connect to the RadosGW admin API with the object-store internal endpoint, the URL becomes https://<FQDN>/admin, as shown by HAProxy logs. This URL does not match any API endpoint from HAProxy point of view. The line of code that rewrites the URL is this one: https://opendev.org/openstack/ceilometer/src/branch/stable/wallaby/ceilomet… What would you think of adding a mechanism based on new Ceilometer configuration option(s) to control the URL rewriting ? Our deployment characteristics: - OpenStack release: Wallaby - Ceph and RadosGW version: 15.2.16 - deployment tool: OSA 23.2.1 and ceph-ansible Best regards, Jean-Francois

2 23

[nova][placement] add your PTG topics before Oct-06 please !
by Sylvain Bauza 06 Oct '22

06 Oct '22

Hi folks, as I said in the nova meeting, I'd like to create an agenda for our PTG topics. Given the PTG is in 3 weeks, please provide your topics you'd like to discuss at the PTG in [1] so I could look at them and try to provide an agenda for them. Eventually, I'd love to have most of the topics by Oct 6th as I said in the title so the agenda would be on the Friday Oct 7th. Also, if you can't be in the Nova PTG sessions for all the PTG schedule (between Tues and Fri for Nova), just add in the topic when you would like to be around. Thanks, -Sylvain [1] https://etherpad.opendev.org/p/nova-antelope-ptg

1 1

[Swift][Ussuri] Erasure Coding Quarantines
by Reid Guyett 05 Oct '22

05 Oct '22

Hello, I'm not sure if it is related, but I am testing reimaging a node from Ubuntu 18.04 to 20.04 (Cloud Archive Ussuri 2.25.1 to Focal Repo Ussuri 2.25.2) in a 3-node cluster. I have a lot of servers to upgrade, and the environments will be mixed for a while, so I have left this mixed for a week. Now the 18.04 servers are starting to accumulate quarantined EC objects. The 20.04 server has log messages indicating that it is unable to get enough responses from the reconstructor. The 18.04 servers have a couple EC messages. "...liberasurecode[30807]: Invalid fragment header information!" followed by "...object-server: Quarantined object /srv/node/d9/objects-4/10321/b2e/50a3dce515aafc6f222824ec5c7dfb2e/1664002866.33100#8#d.data: Invalid EC metadata at offset 0x0 Is there any thing you can think of that would cause this issue? My steps to reproduce: 1. Create a container in an EC policy 2. Upload object to EC container 3. Wait a bit of time (It looks like the object-server is quarantining but not sure on the trigger) 4. Try to download the file and it will give a 504 Looking at python3-swift dependencies and the package versions I thought may affect this: 20.04 libjerasure2 = 2.0.0+2017.04.10.git.de1739cc84-1 python3-pyeclib = 1.6.0-6build1 python3-xattr = 0.9.6-1.1 18.04 libjerasure2 = 2.0.0+2017.04.10.git.de1739cc84-1 python3-pyeclib = 1.3.1-1ubuntu3 python3-xattr = 0.9.2-0ubuntu1 Thanks! Reid Important Notice: This email is intended to be received only by persons entitled to receive the confidential and legally privileged information it presumptively contains, and this notice constitutes identification as such. Any reading, disclosure, copying, distribution or use of this information by or to someone who is not the intended recipient, is prohibited. If you received this email in error, please notify us immediately at legal(a)kaseya.com, and then delete it. To opt-out of receiving emails Please click here<https://info.kaseya.com/email-subscription-center.html>. The term 'this e-mail' includes any and all attachments.

3 6

[kolla-ansible] How to recover from unfinished upgrade
by wodel youchi 05 Oct '22

05 Oct '22

Hi, I am testing the upgrade from xena to yoga and I made a mistake in globals.yml, I forgot to specify the correct name of gnocchi ceph pool, so my deployment went wrong. I interrupted the deployment Ctrl+C I corrected the mistake, then I restarted the upgrade and it got stuck somewhere else, but I couldn't find where, I interrupted then restarted the deployment again and it got stuck at the same place. My questions : - Is there a way to rollback the upgrade in case of a problem, then start over? - What is the best way to restart a broken upgrade process? Regards.

2 2

[TripleO] TripleO Antelope PTG Topics
by Rabi Mishra 05 Oct '22

05 Oct '22

Hi All, Please add your session proposals to this etherpad[1]. We'll reserve time allocation based on proposed topics and work out a schedule in the coming weeks. [1] https://etherpad.opendev.org/p/tripleo-antelope-topics -- Regards, Rabi Mishra

2 4

[neutron] PTG topics and scheduling
by Rodolfo Alonso Hernandez 03 Oct '22

03 Oct '22

Hello all: Based on the schedule polls results, I've booked the Neutron meetings from Tuesday to Thursday in Mitaka channel [1], from 13UTC to 16UTC. Of course, if that is not enough, we can always use Friday to continue any pending conversation. The operator hour (actually 2), will be on Friday (pending for reservation), from 13UTC to 15UTC. Please continue adding any topic you want to discuss in the Neutron etherpad [2]. There is a specific section for the Nova-Neutron cross-team meeting. If you have any doubt or question, do not hesitate to let me know (IRC: ralonsoh, mail: ralonsoh(a)redhat.com) You can also ping any core reviewer in #openstack-neutron channel. See you in a few weeks! [1]https://ptg.opendev.org/ptg.html [2]https://etherpad.opendev.org/p/neutron-antelope-ptg

3 3

[all][tc] What's happening in Technical Committee: summary 2022 Sept 30: Reading: 5 min
by Ghanshyam Mann 01 Oct '22

01 Oct '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Sept 29. Most of the meeting discussions are summarized in this email. Meeting logs are available @ https://meetings.opendev.org/meetings/tc/2022/tc.2022-09-29-15.00.log.html * Next TC weekly meeting will be a video call on Oct 6 Thursday at 15:00 UTC, feel free to add the topic on the agenda[1] by Oct 5. 2. What we completed this week: ========================= * Goal proposal of 'Migrating CI/CD testing from Ubuntu 20.04 to 22.04' is merged [2] * 2023.1 cycle leaderless projects: PTL appointment done for below projects: ** Adjutant[3] ** Keystone[4] ** Masakari[5] ** OpenStack_Charms[6] ** Sahara[7 ** Senlin[8] ** Swift[9] ** Venus[10] 3. Activities In progress: ================== TC Tracker for Zed cycle ------------------------------ * Zed tracker etherpad includes the TC working items[11], Five are completed and other items are in-progress. Open Reviews ----------------- * Five open reviews for ongoing activities[12]. Dedicating Zed release to Ilya Etingof -------------------------------------------- As you might know, there is sad news of Ilya Etingof (Ironic contributor) passed away on Aug 10[13] and we will be dedicating the Zed release to Ilya[14] New community-wide goal "Migration CI/CD to Ubuntu 22.04" -------------------------------------------------------------------------------------- The goal proposal is merged[15]. Dmitriy will propose this goal to be selected for 2023.1 cycle. 2023.1 cycle Leaderless projects & TC Chair ---------------------------------------------------- * PTL appointments for 8 projects are done. Zun project PTL appointment is under review[16]. * TC Chair: TC members are in the progress to select the chair for the next term. 2023.1 cycle TC PTG planning ------------------------------------ * JayF sent the ICS invite of TC PTG slots on ML[17] * Etherpads to add the topics: ** https://etherpad.opendev.org/p/tc-2023-1-ptg ** https://etherpad.opendev.org/p/tc-leaders-interaction-2023-1 * I sent an email about the 'Operator Hours' slots in this PTG, please check and reserve the operator hour slot for your project[18] 2021 User Survey TC Question Analysis ----------------------------------------------- No update on this. The survey summary is up for review[19]. Feel free to check and provide feedback. Fixing Zuul config error ---------------------------- We discussed the Zuul config error for zuul 'queue' syntex[20]. Also added it in the zuul config error etherpad[21 ]. Requesting projects have zuul config errors in their jobs to look into those and fix them asap. As most of the errors occur while project renaming/retiring, I am adding a separate step about it in the project rename/retiring process[22]. 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[23]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [24] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/858690 [3] https://review.opendev.org/c/openstack/governance/+/858967 [4] https://review.opendev.org/c/openstack/governance/+/858969 [5] https://review.opendev.org/c/openstack/governance/+/858974 [6] https://review.opendev.org/c/openstack/governance/+/858973 [7] https://review.opendev.org/c/openstack/governance/+/858975 [8] https://review.opendev.org/c/openstack/governance/+/858976 [9] https://review.opendev.org/c/openstack/governance/+/858978 [10] https://review.opendev.org/c/openstack/governance/+/858979 [11] https://etherpad.opendev.org/p/tc-zed-tracker [12] https://review.opendev.org/q/projects:openstack/governance+status:open [13] https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030062.… [14] https://review.opendev.org/c/openstack/governance/+/859464 [15] https://review.opendev.org/c/openstack/governance/+/858690 [16] https://review.opendev.org/c/openstack/governance/+/858980 [17] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0306… [18] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0303… [19] https://review.opendev.org/c/openstack/governance/+/836888 [20] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/0305… [21] https://etherpad.opendev.org/p/zuul-config-error-openstack [22] https://review.opendev.org/c/openstack/project-team-guide/+/859886 [23] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [24] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[Diversity] Diversity and Inclusion WG meeting reminder
by Amy Marrich 30 Sep '22

30 Sep '22

The D&I WG will be meeting Monday at 15:00 UTC. The meeting will be held on video at https://meetpad.opendev.org/osf-diversity-and-inclusion and the agenda can be found at https://etherpad.openstack.org/p/diversity -wg-agenda. Thanks, Amy (spotz)

1 0

[release] Release countdown for week R+0, Oct 3 - 7
by Előd Illés 30 Sep '22

30 Sep '22

Development Focus ----------------- We will be releasing the coordinated OpenStack Zed release next week, on October 5th, 2022. Thanks to everyone involved in the Zed cycle! We are now in pre-release freeze, so no new deliverable will be created until final release, unless a release-critical regression is spotted. Otherwise, teams attending the virtual PTG should start to plan what they will be discussing there, by creating and filling team etherpads. You can access the list of PTG etherpads at: http://ptg.openstack.org/etherpads.html General Information ------------------- On release day, the release team will produce final versions of deliverables following the cycle-with-rc release model, by re-tagging the commit used for the last RC. A patch doing just that will be proposed. PTLs and release liaisons should watch for that final release patch from the release team. While not required, we would appreciate having an ack from each team before we approve it on the 5th, so that their approval is included in the metadata that goes onto the signed tag. Upcoming Deadlines & Dates -------------------------- Final Zed release: October 5th, 2022 Virtual PTG: October 17-21, 2022 Előd Illés irc: elodilles

1 0

TLS error when cloning https://opendev.org/openstack/devstack
by Neil Jerram 30 Sep '22

30 Sep '22

Anyone else seeing this? neil@glaurung:~/tt$ git clone https://opendev.org/openstack/devstack Cloning into 'devstack'... remote: Enumerating objects: 28589, done. remote: Counting objects: 100% (28589/28589), done. remote: Compressing objects: 100% (9638/9638), done. error: RPC failed; curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet. fatal: early EOF fatal: fetch-pack: invalid index-pack output Best wishes, Neil -- Neil Jerram Principal Software Engineer Tigera neil(a)tigera.io | @neiljerram <http://twitter.com/neiljerram> Follow Tigera: Blog <https://blog.tigera.io/> | Twitter <https://twitter.com/tigeraio> | LinkedIn <https://www.linkedin.com/company/tigera/> Security and observability for containers, Kubernetes, and cloud <https://tigera.io/>

5 14

Oracle Linux 6 VM volume performance
by Quang Long 30 Sep '22

30 Sep '22

Hi Openstack-users, I am having a problem with I/O performance on VM running Oracle Linux 6, I/O throughput on VM Oracle Linux 6 is much lower than VM using another OS (Ubuntu, CentOS). - VM Oracle Linux 6: throughput 40 MBps https://prnt.sc/buKscX_qEtcF - Other VM: throughput 113 MBps https://prnt.sc/IRhBUPrGgLOy - Test tool: dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync; rm -f test My Enviroment: - Openstack: Ussuri - Ceph: Octopus 15.2.8 - Compute: CentOS8_x86_64, kernel: 4.18.0-240.15.1.el8_3.x86_64 - KVM: qemu-kvm-5.2.0-16.el8.x86_64 - VM Oracle linux6: kernel-uek-4.1.12-124.42.3.el6uek.x86_64 I think because the kernel of Oracle Linux 6 is too old, maybe an older KVM version could support it, and now KVM does not optimize for this OS. Could you guy can help me with this? -- *Lê Quang Long* 0942.533.683 | 0977.116.502

2 2

Oracle Linux 6 VM disk performance
by Quang Long 30 Sep '22

30 Sep '22

Hi Openstack-users, I am having a problem with I/O performance on VM running Oracle Linux 6, I/O throughput on VM Oracle Linux 6 is much lower than VM using another OS (Ubuntu, CentOS). - VM Oracle Linux 6: throughput 40 MBps https://prnt.sc/buKscX_qEtcF - Other VM: throughput 113 MBps https://prnt.sc/IRhBUPrGgLOy - Test tool: dd bs=1M count=1024 if=/dev/zero of=test conv=fdatasync; rm -f test My Enviroment: - Openstack: Ussuri - Ceph: Octopus 15.2.8 - Compute: CentOS8_x86_64, kernel: 4.18.0-240.15.1.el8_3.x86_64 - KVM: qemu-kvm-5.2.0-16.el8.x86_64 - VM Oracle linux6: kernel-uek-4.1.12-124.42.3.el6uek.x86_64 I think because the kernel of Oracle Linux 6 is too old, maybe an older KVM version could support it, and now KVM does not optimize for this OS. Could you guy can help me with this? -- *Lê Quang Long* 0942.533.683 | 0977.116.502

1 0

Live Migration Issues
by Alexander Dibbo - STFC UKRI 30 Sep '22

30 Sep '22

Hi All, I'm having a few issues with live migration at the moment. This is an openstack train deployed with rdo packages. 1. when migrating some VMs the migration succeeds but the VM doesn't move and the following error can be found in the nova logs with nothing that seems to correspond in the neutron logs: 2022-09-30 11:04:04.069 716669 INFO nova.compute.manager [-] [instance: c10d1d9e-2baf-4ab5-ba3a-2f60f521aea6] Took 76.49 seconds for pre_live_migration on destination host hv548.nubes.rl. ac.uk. 2022-09-30 11:04:04.720 716669 ERROR nova.virt.libvirt.driver [-] [instance: c10d1d9e-2baf-4ab5-ba3a-2f60f521aea6] Live Migration failure: 'fa:ca:ad:1f:71:41' 2. When migrating some VMs the migration is marked as complete and the VM is moved from the source to the destination hypervisor but nova keeps the migrating state and doesn't update the host or the node fields. The following error is found in nova with no corresponding error that I can find in neutron. The config is the same across all hypervisors. 2022-09-13 10:37:23.709 12387 ERROR nova.network.neutronv2.api [req-ee51a8b4-911c-4f92-860b-9d6a7a24c786 27be800439c244c1bd742ff056cf700c 4de86830e89b4a46b590536571b6ccd4 - 38372510d9bb4ac7916178b062d387de 38372510d9bb4ac7916178b062d387de] Neutron client was not able to generate a valid admin token, please verify Neutron admin credential located in nova.conf: neutronclient.common.exceptions.Unauthorized: 401-{'error': {'message': 'The request you have made requires authentication.', 'code': 401, 'title': 'Unauthorized'}} 2022-09-13 10:37:23.845 12387 ERROR oslo_messaging.rpc.server [req-ee51a8b4-911c-4f92-860b-9d6a7a24c786 27be800439c244c1bd742ff056cf700c 4de86830e89b4a46b590536571b6ccd4 - 38372510d9bb4ac7916178b062d387de 38372510d9bb4ac7916178b062d387de] Exception during message handling: nova.exception.NeutronAdminCredentialConfigurationInvalid: Networking client is experiencing an unauthorized exception. Regards Alexander Dibbo - Cloud Architect / Cloud Operations Group Leader For STFC Cloud Documentation visit https://stfc-cloud-docs.readthedocs.io<https://stfc-cloud-docs.readthedocs.io/> To raise a support ticket with the cloud team please email cloud-support(a)stfc.ac.uk<mailto:cloud-support@stfc.ac.uk> To receive notifications about the service please subscribe to our mailing list at: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=STFC-CLOUD To receive fast notifications or to discuss usage of the cloud please join our Slack: https://stfc-cloud.slack.com/ This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses.

1 0

[all] Skip level upgrades (SLURP) grenade job
by Slawek Kaplonski 30 Sep '22

30 Sep '22

Hi, As You may know there some time ago TC merged resolution about release cadence adjustment [1]. According to that resolution starting from 2023.1 (Antelope) will be first "SLURP" release. That means that upgrade directly from 2023.1 to 2024.1 ("C") needs to be supported so projects will need to run "skip-level" grenade job [2]. To start that effort and see how it works currently and what needs to be done/fixed by teams we (TC) would like to ask teams to add such job to CI in the current (2023.1) cycle already. That job will test upgrade from Yoga to master (2023.1). You can refer to the Manila job [3] and do something similar in Your project. If that job will cause some problems, You can make it non-voting temporary and work on fix it but we highly recommend to have this job voting already. If You would have any questions, please reach out to us here or on the #openstack-tc IRC channel. [1] https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad… [2] https://github.com/openstack/grenade/blob/b1cd7a1866ee7d17392bd9896db6060d4… [3] https://review.opendev.org/c/openstack/manila/+/859875 -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[Image Encryption] No meeting on Monday
by Josephine Seifert 30 Sep '22

30 Sep '22

Hi, Monday the 3. of October is a national holiday. So there will not be a meeting for the Image Encryption pop up team. cheers, Luzi

1 0

[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 29 Sep '22

29 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 29 Sep '22

29 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

[cinder] Bug Report 09-28-2022
by Sofia Enriquez 28 Sep '22

28 Sep '22

This is a bug report from 09-21-2022 to 09-28-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Low - https://bugs.launchpad.net/cinder/+bug/1990053 "Cinder NFS backend with image-volume cache creates volumes with the wrong size." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1990846 "NetApp FC: Not filterings WWPNs correctly in multiple HA pair deployments." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1990946 "Dell PowerFlex: Size shown for a volume doesn't match powerflex backend allocation." Unassigned. - https://bugs.launchpad.net/cinder/+bug/1991068 "Duplicate config option barbican in tempest plugins cinder and barbican." Unassigned. - https://bugs.launchpad.net/os-brick/+bug/1939390 "Missing dependency: lsscsi." Unassigned. Incomplete - https://bugs.launchpad.net/os-brick/+bug/1990825 "Should wait for all devices to appear?." Cheers, -- 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

Regarding Magnum configuration on Xena Openstack
by Adivya Singh 27 Sep '22

27 Sep '22

Hi Team, Can we have standard inputs to put and test to implement Containerization in Xena Openstack installed using ansible Regards Adivya Singh

2 3

[cinder] This week's meeting will be in video+IRC
by Rajat Dhasmana 27 Sep '22

27 Sep '22

Hello Argonauts, As we keep last meeting of the month in video + IRC mode, this week's meeting (tomorrow) will be held in video + IRC mode with details as follows: Date: 28th September, 2022 Time: 1400 UTC Meeting link: https://bluejeans.com/556681290 IRC Channel: #openstack-meeting-alt Make sure you're connected to both the bluejeans meeting and IRC since we do roll call and also discuss topics on IRC (if the author is more comfortable in written format). Thanks and regards Rajat Dhasmana

1 0

Unable to create access rules 'state:error' | Wallaby | Tripelo | NetApp
by Swogat Pradhan 27 Sep '22

27 Sep '22

Hi, When i am trying to create access rule for manila share, the rules are created in error state. Here is the manila share log: 2022-09-23 19:03:58.557 43 INFO manila.share.manager [req-ef21b41e-efc6-4b7d-9214-3de878d50d7f - - - - -] Updating share status 2022-09-23 19:04:01.720 26 INFO manila.share.manager [req-3d66c534-a782-414b-a0a7-2bdd57f57b8f - - - - -] Updating share status 2022-09-23 19:04:58.554 43 INFO manila.share.manager [req-ef21b41e-efc6-4b7d-9214-3de878d50d7f - - - - -] Updating share status 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server [req-5f035b4a-7dc8-4e61-bbd5-d38d4b81a00d c1905e3c5a374924980e851840e7f028 5d922243077045c48fe4b075e386551b - - -] Exception during message handling: manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed. Reason - 15661:entry doesn't exist 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 216, in wrapped 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/utils.py", line 568, in wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return func(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 3965, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server_id=share_server_id) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/manager.py", line 3981, in update_access_for_instances 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 302, in update_access_rules 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 341, in _update_access_rules 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/access.py", line 409, in _update_rules_through_share_driver 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server share_server=share_server 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/cluster_mode/drv_single_svm.py", line 104, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server delete_rules, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/cluster_mode/lib_base.py", line 2347, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server helper.update_access(share, share_name, access_rules) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/base.py", line 36, in wrapped_func 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return source_func(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py", line 391, in inner 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/base.py", line 34, in source_func 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/nfs_cmode.py", line 115, in update_access 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server auth_methods = self._get_auth_methods() 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/protocols/nfs_cmode.py", line 222, in _get_auth_methods 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server kerberos_enabled = self._client.is_kerberos_enabled() 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/utils.py", line 112, in trace_wrapper 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = f(self, *args, **kwargs) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/client_cmode.py", line 1896, in is_kerberos_enabled 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server result = self.send_request('kerberos-config-get', api_args) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/client_base.py", line 90, in send_request 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server use_zapi=use_zapi) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/api.py", line 710, in invoke_successfully 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server na_element, api_args=api_args, enable_tunneling=enable_tunneling) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/manila/share/drivers/netapp/dataontap/client/api.py", line 380, in invoke_successfully 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server raise NaApiError(code, msg) 2022-09-23 19:04:59.447 43 ERROR oslo_messaging.rpc.server manila.share.drivers.netapp.dataontap.client.api.NaApiError: NetApp API failed. Reason - 15661:entry doesn't exist Please suggest how to mitigate this issue. With regards, Swogat Pradhan

2 2

[tacker] Critical bug report and backport the fix
by Yuta Kazato 27 Sep '22

27 Sep '22

Hi tacker team, As you know, new bug report #1990793 [1] related to K8s resource name and v2 API is submitted by Masaki. The bug will appear if K8s resource name contains `-`. I think this is a critical issue because users often set resource names that contain `-`. Fortunately, the fix patch [2] has already been submitted. I suggest that we should backport the fix patch to the stable/zed branch before Zed release. What do you think? [1] https://bugs.launchpad.net/tacker/+bug/1990793 [2] https://review.opendev.org/c/openstack/tacker/+/859206 Yuta -- Yuta Kazato (風戸雄太) NTT Network Innovation Center. tel: +81-422-59-6754 mail: yuta.kazato.nw(a)hco.ntt.co.jp

3 2

Create the TripleO container images using the command in Xena
by Suranga Prabhath 27 Sep '22

27 Sep '22

Hi All, I.m going to install OpenStack Xena on CentOS 8.5. I'm following the TripleO in RDO Xena Release. I followed the RDO guide & enable the required packages. Package installation is successful, but the pulling of the triple container imagers using the command was unsuccessful. Here is the command I use. openstack tripleo container image build --base ubi8 --debug --distro centos \ --namespace tripleoxena --prefix openstack --tag cloudsig-xena \ --push --registry 172.22.1.10::8787 \ --volume /etc/yum.repos.d:/etc/distro.repos.d:z --volume /etc/pki/rpm-gpg:/etc/pki/rpm-gpg:z --volume /etc/dnf/vars:/etc/dnf/vars:z \ --work-dir ~/workdir After executing the above command error was received & I attach it to this mail. Please provide me with a solution for this. -- Thanks & Regards, *Suranga Prabhath,* System Administrator hSenid Software International *Sri Lanka* *M* : +94 00 000 0000 *P* : +94 11 268 3751 *F* : +94 11 268 3951 *Singapore* *M* : +65 00 000 000 *P* : +65 65 332 140 *F* : +65 62 910 023 <http://www.hsenid.com/> <http://www.hsenidmobile.com/> <https://www.facebook.com/hSenid.Software.International/> <https://twitter.com/hsenid_biz> <https://www.linkedin.com/company/hsenid-business-solutions> <https://www.youtube.com/user/hsenidbiz> *www.hSenid.com* <http://www.hsenid.com/> <https://www.google.com/url?q=http://www.hsenidmobile.com/&source=gmail-html…> *Disclaimer*: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. The content and opinions contained in this email are not necessarily those of hSenid Mobile Solutions. If you have received this email in error please contact the sender.

1 0