December 2021 - 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

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

06 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

[all] Dynamic Zuul results table in Gerrit 3
by Radosław Piliszek 04 Aug '22

04 Aug '22

Hello Fellow OpenStack and OpenDev Folks! TL;DR click on [3] and enjoy. I am starting this thread to not hijack the discussion happening on [1]. First of all, I would like to thank gibi (Balazs Gibizer) for hacking a way to get the place to render the table in the first place (pun intended). I have been a long-time-now user of [2]. I have improved and customised it for myself but never really got to share back the changes I made. The new Gerrit obviously broke the whole script so it was of no use to share at that particular state. However, inspired by gibi's work, I decided to finally sit down and fix it to work with Gerrit 3 and here it comes: [3]. Works well on Chrome with Tampermonkey. Not tested others. I hope you will enjoy this little helper (I do). I know the script looks super fugly but it generally boils down to a mix of styles of 3 people and Gerrit having funky UI rendering. Finally, I'd also like to thank hrw (Marcin Juszkiewicz) for linking me to the original Michel's script in 2019. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019051… [2] https://opendev.org/x/coats/src/commit/444c95738677593dcfed0cfd9667d4c4f0d5… [3] https://gist.github.com/yoctozepto/7ea1271c299d143388b7c1b1802ee75e Kind regards, -yoctozepto

5 7

[all] PyCharm Licenses Renewed till July 2021
by Swapnil Kulkarni 13 Jul '22

13 Jul '22

Hello, Happy to inform you the open source developer license for Pycharm has been renewed for 1 additional year till July 2021. Best Regards, Swapnil Kulkarni coolsvap at gmail dot com

8 13

Nova not updating to new size of an extended in-use / attached cinder volume (Ceph RBD) to guest
by Christian Rohmann 28 Jun '22

28 Jun '22

Hello Openstack-Discuss, after some digging I found out that cinder learned to resize attached (in-use) volumes quite a while ago with the introduction of the initial "extend 'in-use' volume" feature: https://review.opendev.org/c/openstack/cinder/+/454287/ The support was then extended to also cover Ceph RBD backed volumes with: https://review.opendev.org/c/openstack/nova/+/613039/ Since this is only about the cinder part, I was wondering if nova would ever find out and would actively rescan the device / volume and quintessentially present an increased new size to the guest. Apparently this is where a certain volume-extended event comes into play: https://review.opendev.org/c/openstack/nova/+/454322/ that is to be emitted by cinder when a volume had been extened. I then went head and tried this with the openstack cli (as Horizon does not seem to support / offer to resize in-use volumes. I run Openstack Train with Ceph RBD as storage. First I ran into an issue with the openstack cli (https://bugs.launchpad.net/cinder/+bug/1871759/comments/2 <https://bugs.launchpad.net/cinder/+bug/1871759/comments/2>) but using cinder extend $volumeid $newsize I was able to resize in-use volumes just fine. The only thing missing was the propagation to the guest. I played around with SCSI rescans, but that did not work, reboots also failed to do anyting in this regards. Stopping and starting the VM did work, but why having the capability to online-resize an attached volume when not being able to resize the guest volume as well? Apparently there seems to be an old and somewhat similar observation / bug with https://bugs.launchpad.net/nova/+bug/1369465 So I was simply wondering if this is expected to be working? Are there any special settings / options I need to set to enable this feature? Thanks and with kind regards Christian

4 9

[oslo] Propose to EOL stable/queens, stable/rocky on all the oslo scope
by Herve Beraud 24 Jun '22

24 Jun '22

Hi, On our last meeting of the oslo team we discussed the problem with broken stable branches (rocky and older) in oslo's projects [1]. Indeed, almost all these branches are broken. Előd Illés kindly generated a list of periodic-stable errors on Oslo's stable branches [2]. Given the lack of active maintainers on Oslo and given the current status of the CI in those branches, I propose to make them End Of Life. I will wait until the end of month for anyone who would like to maybe step up as maintainer of those branches and who would at least try to fix CI of them. If no one will volunteer for that, I'll EOLing those branches for all the projects under the oslo umbrella. Let us know your thoughts. Thank you for your attention. [1] https://meetings.opendev.org/meetings/oslo/2021/oslo.2021-10-04-15.00.log.t… [2] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023939.html -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

5 5

[TripleO] Core team cleanup
by James Slagle 30 Mar '22

30 Mar '22

Hello, I took a look at our core team, "tripleo-core" in gerrit. We have a few individuals who I feel have moved on from TripleO in their focus. I looked at the reviews from stackalytics.io for the last 180 days[1]. These individuals have less than 6 reviews, which is about 1 review a month: Bob Fournier Dan Sneddon Dmitry Tantsur Jiří Stránský Juan Antonio Osorio Robles Marius Cornea These individuals have publicly expressed that they are moving on from TripleO: Michele Baldessari wes hayutin I'd like to propose we remove these folks from our core team, while thanking them for their contributions. I'll also note that I'd still value +1/-1 from these folks with a lot of significance, and encourage them to review their areas of expertise! If anyone on the list plans to start reviewing in TripleO again, then I also think we can postpone the removal for the time being and re-evaluate later. Please let me know if that's the case. Please reply and let me know any agreements or concerns with this change. Thank you! [1] https://www.stackalytics.io/report/contribution?module=tripleo-group&projec… -- -- James Slagle --

5 6

[all][tc] Relmgt team position on release cadence
by Thierry Carrez 14 Feb '22

14 Feb '22

Hi everyone, The (long) document below reflects the current position of the release management team on a popular question: should the OpenStack release cadence be changed? Please note that we only address the release management / stable branch management facet of the problem. There are other dimensions to take into account (governance, feature deprecation, supported distros...) to get a complete view of the debate. Introduction ------------ The subject of how often OpenStack should be released has been regularly debated in the OpenStack community. OpenStack started with a 3-month release cycle, then switched to 6-month release cycle starting with Diablo. It is often thought of a release management decision, but it is actually a much larger topic: a release cadence is a trade-off between pressure to release more often and pressure to release less often, coming in from a lot of different stakeholders. In OpenStack, it is ultimately a Technical Committee decision. But that decision is informed by the position of a number of stakeholders. This document gives historical context and describes the current release management team position. The current trade-off --------------------- The main pressure to release more often is to make features available to users faster. Developers get a faster feedback loop, hardware vendors ensure software is compatible with their latest products, and users get exciting new features. "Release early, release often" is a best practice in our industry -- we should generally aim at releasing as often as possible. But that is counterbalanced by pressure to release less often. From a development perspective, each release cycle comes with some process overhead. On the integrators side, a new release means packaging and validation work. On the users side, it means pressure to upgrade. To justify that cost, there needs to be enough user-visible benefit (like new features) in a given release. For the last 10 years for OpenStack, that balance has been around six months. Six months let us accumulate enough new development that it was worth upgrading to / integrating the new version, while giving enough time to actually do the work. It also aligned well with Foundation events cadence, allowing to synchronize in-person developer meetings date with start of cycles. What changed ------------ The major recent change affecting this trade-off is that the pace of new development in OpenStack slowed down. The rhythm of changes was divided by 3 between 2015 and 2021, reflecting that OpenStack is now a mature and stable solution, where accessing the latest features is no longer a major driver. That reduces some of the pressure for releasing more often. At the same time, we have more users every day, with larger and larger deployments, and keeping those clusters constantly up to date is an operational challenge. That increases the pressure to release less often. In essence, OpenStack is becoming much more like a LTS distribution than a web browser -- something users like moving slow. Over the past years, project teams also increasingly decoupled individual components from the "coordinated release". More and more components opted for an independent or intermediary-released model, where they can put out releases in the middle of a cycle, making new features available to their users. This increasingly opens up the possibility of a longer "coordinated release" which would still allow development teams to follow "release early, release often" best practices. All that recent evolution means it is (again) time to reconsider if the 6-month cadence is what serves our community best, and in particular if a longer release cadence would not suit us better. The release management team position on the debate -------------------------------------------------- While releasing less often would definitely reduce the load on the release management team, most of the team work being automated, we do not think it should be a major factor in motivating the decision. We should not adjust the cadence too often though, as there is a one-time cost in switching our processes. In terms of impact, we expect that a switch to a longer cycle will encourage more project teams to adopt a "with-intermediary" release model (rather than the traditional "with-rc" single release per cycle), which may lead to abandoning the latter, hence simplifying our processes. Longer cycles might also discourage people to commit to PTL or release liaison work. We'd probably need to manage expectations there, and encourage more frequent switches (or create alternate models). If the decision is made to switch to a longer cycle, the release management team recommends to switch to one year directly. That would avoid changing it again anytime soon, and synchronizing on a calendar year is much simpler to follow and communicate. We also recommend announcing the change well in advance. We currently have an opportunity of making the switch when we reach the end of the release naming alphabet, which would also greatly simplify the communications around the change. Finally, it is worth mentioning the impact on the stable branch work. Releasing less often would likely impact the number of stable branches that we keep on maintaining, so that we do not go too much in the past (and hit unmaintained distributions or long-gone dependencies). We currently maintain releases for 18 months before they switch to extended maintenance, which results in between 3 and 4 releases being maintained at the same time. We'd recommend switching to maintaining one-year releases for 24 months, which would result in between 2 and 3 releases being maintained at the same time. Such a change would lead to longer maintenance for our users while reducing backporting work for our developers. -- Thierry Carrez (ttx) On behalf of the OpenStack Release Management team

15 45

[magnum] dropping mesos code
by Mohammed Naser 01 Feb '22

01 Feb '22

Hi there, Does it make sense for us to drop the Mesos driver code from the code base? I don't know of anyone that actually uses it and I believe it's likely not been tested for years. Mohammed -- Mohammed Naser VEXXHOST, Inc.

4 5

[nova][powervm][zvm] Time to mark powervm and zvm drivers as deprecated for removal?
by Stephen Finucane 28 Jan '22

28 Jan '22

I've had a PR open against the pypowervm library for over a fortnight now [1] with no activity. This has prompted me to go looking into the state of the powervm driver and what I've found isn't great. It doesn't seem there has been any feature development on the driver for many years, and the last change I can see that wasn't simply of a case of "I need to do this to get tests to pass" was over three years ago [2]. The CI also doesn't appear to have been touched in years. The situation for zvm isn't any better. The last functional change to that driver was nearly 2 years ago and I wasn't able to spot any CI running (though it's possible I just missed this). This means the powervm and zvm drivers stand out from the other non-libvirt drivers in-tree, each of which are getting at least some activity (albeit out- of-tree for Hyper-V, from what I recall). It also begs the question: are these drivers something we want to keep around? If we do, how are we going to maintain them long term? If not, how aggressive should we be in removing that now dead code? I'll open patches to mark both powervm and zvm as deprecated shortly so that, assuming nothing changes in the interim, we can look to remove it early in the Z cycle. Please respond here or on the reviews if you have concerns. Stephen [1] https://github.com/powervm/pypowervm/pull/17 [2] Change ID I89ad36f19672368a1f795e1f29c5af6368ccfeec

1 1

Re: Re: [ops] [kolla] RabbitMQ High Availability
by Albert Braden 25 Jan '22

25 Jan '22

Replying from my home email because I've been asked to not email the list from my work email anymore, until I get permission from upper management. I'm not sure I follow. I was planning to add 2 lines to etc/kolla/config/global.conf: [oslo_messaging_rabbit] amqp_durable_queues = False Is that not sufficient? What is involved in configuring dedicated control exchanges for each service? What would that look like in the config? From: Herve Beraud <hberaud(a)redhat.com> Sent: Thursday, December 9, 2021 2:45 AM To: Bogdan Dobrelya <bdobreli(a)redhat.com> Cc: openstack-discuss(a)lists.openstack.org Subject: [EXTERNAL] Re: [ops] [kolla] RabbitMQ High Availability Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Le mer. 8 déc. 2021 à 11:48, Bogdan Dobrelya <bdobreli(a)redhat.com> a écrit : Please see inline >> I read this with great interest because we are seeing this issue. Questions: >> >> 1. We are running kola-ansible Train, and our RMQ version is 3.7.23. Should we be upgrading our Train clusters to use 3.8.x? >> 2. Document [2] recommends policy '^(?!(amq\.)|(.*_fanout_)|(reply_)).*'. I don't see this in our ansible playbooks, nor in any of the config files in the RMQ container. What would this look like in Ansible, and what should the resulting container config look like? >> 3. It appears that we are not setting "amqp_durable_queues = True". What does this setting look like in Ansible, and what file does it go into? > > Note that even having rabbit HA policies adjusted like that and its HA > replication factor [0] decreased (e.g. to a 2), there still might be > high churn caused by a large enough number of replicated durable RPC > topic queues. And that might cripple the cloud down with the incurred > I/O overhead because a durable queue requires all messages in it to be > persisted to a disk (for all the messaging cluster replicas) before they > are ack'ed by the broker. > > Given that said, Oslo messaging would likely require a more granular > control for topic exchanges and the durable queues flag - to tell it to > declare as durable only the most critical paths of a service. A single > config setting and a single control exchange per a service might be not > enough. Also note that therefore, amqp_durable_queue=True requires dedicated control exchanges configured for each service. Those that use 'openstack' as a default cannot turn the feature ON. Changing it to a service specific might also cause upgrade impact, as described in the topic [3]. The same is true for `amqp_auto_delete=True`. That requires dedicated control exchanges else it won't work if each service defines its own policy on a shared control exchange (e.g `openstack`) and if policies differ from each other. [3] https://review.opendev.org/q/topic:scope-config-opts > > There are also race conditions with durable queues enabled, like [1]. A > solution could be where each service declare its own dedicated control > exchange with its own configuration. > > Finally, openstack components should add perhaps a *.next CI job to test > it with durable queues, like [2] > > [0] https://www.rabbitmq.com/ha.html#replication-factor > > [1] > https://zuul.opendev.org/t/openstack/build/aa514dd788f34cc1be3800e6d7dba0e8… > > [2] https://review.opendev.org/c/openstack/nova/+/820523 > >> >> Does anyone have a sample set of RMQ config files that they can share? >> >> It looks like my Outlook has ruined the link; reposting: >> [2] https://wiki.openstack.org/wiki/Large_Scale_Configuration_Rabbit > > > -- > Best regards, > Bogdan Dobrelya, > Irc #bogdando -- Best regards, Bogdan Dobrelya, Irc #bogdando -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud

6 16

[ops][nova][victoria] Power State = Suspended?
by DHilsbos＠performair.com 24 Jan '22

24 Jan '22

All; I had something unusual happen this morning; one of my VMs was showing "Suspended" under the Power State in the Horizon dashboard. I've never seen that. What does it mean? Any search that I do points me to a bunch of resources for Status Suspended. Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

4 8

OpenInfra Summit Berlin 2022 Programming Committee Nominations Now Open
by Erin Disney 19 Jan '22

19 Jan '22

Hey everyone- Programming Committee nominations <https://openinfrafoundation.formstack.com/forms/programmingcommittee2022> for the 2022 OpenInfra Summit in Berlin (June 7-9, 2022) are now open! Programming Committees for each Track will help build the Summit schedule, and are made up of individuals working in open infrastructure. Responsibilities include: Help the Summit team put together the best possible content based on your subject matter expertise Promote the individual Tracks within your networks Review the submissions and Community voting results in your particular Track Determine if there are any major content gaps in your Track, and if so, potentially solicit additional speakers directly to submit Ensure diversity of speakers and companies represented in your Track Avoid vendor sales pitches, focusing more on real-world user stories and technical, in-the-trenches experiences Identify which submissions would make good content for OpenInfra Live, the virtual show hosted by the OpenInfra Foundation that encourages live questions from a global audience 2022 Summit Tracks: 5G, NFV & Edge AI, Machine Learning & HPC CI/CD Container Infrastructure Getting Started Hands-on Workshops NEW: Hardware Enablement Open Development Private & Hybrid Cloud Public Cloud Security Full track descriptions are available here <https://etherpad.opendev.org/p/r.86088dcd62bc50a6381c19f7f26995b6>. If you’re interested in nominating yourself or someone else to be a member of the Summit Programming Committee for a specific Track, please fill out the nomination form <https://openinfrafoundation.formstack.com/forms/programmingcommittee2022>. Nominations will close on January 19, 2022. Programming Committee selections will occur before we close the Call for Presentations (CFP) so that the Committees can host office hours to consult on submissions, and help promote the event. CFP will be opening in January, registration <https://www.eventbrite.com/e/openinfra-summit-berlin-2022-tickets-211374997…> and sponsorship <https://openinfra.dev/summit/> information are already available. Please email speakersupport(a)openinfra.dev with any questions or feedback. Cheers, Erin Disney Event Marketing Open Infrastructure Foundation

1 1

Can neutron-fwaas project be revived?
by Dazhong Qin (秦海中)-云数据中心集团 17 Jan '22

17 Jan '22

Hi： The firewall project is a necessary function when the project is delivered. The lack of firewall function after switching OVN is not acceptable to customers. We intend to maintain this project and develop the fwaas driver based on ovn. Whether the neutron-fwaas project can be reactivate? What should I do ?

4 10

[Deploy] Can three all-in-one nodes form a OpenStack cluster?
by 韩光宇 10 Jan '22

10 Jan '22

Dear all, I am deploing OpenStack Victoria. Can I make a cluster with three all-in-one nodes? Will this have any problems or points to be aware of? Sorry to bother, Thank you very much. Han Guangyu.

3 4

[nova][dev] Revisiting qemu emulation where guest arch != host arch
by Apsey, Christopher 05 Jan '22

05 Jan '22

All, A few years ago I asked a question[1] about why nova, when given a hw_architecture property from glance for an image, would not end up using the correct qemu-system-xx binary when starting the guest process on a compute node if that compute nodes architecture did not match the proposed guest architecture. As an example, if we had all x86 hosts, but wanted to run an emulated ppc guest, we should be able to do that given that at least one compute node had qemu-system-ppc already installed and libvirt was successfully reporting that as a supported architecture to nova. It seemed like a heavy lift at the time, so it was put on the back burner. I am now in a position to fund a contract developer to make this happen, so the question is: would this be a useful blueprint that would potentially be accepted? Most of the time when people want to run an emulated guest they would just nest it inside of an already running guest of the native architecture, but that severely limits observability and the task of managing any more than a handful of instances in this manner quickly becomes a tangled nightmare of networking, etc. I see real benefit in allowing this scenario to run natively so all of the tooling that exists for fleet management 'just works'. This would also be a significant differentiator for OpenStack as a whole. Thoughts? [1] http://lists.openstack.org/pipermail/openstack-operators/2018-August/015653… Chris Apsey Director | Georgia Cyber Range GEORGIA CYBER CENTER 100 Grace Hopper Lane | Augusta, Georgia | 30901 https://www.gacybercenter.org

2 2

[charms] nominate Hemanth Nakkina for charms-core
by Edward Hope-Morley 04 Jan '22

04 Jan '22

I would like propose Hemanth Nakkina for charms-core. Hemanth has really stepped up his efforts to provide invaluable contributions both in code and reviews and I beleive he is in a good position to be considered for core where he will be able to provide additional value to the project. Hemanth has demonstrated rigour for quality through his contributions and is always keen to help others with his deep knowledge of the charms and Openstack. Here is a list of all his contributions: patches: https://review.opendev.org/q/owner:hemanth.nakkina%2540canonical.com reviews: https://review.opendev.org/q/reviewedby:hemanth.nakkina%2540canonical.com I hope you will join me in voting for Hemanth. - Ed

6 5

[nova] Getting away from cdrkit / genisoimage
by Thomas Goirand 04 Jan '22

04 Jan '22

Hi, Please see: https://bugs.debian.org/982241 It looks like cdrkit / genisoimage wont be available in the next Debian 12 (and therefore probably it will also be dropped in Ubuntu). As per the bug report: "I'm told xorriso and libburnia are alternatives and are alive and doing well." Would it be possible to switch to that? Cheers, Thomas Goirand (zigo)

2 1

cpu pinning
by open infra 04 Jan '22

04 Jan '22

3 7

[all][qa][triplo] Help need to maintain OpenStack health dashboard
by Ghanshyam Mann 04 Jan '22

04 Jan '22

Hello Everyone, In the QA meeting[1], we discussed the help needed to maintain the OpenStack health dashboard which is broken currently and the QA team does not have the JS developer and bandwidth to fix it. While discussing it meeting, we found that the TripleO team might be working on a similar dashboard for their CI results. If that is the case, can we collaborate on maintaining the existing dashboard? OpenStack health dashboard: https://opendev.org/openstack/openstack-health Repo: http://status.openstack.org/openstack-health/#/ [1] https://meetings.opendev.org/meetings/qa/2021/qa.2021-11-16-15.00.log.html#… -gmann

5 7

[tempest] Extending tempest for mixed-architecture stacks
by James LaBarre 03 Jan '22

03 Jan '22

Recently I had been running Tempest on my setup testing a mixed-architecture deployment (x86_64 ans ppc64le compute nodes at the same time). It seems that some of the migration and affinity tests will check if there's more than one Compute node before they run. However, it would seem that's as far as they check, without checking if they are in fact compatible or even of the same architecture. (my test cluster is very small, and normally includes two ppc64le Compute nodes, and sometimes one x86_64 Compute node. Currently one ppc64le machine is down for repair). Because the two compute nodes are different architectures, I am getting failures in various migration and affinity tests, maybe more if I tested a larger subset. Now granted my particular setup is a special case, but it does bring to mind some extensions that may be needed for Tempest in the future. I could see it being possible to have x86_64 and ARM mixed together in one stack, maybe even tossing in RISC-v someday. I'm thinking we need to start adding in extra test images, flavors, etc into the Tempest configurations (as in defining multiple options so that each architecture can have test images, etc assigned to it, rather than the current primary and alt image for just one architecture) Additionally, there should be testcases taking into account the architectures involved (such as seeing that an instance on one arch cannot be migrated to the other, as an example). I know this involves a bit of refactoring, I didn't know if it had even been considered yet. -- James LaBarre Software Engineer, OpenStack MultiArch Red Hat <https://www.redhat.com> jlabarre(a)redhat.com <mailto:jlabarre@redhat.com> <https://www.redhat.com>

3 2

[tc][all] Follow up pain point discussion
by Rico Lin 03 Jan '22

03 Jan '22

Dear all The pain point collection etherpad [1] seems to get good attention from teams. We plan to host a one-hour video meeting to keep the discussion going. Please fill in the doodle to select your preferred time if you can join us: https://doodle.com/poll/kur2mfywceerqcvh?utm_source=poll&utm_medium=link The discussion will be hosted in video format. Here are some items (but not limited to) I expect we will discuss and hopefully put some actions/efforts on. - General Pain point: RabbitMQ - General Pain point: OpenStackClient support - General project pain point discussion: How to encourage teams to work/reply on pain points. Meanwhile, we encourage all to check the etherpad and provide your feedback. Also if teams can help to answer questions/concerns on etherpad (like Nova team does) will be greatly appreciated. [1] https://etherpad.opendev.org/p/pain-point-elimination *Rico Lin*

7 11

[octavia] Management Network Issue
by Ammad Syed 03 Jan '22

03 Jan '22

Hi, I am using octavia 9.0. I have created a neutron vlan based management network of octavia. I am creating a loadbalancer with a subnet in the tenant network, its getting created successfully. Then added a listener and created a pool, both created successfully. Now a weird situation is happening. Now when I add a member in the pool, the management network interface get detached automatically from the AMPHORA instance and amphora keeps in PENDING_UPDATE state. I have created a dedicated service-project for octavia and management network and subnet resides there. Any advise how to fix it ? Ammad

2 2

[release] Release countdown for week R-12, Jan 03-07
by Előd Illés 31 Dec '21

31 Dec '21

Development Focus ----------------- Happy new year! The Yoga-2 milestone is next week, on January6th, 2022. Yoga-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/ <https://releases.openstack.org/yoga/schedule.html>yoga <https://releases.openstack.org/yoga/schedule.html>/schedule.html <https://releases.openstack.org/yoga/schedule.html>for details. General Information ------------------- Libraries need to be released at least once per milestone period. Next week, the release team will propose releases for any library that has not been otherwise released since milestone 1. PTL's and release liaisons, please watch for these and give a +1 to acknowledge them. If there is some reason to hold off on a release, let us know that as well. A +1 would be appreciated, but if we do not hear anything at all by the end of the week, we will assume things are OK to proceed. Remember that 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. Next week is also the deadline to freeze the contents of the final release. All new 'Yoga' deliverables need to have a deliverable file in https://opendev.org/openstack/releases/src/branch/master/deliverables <https://opendev.org/openstack/releases/src/branch/master/deliverables> and need to have done a release by milestone-2. Changes proposing missingdeliverables for inclusion in Yogahave been posted, so if you have one in your project team please update them with an actual release request before the milestone-2 deadline if you plan on including that deliverable in Yoga, or -1 if you need one more cycle to be ready. Upcoming Deadlines & Dates -------------------------- Yoga-2 Milestone:January6th, 2022 Előd Illés irc: elodilles

1 0

[cinder] proposing Simon Dodsley for cinder-specs-core
by Brian Rosmaita 31 Dec '21

31 Dec '21

As everyone is painfully aware, we have review bandwidth issues in the Cinder project. I propose to address this issue with respect to cinder specs, at least, by adding a contributor who is not currently a cinder-core as a member of the cinder-specs-core team. (Right now, the only members of cinder-specs-core are the cinder-core team.) Simon Dodsley (simondodsley on IRC) has been a cinder contributor for a long time, and has been especially active in PTGs and midcycle meetings over the past few cycles. He's done quality reviews, especially of specs, this cycle. As a vendor representative, he brings a useful perspective to reviews that affect drivers, as well as general deployment and usability issues. Additionally, given that the current core team has reviewing responsibilities spread over multiple repositories, having a person focused primarily on specs should help us to get more timely feedback for specs proposers. Finally, don't forget that it is thanks to Simon that the Cinder mascot finally has a name ("Argo"), which in turn has given the Cinder team the really cool name "The Argonauts". In the absence of objections, I'll add Simon to the cinder-specs-core team shortly after 1500 UTC on Friday 31 December. Please communicate any concerns to me before that time. cheers, brian

4 4

PTR records in Designate
by Albert Braden 30 Dec '21

30 Dec '21

We have hacked Designate to add PTR records and it is a mess. Every upgrade turns into a bug hunt. I'd like to advocate for going back to vanilla kolla-ansible but then we wouldn't have PTR records. How are other Designate users dealing with the PTR issue?

2 2

[neutron] Do I need to replace NetworkManager with network.service in centos8?
by 韩光宇 29 Dec '21

29 Dec '21

Dear all, I am deploing OpenStack Victoria. I want to ask a question. Do I need to replace NetworkManager with network-scripts in centos8? I saw that "OpenStack Networking does not work on systems that have the Network Manager service enabled" in past redhat documentation and some other places. But I don't see this in latest documentation of OpenStack community（ https://docs.openstack.org/install-guide/environment-packages-rdo.html）. And If NetworkManager is confit will OpenStack network, Do anyone know where I can see the reason of confit. I would appreciate any kind of guidance. Thanks, Han Guangyu. Past redhat documentation: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11…

2 1

[cinder] Bug deputy report for week of 12-29-2021
by Sofia Enriquez 29 Dec '21

29 Dec '21

No meeting today. This is a bug report from 12-22-2021 to 12-29-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1955670 "Unable to delete a group volume after transfer". Unassigned. 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

[TripleO] Unable to deploy Overcloud Machines
by Anirudh Gupta 28 Dec '21

28 Dec '21

Hi Team, I am trying to deploy TripleO Train with 3 controller and 1 Compute. For overcloud images, I have a registry server at undercloud only. I executed the following command to deploy overcloud openstack overcloud deploy --templates \ -r /home/stack/templates/roles_data.yaml \ -e /home/stack/templates/node-info.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \ -e /home/stack/containers-prepare-parameter.yaml The command ran for around 1.5 hrs and initially stack got successfully created and after that for 45 mins, ansible tasks were getting executed. It then gave following error in overcloud-controller-0 2021-12-27 11:12:27,507 p=181 u=mistral n=ansible | 2021-12-27 11:12:27.506838 | 525400b1-b522-2a06-ea9d-00000000356f | OK | Debug output for task: Start containers for step 2 | overcloud-novacompute-0 | result={ "changed": false, "failed_when_result": false, "start_containers_outputs.stdout_lines | default([]) | union(start_containers_outputs.stderr_lines | default([]))": [ "f206c31a781641313aa4a0499c62475efc335de6faea785cd4e855dc32ebb571", "", "Info: Loading facts", "Notice: Compiled catalog for overcloud-novacompute-0.localdomain in environment production in 0.05 seconds", "Info: Applying configuration version '1640604309'", "Notice: /Stage[main]/Tripleo::Profile::Base::Neutron::Ovn_metadata_agent_wrappers/Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]/File[/var/lib/neutron/ovn_metadata_haproxy_wrapper]/ensure: defined content as '{md5}5bb050ca70c01981975efad9d8f81f2d'", "Info: Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]: Unscheduling all events on Tripleo::Profile::Base::Neutron::Wrappers::Haproxy[ovn_metadata_haproxy_process_wrapper]", "Info: Creating state file /var/lib/puppet/state/state.yaml", "Notice: Applied catalog in 0.01 seconds", "Changes:", " Total: 1", "Events:", " Success: 1", "Resources:", " Changed: 1", " Out of sync: 1", " Skipped: 7", " Total: 8", "Time:", " File: 0.00", " Transaction evaluation: 0.01", " Catalog application: 0.01", " Config retrieval: 0.09", " Last run: 1640604309", " Total: 0.01", "Version:", " Config: 1640604309", " Puppet: 5.5.10", * "Error executing ['podman', 'container', 'exists', 'nova_compute_init_log']: returned 1", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=nova_compute_init_log', '--filter', 'label=config_id=tripleo_step2', '--format', '{{.Names}}']\" - retrying without config_id", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=nova_compute_init_log', '--format', '{{.Names}}']\"", "Error executing ['podman', 'container', 'exists', 'create_haproxy_wrapper']: returned 1", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=create_haproxy_wrapper', '--filter', 'label=config_id=tripleo_step2', '--format', '{{.Names}}']\" - retrying without config_id", "Did not find container with \"['podman', 'ps', '-a', '--filter', 'label=container_name=create_haproxy_wrapper', '--format', '{{.Names}}']\""* ] } I am also attaching ansible.log file for more information. Note: On Centos 8, there is no docker, so I didn't pass docker-ha.yml Can someone please help in resolving my issue Regards Anirudh Gupta

2 9

[neutron] bug deputy report of week 2021-12-20
by Bence Romsics 27 Dec '21

27 Dec '21

Hi Team, We only had a few new bugs last week, here they are: High: * https://bugs.launchpad.net/neutron/+bug/1955478 Scenario test failed due to metadata service not available slaweq investigated this gate failure, but did not find enough information in the logs. * https://bugs.launchpad.net/neutron/+bug/1955546 [stable only] Logging service plugin expects wrong arguments in the callback function fixes mostly merged: https://review.opendev.org/q/I0003bd566dc769436ad1342351ad058394bd52da * https://bugs.launchpad.net/neutron/+bug/1955578 OVN transaction could not be completed due to a race condition proposed fix: https://review.opendev.org/c/openstack/neutron/+/821401 * https://bugs.launchpad.net/neutron/+bug/1955775 Error when l3-agent get filter id for ip proposed fix: https://review.opendev.org/c/openstack/neutron/+/822987 Medium: * https://bugs.launchpad.net/neutron/+bug/1955639 Performance of mariadb's neutron.agents table unassigned Incomplete: * https://bugs.launchpad.net/neutron/+bug/1955503 [ovn] OVN agents showing as dead until neutron services restarted If ovn folks have an intuition what may go wrong with agent caching, then please look at it, but we don't have reproduction steps, so marked as Incomplete. Other: * https://bugs.launchpad.net/neutron/+bug/1955765 Devstack - Can no longer enable qos with neutron-qos Now that we un-deprecated the legacy plugin what do we want to do with the new plugin? Possible discussion point for the next meeting. Cheers, Bence

1 0

[cloudkitty] No weekly meeting today
by Rafael Weingärtner 27 Dec '21

27 Dec '21

Hello guys, As agreed in the previous meeting, we will skip IRC meeting this week and be on 10th Jan next year. I hope you all had a merry Christmans, and happy holidays! -- Rafael Weingärtner

1 0

[kolla] No IRC meeting this week
by Michał Nasiadka 26 Dec '21

26 Dec '21

Hello Koalas, As agreed in the previous meeting, we will skip IRC meeting this week (planned for 29th Dec) and meet on 5th Jan. Happy new year! Michal -- Michał Nasiadka mnasiadka(a)gmail.com

1 0

[tacker] No weekly meeting until 2022
by Yasufumi Ogawa 26 Dec '21

26 Dec '21

Hi, As agreed in the previous meeting, we will skip IRC meeting this week and be on 11th Jan next year. Happy holidays! Cheers, yasufumi

1 0

No network access for Openstack instances
by A Monster 26 Dec '21

26 Dec '21

I have used kolla ansible to deploy openstack on two machine servers, but after setting up the images and the virtual networks, the vm instances don't get the ip address that neutron provides for them, so I had to manually set the addresses inside the vm's, but even with that I can't seem to connect vm's to neither internet nor any other network. I'm on centos 7 and trying to deploy openstack train using kolla ansible 9.3.1 Ansible 2.9.25 And neutron open vSwitch.

3 2

[all][tc] What's happening in Technical Committee: summary 24th Dec, 21: Reading: 5 min
by Ghanshyam Mann 24 Dec '21

24 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had a quick meeting yesterday. Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @https://meetings.opendev.org/meetings/tc/2021/tc.2021-12-23-15.00.log.html * Next week's meeting on 30th Dec is canceled. We will continue our weekly meeting from Jan 6th, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 5th Jan. 2. What we completed this week: ========================= * Nothing much in this week. 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[2]. Open Reviews ----------------- * 4 open reviews for ongoing activities[3]. SIG i18n status check -------------------------- Ian (SIG chair) responded on ML thread and will look into the things after he is back from leave next month[4]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[5] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- No updates on this. Discussion is in-progress in ML thread[6]. No other updates from TC on this and we will set up a separate call to continue the discussion sometime in Jan (after the Christmas holidays). Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[7]. Skyline as official projects ------------------------------ We accepted the Skyline as an official project last week and next work on project renaming etc are also started. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[8]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [9] 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[10]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [11] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. Marry Chirsmas and Happy new year to everyone and stay safe! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://etherpad.opendev.org/p/tc-yoga-tracker [3] https://review.opendev.org/q/projects:openstack/governance+status:open [4] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026441… [5] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [7] https://etherpad.opendev.org/p/zuul-config-error-openstack [8] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [9] https://review.opendev.org/c/openstack/governance/+/798540 [10] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [11] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[gate][tempest][plugins][stable] Stable/train tempest plugins jobs are broken
by Ghanshyam Mann 23 Dec '21

23 Dec '21

Hello Everyone, gthiemonge reported the issue for tempest plugin stable/train jobs are broken. I have explained the issue in https://bugs.launchpad.net/tempest/+bug/1955418 and fix is up (it is under testing). This is applicable for any tempest plugin job on stable/train. Please hold the recheck until the below fix is merged: https://review.opendev.org/c/openstack/tempest/+/822339 -gmann

1 1

[tc][sig][i18n] What's the status for Xena translation?
by Akihiro Motoki 23 Dec '21

23 Dec '21

Hi, # I include TC and SIG tags to get broader attractions to this topic. # Also Cc'ed to Ian (i18n SIG char) and Andreas. I would like to ask the status of Xena translation in translate.openstack.org (Zanata). In past releases, stable-XXX branches were created on Zanata, but a branch for Xena translation has not been created yet. Ajaeger usually prepared these branches as a volunteer (I am really appreciated) but AFAIK he no longer works on OpenStack actively. Who takes care of the translatio preparation around the release now? I hope the i18n SIG is not dead. Thanks, Akihiro Motoki (amotoki)

3 2

Re: [kolla-ansible][cinder] MPIO - how to set "storage_interface" when using two NICs for storage connection
by Adam Tomas 23 Dec '21

23 Dec '21

Hi again, I found some informations about MPIO here (https://docs.oracle.com/cd/E78305_01/E78304/html/setup-cinder.html) : "By default, the Cinder block storage service uses the iSCSI protocol to connect instances to volumes. The iscsid container runs on compute nodes and handles the iSCSI session using an iSCSI initiator name that is generated when you deploy Nova compute services. The Nova compute service supports iSCSI multipath for failover purposes and increased performance. Multipath is enabled by default (configured with the enable_multipathd property). When multipath is enabled, the iSCSI initiator (the Compute node) is able to obtain a list of addresses from the storage node that the initiator can use as multiple paths to the iSCSI LUN." But still - how should I set storage_interface, if I have two NICs for storage connection (let’s say eth4 and eth5)? storage_interface=eth4,eth5 ? Best regards Adam Tomas > Hi, > I’d like to use MPIO in connection to storage array, so I have two physical NIC’s in different VLANS on each node and also 4 NIC’s in the storage array (2 in each storage VLAN) so it should result in 4 MPIO paths from every node (2 paths in each VLAN). But how to set it in kolla-ansible? Can I point to more than one interface using storage_interface variable? Or maybe I should configure it in different way?

2 4

Networks for different availability zones in Horizon
by hai wu 23 Dec '21

23 Dec '21

In Horizon "Launch Instance" workflow, in its 4th step of selecting networks for the new instance, it would always show all the available networks from all availability zones, regardless of which "Availability Zone" got picked in 1st step of "Details". I tried to update some DB field for availability zone hint for the relevant network, and that did not help. Any way to ensure in Horizon "Launch Instance" GUI workflow, after a user picking one availability zone in step 1, it would only show the related networks in that availability zone as available networks in step 4?

6 10

[all][tc] Technical Committee next weekly meeting on Dec 23rd at 1500 UTC
by Ghanshyam Mann 22 Dec '21

22 Dec '21

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Dec 23rd at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Dec 22nd, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[adjutant][requirements] Adjutant Django version
by Dmitriy Rabotyagov 22 Dec '21

22 Dec '21

2 1

[requirements][OpenStackClients][rally][tempest][watcher][nova][glance] Use prettytable in requirements
by Dmitriy Rabotyagov 22 Dec '21

22 Dec '21

2 2

[cinder] Bug deputy report for week of 12-22-2021
by Sofia Enriquez 22 Dec '21

22 Dec '21

No meeting today. This is a bug report from 12-15-2021 to 12-22-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/os-brick/+bug/1955020 "multipath -l <device_name> is failing". Assigned to Rajat Dhasmana. Low - https://bugs.launchpad.net/cinder/+bug/1955057 "NetApp driver fails to compare ONTAP version". Assigned to Nahim Alves de Souza. Wishlist - https://bugs.launchpad.net/cinder/+bug/1955360 "Cannot clone a volume from the image within the same ceph cluster". Assigned to Eric Xie. 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

[tripleo][ussuri] Log4j add protection to haproxy {even it is not impacted
by Ruslanas Gžibovskis LPIC 22 Dec '21

22 Dec '21

3 2

[kolla-ansible][cinder]
by Adam Tomas 22 Dec '21

22 Dec '21

Hi, I’d like to use MPIO in connection to storage array, so I have two physical NIC’s in different VLANS on each node and also 4 NIC’s in the storage array (2 in each storage VLAN) so it should result in 4 MPIO paths from every node (2 paths in each VLAN). But how to set it in kolla-ansible? Can I point to more than one interface using storage_interface variable? Or maybe I should configure it in different way? Best regards Adam Tomas

1 0

[neutron] CI meeting 28.12.2021 cancelled
by Slawek Kaplonski 21 Dec '21

21 Dec '21

Hi, Next week Neutron CI meeting is cancelled. Happy holidays for all of You and see You on the meetings in 2022! We will start with CI meeting 4.01.2022 :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder] weekly meetings for the remainder of december
by Brian Rosmaita 21 Dec '21

21 Dec '21

As agreed at last week's cinder meeting, our meetings for the remainder of 2021 will be: * Wednesday, December 22: no meeting * Wednesday, December 29: no meeting The next weekly cinder meeting will be Wednesday, January 5 at the usual time (1400 UTC) in the usual place (#openstack-meeting-alt on OFTC). The meeting agenda is here: https://etherpad.opendev.org/p/cinder-yoga-meetings cheers, brian

1 0

[Triple0] Unable to pxeBoot overcloud Nodes via ipv6
by Lokendra Rathour 20 Dec '21

20 Dec '21

Hi Team, we have installed Undercloud with Train release on Centos8 using ipv6 as loca_ip in undercloud.conf file. Undercloud seems to be installed successfully and we are able to see IPv6 endpoints as well. Also, the OpenStack overcloud images are uploaded and well visible on http://<ipv6>:8088 tftp link. Problem Statement: During introspection start, we see that ipv6 is allocated to the node, further no action is being performed. Please refer the screen attached. [image: image.png] As we can see ipv6 bbbb:bbbb:bbbb::9 is allocated to the desired machine. Furthermore, we see that the link is shown as down for the same mac, which also becomes up as can be seen but the configuring on that NIC eventually fails for some reason. Any idea/inputs on this please? -- ~ Lokendra

1 0

[TripleO] Tomorrow's (Dec 21) meeting cancelled, next meeting Jan 3
by James Slagle 20 Dec '21

20 Dec '21

As we have no items on the agenda[1] for tomorrow's meeting, let's cancel it and hold our next meeting on Tuesday, January 3rd. Thanks! [1] https://etherpad.opendev.org/p/tripleo-meeting-items -- -- James Slagle --

1 0

[kolla] The impact of CentOS Linux 8 EOL and OpenDev's drop of the respective image
by Radosław Piliszek 20 Dec '21

20 Dec '21

Dears, As you may recall, the CentOS Linux 8 (as opposed to CentOS Stream 8) is reaching its EOL (End Of Life) Dec 31st, 2021 (that is, in eleven days). [1] Due to that, the OpenDev team (that hosts kolla's repos and the CI/CD that we rely on) has decided to drop the EOLed images January 14th, 2022. [2] This impacts both Kolla and Kolla Ansible in subtle ways - both operator-wise and contributor-wise. The EM (Extended Maintenance) branches, Train and Ussuri, in both projects, rely solely on CentOS Linux 8, the Stream variant is *not* supported there. This means that in 2022 we are forced to cease to test these branches against CentOS Linux 8 (we will still test the two other distros - Ubuntu and Debian). Operators are advised to upgrade to Victoria or (preferably) later (psst, go Xena). Furthermore, CentOS Linux 8 is currently supported in Victoria but this support will also end naturally with 2022 on the horizon. Operators are advised to migrate to CentOS Stream 8 and images based on it. [1] https://www.centos.org/centos-linux-eol/ [2] http://lists.opendev.org/pipermail/service-announce/2021-December/000029.ht… Kind regards, -yoctozepto

1 0

[kolla] Dropping support for vmtp in Yoga
by Radosław Piliszek 20 Dec '21

20 Dec '21

Dear Users of Kolla! The Kolla project, so far, provided vmtp [1] image and ansible role. However, the status of those has been unknown (the ansible role looks pretty stale, still referencing ubuntu 16.04!) and now the vmtp image is failing to build so we are forced to disable it. [2] The project itself [1] looks rather unmaintained and it's outside of the openstack namespace so our plan is to drop support for it entirely in this cycle (Yoga). Please reply to this mail if you are using vmtp with Kolla in some recent release and are willing to contribute to let us keep supporting it. [1] https://opendev.org/x/vmtp [2] https://review.opendev.org/c/openstack/kolla/+/820043 Kind regards, -yoctozepto

1 1

[Glance] No weekly meeting until New Year
by Abhishek Kekane 20 Dec '21

20 Dec '21

Hello All, Christmas and New year holidays are approaching and most of the glance team is on vacation so we are canceling our next two weekly meetings. Next meeting will be on 06th January, 2022. Merry Christmas and Happy New year in advance!!! Cheers, Abhishek Kekane

1 0

[nova][placement] PTL on PTO until Jan 3rd
by Sylvain Bauza 20 Dec '21

20 Dec '21

Hi folks, I'll be off the keyboard from tonight and only be back on Monday January the 3rd. Have good holidays if you have them and good rest. For others, thanks for continuing to help Nova and see you again in 2022 ! -Sylvain

1 0

[qa] Cancelling office hour on Dec 28th due to holidays
by Martin Kopec 20 Dec '21

20 Dec '21

Hi all, we'll have the last office hour in 2021 tomorrow (Dec. 21st). Our first office hour in 2022 will be held on Dec. 4th. Merry Christmas and Happy New Year! Regards, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

2 2

[nova] random unauthorized errors
by Ammad Syed 20 Dec '21

20 Dec '21

Hi, I am using nova 23.0.0 and I am randomly facing unauthorized error sometime when nova uses neutron or cinder phython3 client during listing of server and creation of server. When I list server again, it works fine. I have found below logs in nova-api. 2021-12-20 09:10:24.920 2689471 DEBUG nova.api.openstack.wsgi [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Calling method '<bound method ServersController.detail of <nova.api.openstack.compute.servers.ServersController object at 0x7f840b6c5070>>' _process_stack /usr/lib/python3/dist-packages/nova/api/openstack/wsgi.py:513 2021-12-20 09:10:24.925 2689471 DEBUG nova.compute.api [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Searching by: {'project_id': '890eb2b7d1b8488aa88de7c34d08817a', 'deleted': False} get_all /usr/lib/python3/dist-packages/nova/compute/api.py:2857 2021-12-20 09:10:24.930 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Lock "00000000-0000-0000-0000-000000000000" acquired by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: waited 0.000s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:355 2021-12-20 09:10:24.931 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default def2021-12-20 09:10:24.548 2689471 INFO nova.osapi_compute.wsgi.server [req-c5da1a3c-3c99-46c2-84e9-b504ccc5d156 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] 172.16.30.56 "GET /v2.1/ HTTP/1.1" status: 200 len: 800 time: 0.0048089 2021-12-20 09:10:24.697 2689471 DEBUG nova.osapi_compute.wsgi.server [req-572eca81-8d3b-4524-89e5-e4e1124a7ac5 - - - - -] (2689471) accepted ('172.16.30.56', 52016) server /usr/lib/pytho n3/dist-packages/eventlet/wsgi.py:992 2021-12-20 09:10:24.920 2689471 DEBUG nova.api.openstack.wsgi [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default defaul t] Calling method '<bound method ServersController.detail of <nova.api.openstack.compute.servers.ServersController object at 0x7f840b6c5070>>' _process_stack /usr/lib/python3/dist-packag es/nova/api/openstack/wsgi.py:513 2021-12-20 09:10:24.925 2689471 DEBUG nova.compute.api [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Sear ching by: {'project_id': '890eb2b7d1b8488aa88de7c34d08817a', 'deleted': False} get_all /usr/lib/python3/dist-packages/nova/compute/api.py:2857 2021-12-20 09:10:24.930 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default def ault] Lock "00000000-0000-0000-0000-000000000000" acquired by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: waited 0.000s inner /usr/lib/python3/d ist-packages/oslo_concurrency/lockutils.py:355 2021-12-20 09:10:24.931 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default def ault] Lock "00000000-0000-0000-0000-000000000000" released by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: held 0.001s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:367 2021-12-20 09:10:24.933 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Lock "fc805771-7891-4095-8162-491cf824b02f" acquired by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: waited 0.000s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:355 2021-12-20 09:10:24.934 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Lock "fc805771-7891-4095-8162-491cf824b02f" released by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: held 0.001s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:367 2021-12-20 09:10:25.019 2689471 DEBUG nova.compute.multi_cell_list [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Listed batch of 13 results from cell out of 21 limit. Returned 13 total so far. do_query /usr/lib/python3/dist-packages/nova/compute/multi_cell_list.py:371 2021-12-20 09:10:25.093 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Lock "fc805771-7891-4095-8162-491cf824b02f" acquired by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: waited 0.000s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:355 2021-12-20 09:10:25.094 2689471 DEBUG oslo_concurrency.lockutils [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Lock "fc805771-7891-4095-8162-491cf824b02f" released by "nova.context.set_target_cell.<locals>.get_or_set_cached_cell_and_set_connections" :: held 0.000s inner /usr/lib/python3/dist-packages/oslo_concurrency/lockutils.py:367 *2021-12-20 09:10:25.393 2689471 DEBUG neutronclient.v2_0.client [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Error message: {"error": {"code": 401, "title": "Unauthorized", "message": "The request you have made requires authentication."}} _handle_fault_response /usr/lib/python3/dist-packages/neutronclient/v2_0/client.py:258* 2021-12-20 09:10:25.394 2689471 ERROR nova.network.neutron [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] 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': {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'}} 2021-12-20 09:10:25.395 2689471 INFO nova.api.openstack.wsgi [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] HTTP exception thrown: Networking client is experiencing an unauthorized exception. 2021-12-20 09:10:25.396 2689471 DEBUG nova.api.openstack.wsgi [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] Returning 400 to user: Networking client is experiencing an unauthorized exception. __call__ /usr/lib/python3/dist-packages/nova/api/openstack/wsgi.py:927 2021-12-20 09:10:25.398 2689471 INFO nova.osapi_compute.wsgi.server [req-91ee9c88-e8ab-4e9b-8e1a-ca8a807c7e45 2af528fdf3244e15b4f3f8fcfc0889c5 890eb2b7d1b8488aa88de7c34d08817a - default default] 172.16.30.56 "GET /v2.1/890eb2b7d1b8488aa88de7c34d08817a/servers/detail?limit=21&project_id=890eb2b7d1b8488aa88de7c34d08817a&sort_dir=desc&sort_dir=desc&sort_dir=desc&sort_key=created_at&sort_key=display_name&sort_key=uuid HTTP/1.1" status: 400 len: 529 time: 0.7002470 Is there anything that I need to change ? -- Regards, Syed Ammad Ali

1 0

[octavia] cancelling weekly meetings until 2022
by Gregory Thiemonge 20 Dec '21

20 Dec '21

Hi, As discussed during our last weekly meeting, the next 2 meetings (Dec 22nd and 29th) are cancelled. Our next meeting will be on January 5th, Greg

1 0

[neutron] PTL on PTO
by Lajos Katona 19 Dec '21

19 Dec '21

Hi, I will be on PTO, back in Tuesday, 04. 01. 2022. Don't hesitate to write, I will be reachable. Regards Lajos Katona (lajoskatona)

3 3

Inquiry on FWaaS Deprecation
by 권다진 19 Dec '21

19 Dec '21

1 0

[neutron] bug deputy report December 13th to 19th
by Miguel Lavalle 19 Dec '21

19 Dec '21

Hi, Here's this week's bugs deputy report: High ==== https://bugs.launchpad.net/neutron/+bug/1954666 "LoggingPlugin._clean_logs_by_target_id" failing in stable releases. Assigned to Rodolfo Alonso. Fixes: https://review.opendev.org/c/openstack/neutron/+/821563, https://review.opendev.org/c/openstack/neutron/+/821564, https://review.opendev.org/c/openstack/neutron/+/821565 Medium ====== https://bugs.launchpad.net/neutron/+bug/1954763 Creating ports in bulks can be very slow due to many IPAM module conflicts. Assigned to Slawek Kaplonski. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/821727 https://bugs.launchpad.net/neutron/+bug/1954785 Session semantic violated when sending FloatingIP disassociation update during port deletion. Assigned to Szymon Wróblewski https://bugs.launchpad.net/neutron/+bug/1954942 [fullstack] Failure of "test_reschedule_network_on_new_agent". Needs owner https://bugs.launchpad.net/neutron/+bug/1955008 [functional] Failure of "test_floatingip_mac_bindings". Needs owner https://bugs.launchpad.net/neutron/+bug/1955010 [stable] py27 is not supported in "python-lazy-object-proxy" release 1.7.0. Assigned to Rodolfo Alonso Low ==== https://bugs.launchpad.net/neutron/+bug/1954903 [OVN] Add floating IP pools L3 extension to OVN L3 service. Assigned to Rodolfo Alonso. Proposed fix https://review.opendev.org/c/openstack/neutron/+/821818 https://bugs.launchpad.net/neutron/+bug/1955121 Update subnet with same gateway_ip as is already used should be allowed. Assigned to Slawek Kaplonski. Proposed fix: https://review.opendev.org/c/openstack/neutron/+/822098 Waiting for response from submitter =========================== https://bugs.launchpad.net/neutron/+bug/1954771 [OVN]MAC of lrp has not been updated in MAC_Binding when it re-associated. https://bugs.launchpad.net/neutron/+bug/1954777 setting same static route with subnet already exists as direct connected network Cheers Miguel

1 0

[horizon] Networks for different availability zones in Horizon
by hai wu 18 Dec '21

18 Dec '21

In Horizon "Launch Instance" workflow, in its 4th step of selecting networks for the new instance, it would always show all the available networks from all availability zones, regardless of which "Availability Zone" got picked in 1st step of "Details". I tried to update some DB field for availability zone hint for the relevant network, and that did not help. Any way to ensure in Horizon "Launch Instance" GUI workflow, after a user picking one availability zone in step 1, it would only show the related networks in that availability zone as available networks in step 4?

1 0

[all][tc] What's happening in Technical Committee: summary 17th Dec, 21: Reading: 10 min
by Ghanshyam Mann 17 Dec '21

17 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @ https://meetings.opendev.org/meetings/tc/2021/tc.2021-12-16-15.00.log.html * Next week's meeting is on IRC on 23rd Dec (it is scheduled as of now but i will confirm it on Monday), Thursday 15:00 UTC, feel free the topic on the agenda[1] by 22nd Dec. 2. What we completed this week: ========================= * Skyline is accepted as an official project [2] * Updated Yoga testing runtime and job templates[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. Open Reviews ----------------- * 3 open reviews for ongoing activities[5]. SIG i18n status check -------------------------- As you might have seen in the email from Amotoki on missing Xena translation[6] or ID translation bug[7], we checked this SIG status in the TC meeting. We did not get any concrete answer about the status of this SIG, but I have an action item to reach out to the current chair of this SIG (Ian). If anyone would like to help or know who can help especially those who need the translation, please reply to this thread or thread started by Amotoki[6]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[8] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- Discussion is in-progress in ML thread[9]. No other updates from TC on this and we will set up a separate call to continue the discussion sometime in Jan (after the Christmas holidays). Fixing Zuul config error -------------------------- There is some progress by projects but still, we need to fix a lot of config errors. If your project is listed in zuul config error, please start planning to fix those[10] Community-wide goal updates ------------------------------------ You might have seen my email[11] about goal status and planning the work, below is the current status: * Selected (active) goals[12]: ** Migrate from oslo.rootwrap to oslo.privsep ** Consistent and Secure Default RBAC * Goal proposal under review: ** FIPS compatibility and compliance [13]. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[14]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [15] 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[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 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/+/814037 [3] https://review.opendev.org/c/openstack/governance/+/820195 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026244… [7] https://review.opendev.org/c/openstack/contributor-guide/+/821371 [8] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [10] https://etherpad.opendev.org/p/zuul-config-error-openstack [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026218… [12] https://governance.openstack.org/tc/goals/selected/index.html [13] https://review.opendev.org/c/openstack/governance/+/816587 [14] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [15] https://review.opendev.org/c/openstack/governance/+/798540 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

No network access for openstack instances
by A Monster 17 Dec '21

17 Dec '21

I have used kolla ansible to deploy openstack on two machine servers, but after setting up the images and the virtual networks, the vm instances don't get the ip address that neutron provides for them, so I had to manually set the addresses inside the vm's, but even with that I can't seem to connect vm's to neither internet nor any other network.

2 2

[neutron] Routing fake "floating IPs" of VMs running inside VMs of an OpenStack
by Thomas Goirand 17 Dec '21

17 Dec '21

Hi, I've been designing a CI for OCI [1] to make it more robust and easier to contribute. After a week and a half, I've been able to make OCI deploy itself in an OpenStack itself. OCI itself pops with a public IP I can reach from the outside, and it setups OpenStack inside OpenStack VMs on a flat, private subnet (currently 192.168.100.0/24). This works pretty well, I have a fully working setup, and the deployment is completely automated. This even works without admin credentials, so all one needs, is a non-privileged account in any OpenStack. However, at this point, I'd like to setup the network for VMs inside the VMs. And that's where it becomes tricky. The VM that runs tempest will need to reach the floating IPs of the VMs inside the VMs that are running nova-compute, in order to do ssh tests. How can I do that? Is this even possible? Cheers, Thomas Goirand (zigo) [1] https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer

2 1

[neutron][ovn] VLAN Ranges
by Ammad Syed 17 Dec '21

17 Dec '21

Hi, I am using neutron xena release with OVN. I have currently defined the vlan range "network_vlan_ranges = vlannet1:3500:3600" in ml2_conf.ini. I have set bridge mapping via ovs with the below command. ovs-vsctl set open . external-ids:ovn-bridge-mappings=vlannet1:br-vlan Now I have to add a new vlan range. Can anyone confirm the syntax of ml2_conf.ini and bridge mapping. network_vlan_ranges = vlannet1:3500:3600,vlannet2:300:400 ovs-vsctl set open . external-ids:ovn-bridge-mappings=vlannet1:br-vlan,vlannet2:br-vlan Need to confirm the correct way to add new vlan range if the server is currently live ? Can we use the same bridge with two different mapping i.e vlannet1 and vlannet2 ? Ammad

2 3

[blazar] Next IRC meeting cancelled
by Pierre Riteau 17 Dec '21

17 Dec '21

Hello, As decided during yesterday's meeting, we are cancelling the Blazar IRC meeting scheduled for December 30. The next meeting will be on January 13. Merry Christmas and Happy New Year! Best wishes, Pierre Riteau (priteau)

1 0

[horizon] Cancelling next two weekly meetings
by vishal manchanda 17 Dec '21

17 Dec '21

Hello Team, As agreed, during the last weekly meeting, we are canceling our weekly meeting on 22nd and 29th December. The next weekly meeting will be on 5th December. Happy holidays and happy new year in advance! Thanks & Regards, Vishal Manchanda

1 0

[charms] review abandonment policy
by James Page 17 Dec '21

17 Dec '21

Hi Charms Contributors As part of this cycles work to put in more proactive general maintenance of the Gerrit review queue for the OpenStack Charms projects we have introduced an abandonment policy for reviews: https://docs.openstack.org/charm-guide/latest/community/rotas.html#abandonm… Pruning the set of open reviews on a regular basis against this policy will help reviewers focus on active reviews. We'll start doing this in January - you can follow the blocked/failing links in the charm-guide policy section to see which reviews will be abandoned at any given point in time. Cheers James

1 0

[neutron] missing dhcp ports after reboot and neutron-ovs-cleanup
by Kamil Madáč 16 Dec '21

16 Dec '21

Hello We have deployed Victoria release with kolla-ansible (openvswitch neutron driver), and after the reboot of control nodes we are experiencing issues with dhcp on some networks. I found out that there were missing dhcp tap interfaces in br-int openvswitch. After restart of dhcp agetn and openvswitch agent, interface was added to br-int and dhcp works again in that network. I found bug from 2016 (https://bugs.launchpad.net/kolla/+bug/1617188) that there is a script neutron-ovs-cleanup (it is in each neutron docker container), which should be run after reboot of dhcp/L3 nodes otherwise issues with dhcp/metadata/l3 functionalities could arise. I do not see mentioned this in kolla documentation, bug is quite old and expired, so I would like to ask, is that still valid and should it be run manually after each reboot of dhcp/L3 node? If yes, what is best what how to achieve it when docker starts all container automatically after reboot. Should I stop neutron containers, run neutron-ovs-cleanup and start them again? Kamil Madáč Slovensko IT a.s.

2 1

[neutron] No more meetings in 2021 :-)
by Lajos Katona 16 Dec '21

16 Dec '21

Hi Neutrinos! Due to the holiday season let's cancel the next 2 Team and Drivers meeting. See you all in January, and have great Holidays! Lajos Katona (lajoskatona)

1 0

[nova] instance device_metadata
by Arnaud Morin 16 Dec '21

16 Dec '21

Hey all, How is filled the device_metadata in instance_extra db? It's empty for my instances. It's supposed to be accessible then through metadata api, and contains at least network and block device info, but it's empty here. Thanks for any hint!

1 1

[manila] No IRC meeting on 30th Dec 2021
by Goutham Pacha Ravi 16 Dec '21

16 Dec '21

Hi Zorillas, As we discussed during our meeting today [1], we'll have our last IRC meeting for 2021 next week (23rd Dec 2021 at 1500 UTC) in OFTC's #openstack-meeting-alt. We'll skip the meeting on 30th Dec 2021 due to the year end holidays. As always, please feel free to add to the meeting agenda here: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting Thanks, Goutham Pacha Ravi [1] https://meetings.opendev.org/meetings/manila/2021/manila.2021-12-16-15.01.l…

1 0

[all][tc][policy] Canceling policy popup team next meeting
by Ghanshyam Mann 16 Dec '21

16 Dec '21

Hello Everyone, Due to holiday weeks, we are cancelling the policy pop-up next meeting scheduled for 30th Dec. We will continue this biweekly meeting from 13th Jan. https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… -gmann

1 0

[cinder] festival of XS reviews 17 December 2021
by Brian Rosmaita 16 Dec '21

16 Dec '21

Hello Argonauts [0], Apologies for the lateness of this reminder, but hopefully everyone has already used the handy ICS file [1] to have this event on their personal calendars. The most recent edition of the Cinder Festival of XS Reviews will be held tomorrow (Friday 17 December). who: Everyone! what: The Cinder Festival of XS Reviews when: Friday 17 December 2021 from 1400-1600 UTC where: https://meetpad.opendev.org/cinder-festival-of-reviews etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews See you there! brian [0] At the Yoga PTG, the Cinder mascot was named "Argo" and the Cinder project team thereby became the "Argonauts". [1] http://eavesdrop.openstack.org/calendars/cinder-festival-of-reviews.ics

1 0

[cyborg][nova][qa]Question about Accelerator unbinding
by Di XiaoLi 15 Dec '21

15 Dec '21

hi, Cyborg and nova team: I am using cyborg with "Wallaby" release to manage my accelerator devices, while I'm trying to unbind the accelerator I found that the device was not actually unbound from the virtual machine. Here are my questions: 1. What is the function of the arq unbind command in cyborg ? 2. How to unbind the accelerator which bounded to vm? Does nova or cyborg support this function now？ Here are my steps: step1: openstack accelerator arq unbind ed205084-f58d-4fad-99b4-327a1398858f +---------------------+--------------------------------------+ | Field | Value | +---------------------+--------------------------------------+ | uuid | ed205084-f58d-4fad-99b4-327a1398858f | | state | Unbound | | device_profile_name | ssd | | hostname | None | | device_rp_uuid | None | | instance_uuid | None | | attach_handle_type | | | attach_handle_info | {} | +---------------------+--------------------------------------+ step2: login vm and check the device, but it still here. step3: stop vm and start vm, met the following error: "nova.exception.AcceleratorRequestOpFailed: Failed to get accelerator requests: Cyborg returned no accelerator requests for instance ca77ef4e-421c-4c6c-9d76-7618a90ec921"

4 9

[all][tc] Technical Committee next weekly meeting on Dec 16th at 1500 UTC
by Ghanshyam Mann 15 Dec '21

15 Dec '21

Hello Everyone, Technical Committee's next weekly meeting is scheduled for Dec 16th at 1500 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Wednesday, Dec 15th, at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

1 1

[stable][requirements][zuul] unpinned setuptools dependency on stable
by Balazs Gibizer 15 Dec '21

15 Dec '21

Hi, The latest setuptools (58.0) removed support for "use_2to3" [1] (deprecated since 46.2). Many OpenStack modules defines decorator==3.4.0 as lower constraints[2]. However, decorator 3.4.0 cannot be installed anymore with the latest setuptool as it depends on "use_2to3". On master, this can be solved easily by bumping the dependency to decorator 4.0.0. On stable/xena we can still solve it the same way with a new RC. But on older stable branches such solution might be against the stable policy as it would require a major bump on our dependencies. This issue is not limited to lower-constraints testing it just hit us there first. A similar break could happen in our upper constraints as well on old stable branches. The root of the problem is that we always use the latest setuptools in our CI testing even on old stable branches. Zuul's ensure-tox task[4] installs tox which installs the virtualenv package which bundles the latest setuptools package. This happens without applying any constraints. Then tox is used to install the project's dependencies under lower or upper constraints with the unconstrained setuptools available. During and after yesterday's nova meeting [3] we discussed possible solutions. Option 1: Bump the major version of the decorator dependency on stable. Pros: * easy to implement Cons: * might against the policy / breaks downstream packagers * needs to be done in each affected project[3] separately * not future proof. After a future setuptools release we can see a similar break with another of our dependencies. @Stable Cores: how do you feel about such bump? Option 2: Pin the setuptools version during tox installation Pros: * single solution for all affected projects * future proof against breaks introduced by future setuptools releases Cons: * complex change as it probably requires to extend the base task in zuul itself Option 3: turn off lower-constraints testing Pros: * easy to implement * some of us want to get rid of lower constraints anyhow Cons: * needs per project changes * not future proof against similar break affecting our upper constraints on old stable branches. Option 4: utilize pyproject.toml[6] to specify build-time requirements Unfortunately, I'm not sure if it is possible to restrict the maximum setuptools version with it As a side note I tried applying [tox]requires in tox.ini to restrict setuptools version[7] but It does not seem to take effect in our case[8]. @Stable Cores: what do you think what could be the way forward? Cheers, gibi [1] https://setuptools.pypa.io/en/latest/history.html#v58-0-2 [2] https://codesearch.openstack.org/?q=decorator%3D%3D3.4.0&i=nope&literal=nop… [3] https://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.20… [4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-tox/tasks… [5] https://tox.readthedocs.io/en/latest/config.html#conf-requires [6] https://www.python.org/dev/peps/pep-0518/ [7] https://review.opendev.org/c/openstack/placement/+/810293/1/tox.ini [8] https://zuul.opendev.org/t/openstack/build/f78a0300c8734e7c8475309af1d2e1a4…

11 28

Re: [gate][tripleo] gate blocker
by Ananya Banerjee 15 Dec '21

15 Dec '21

Hi, We have a tripleo gate blocker. Patches 816991,16 and 821778 which fixes bugs needs to go first to unblock the rest. Can someone please get these two patches to the top of the queue? https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/821699/ https://review.opendev.org/c/openstack/tripleo-ci/+/821778/ Thanks, Ananya -- Ananya Banerjee, RHCSA, RHCE-OSP Software Engineer Red Hat EMEA <https://www.redhat.com/> anbanerj(a)redhat.com M: +491784949931 IM: frenzy_friday @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/>

3 3

[barbican][keystone] Weekly meetings to resume in 2022
by Douglas Mendizabal 15 Dec '21

15 Dec '21

Hi Barbican and Keystone contributors! I'll be taking some time off for the holidays starting next week and won't be available to chair the weekly meetings. I'll be back on January 11 to resume the weekly meetings for both Barbican and Keystone teams. Happy holidays, y'all! See you in 2022! - Douglas Mendizábal (redrobot)

1 0

[ops] [nova] problems with some default nova config values after update to Xena
by Massimo Sgaravatto 15 Dec '21

15 Dec '21

Hi After trying to update a CentOS8-stream testbed to Xena, there is a mess with some default values of nova In particular I see that: - everything (for all services) is being logged to syslog (it looks like that log_dir is using "none") - state_path for nova is using /usr/lib/python3.6/site-packages instead of /var/lib/nova Any hints on how to debug this? Thanks, Massimo

1 0

[Openstack][FOSDEM][CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 15 Dec '21

15 Dec '21

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2022, to be hosted virtually on February 5th 2022. This year will mark FOSDEM’s 22nd anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. Due to Covid-19, FOSDEM will be held virtually this year on February 5th & 6th, 2022. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at users or developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 20th of December Acceptance notifications: 25th of December Final schedule announcement: 31st of December Recorded presentations upload deadline: 15th of January Devroom: 6th February 2022 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will need to be pre-recorded and put into our system at least a couple of weeks before the event. The presentations should be uploaded by 15th of January and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend the virtual FOSDEM event for the Q&A. We will not consider proposals from prospective speakers who are unsure whether they will be able to attend the FOSDEM virtual event. If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance with helping speakers to record the presentation as well as helping with streaming and chat moderation for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] https://penta.fosdem.org/submission/FOSDEM22 [2] iaas-virt-devroom at lists.fosdem.org

1 1

[cinder] Bug deputy report for week of 12-15-2021
by Sofia Enriquez 15 Dec '21

15 Dec '21

This is a bug report from 12-08-2021 to 12-15-2021. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1953704 "Volume Type deletion error (image_volume_cache_enabled = True) - stable/xena". Unassigned. Incomplete - https://bugs.launchpad.net/cinder/+bug/1954613 "Blank volume's attach_status causes the volume list to fail". Unassigned. - https://bugs.launchpad.net/cinder/+bug/1954664 "Customer has issues in removing the volumes on the hosts , volumes from 3par". Unassigned. 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

[all] Pending patches proposed by release bot
by Takashi Kajinami 15 Dec '21

15 Dec '21

(I'm using all tag instead of project specific tags because the list can be too long) Hi all, I noticed that many patches proposed by release bot are still pending on reviews. Because of this, I see several projects like; - unit tests are executed in old test runtimes, - release note for specific release is missing ... https://review.opendev.org/q/owner:infra-root%2540openstack.org+status:open I'd like to encourage each project to take a moment to move these forward, or abandon them if these are unnecessary. I'm trying to list up all projects affected but I might be missing some of them. So please check the above query to find anything maintained by your project. - heat - keystone - mistral - sahara - magnum - adjutant - monasca - murano - barbican - freezer - openstacksdk - zaqar - watcher - telemetry(ceilometer/aodh/panko) Thank you, Takashi

2 2

[baremetal-sig][ironic] Tue Dec 14, 2021, 2pm UTC: Metal3 Overview
by Arne Wiebalck 14 Dec '21

14 Dec '21

Dear all, The Bare Metal SIG will meet tomorrow Tue Dec 14, 2021, at 2pm UTC on zoom. The meeting will feature a "topic-of-the-day" presentation by Dmitry Tantsur (dtantsur) with an "Overview of Metal3" (and I hear there might be a demo even!) As usual, all details on https://etherpad.opendev.org/p/bare-metal-sig Everyone is welcome: come along, learn from the expert and bring your questions! Cheers, Arne

1 1

[swift][tempest][kolla]
by Michal Arbet 14 Dec '21

14 Dec '21

Hello to eveyrone, Please, could someone help me with swift capabilities not working when I'm tempesting openstack test stack ? Tempest : rm -rf /tmp/tempest-lock/; refstack-client test -v -c /opt/tempest/tempest.conf -- --regex tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest (.venv) root@ca6353106d83:/opt/refstack-client# rm -rf /tmp/tempest-lock/; refstack-client test -v -c /opt/tempest/tempest.conf -- --regex tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest 2021-12-13 17:44:33.001 4358 INFO tempest [-] Using tempest config file /etc/tempest/tempest.conf 2021-12-13 17:44:33,839 refstack_client:518 INFO Starting Tempest test... 2021-12-13 17:44:33.839 4358 INFO refstack_client [-] Starting Tempest test... {0} setUpClass (tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest) [0.000000s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/opt/refstack-client/.tempest/tempest/test.py", line 181, in setUpClass raise value.with_traceback(trace) File "/opt/refstack-client/.tempest/tempest/test.py", line 174, in setUpClass cls.resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/test_account_quotas_negative.py", line 36, in resource_setup super(AccountQuotasNegativeTest, cls).resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/base.py", line 95, in resource_setup body = cls.capabilities_client.list_capabilities() File "/opt/refstack-client/.tempest/tempest/lib/services/object_storage/capabilities_client.py", line 32, in list_capabilities self._error_checker(resp, body) File "/opt/refstack-client/.tempest/tempest/lib/common/rest_client.py", line 799, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'} ============================== Failed 1 tests - output below: ============================== setUpClass (tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest) ---------------------------------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/opt/refstack-client/.tempest/tempest/test.py", line 181, in setUpClass raise value.with_traceback(trace) File "/opt/refstack-client/.tempest/tempest/test.py", line 174, in setUpClass cls.resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/test_account_quotas_negative.py", line 36, in resource_setup super(AccountQuotasNegativeTest, cls).resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/base.py", line 95, in resource_setup body = cls.capabilities_client.list_capabilities() File "/opt/refstack-client/.tempest/tempest/lib/services/object_storage/capabilities_client.py", line 32, in list_capabilities self._error_checker(resp, body) File "/opt/refstack-client/.tempest/tempest/lib/common/rest_client.py", line 799, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'} ====== Totals ====== Ran: 1 tests in 0.0000 sec. - Passed: 0 - Skipped: 0 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 1 Sum of execute time for each test: 0.0000 sec. TEMPEST LOG : Response - Headers: {'content-type': 'application/json', 'content-length': '114', 'www-authenticate': 'Keystone uri=" http://192.168.205.254:5000"', 'x-trans-id': 'tx815e181e33fb4854b2631-0061b7787a', 'x-openstack-request-id': 'tx815e181e33fb4854b2631-0061b7787a', 'date': 'Mon, 13 Dec 2021 16:44:42 GMT', 'connection': 'close', 'status': '401', 'content-location': ' https://api.refstack.ultimum.cloud:8080/info'} Body: b'{"error": {"code": 401, "title": "Unauthorized", "message": "The request you have made requires authentication."}}' _log_request_full /opt/refstack-client/.tempest/tempest/lib/common/rest_client.py:450 Test from command line and from curl . /etc/kolla/refstack.sh ; curl -H "X-Auth-Token: $(openstack token issue -f value -c id)" https://api.refstack.ultimum.cloud:8080/info {"swift": {"version": "2.27.1.dev9", "strict_cors_mode": true, "policies": [{"name": "Policy-0", "aliases": "Policy-0", "default": true}], "allow_account_management": true, "account_autocreate": true, "max_file_size": 5368709122, "max_meta_name_length": 128, "max_meta_value_length": 256, "max_meta_count": 90, "max_meta_overall_size": 4096, "max_header_size": 8192, "max_object_name_length": 1024, "container_listing_limit": 10000, "account_listing_limit": 10000, "max_account_name_length": 256, "max_container_name_length": 256, "extra_header_count": 0}, "container_sync": {"realms": {}}, "bulk_upload": {"max_containers_per_extraction": 10000, "max_failed_extractions": 1000}, "bulk_delete": {"max_deletes_per_request": 10000, "max_failed_deletes": 1000}, "tempurl": {"methods": ["GET", "HEAD", "PUT", "POST", "DELETE"], "incoming_remove_headers": ["x-timestamp"], "incoming_allow_headers": [], "outgoing_remove_headers": ["x-object-meta-*"], "outgoing_allow_headers": ["x-object-meta-public-*"], "allowed_digests": ["sha1", "sha256", "sha512"]}, "ratelimit": {"account_ratelimit": 0.0, "max_sleep_time_seconds": 60.0, "container_ratelimits": [], "container_listing_ratelimits": []}, "container_quotas": {}, "account_quotas": {}, "slo": {"max_manifest_segments": 1000, "max_manifest_size": 8388608, "yield_frequency": 10, "min_segment_size": 1, "allow_async_delete": false}} Python Swiftclient : ubuntu@deploy:/opt/kolla-ansible$ . /etc/kolla/refstack.sh ; swift --os-auth-url http://192.168.205.254:5000/v3 --auth-version 3 --os-project-name refstack --os-project-domain-name default --os-username refstack --os-user-domain-name default --os-password SECRET capabilities Capabilities GET failed: http://192.168.205.254:8080/info 401 Unauthorized [first 60 chars of response] b'{"error": {"code": 401, "title": "Unauthorized", "message": ' Failed Transaction ID: txc1d8607e26eb4cd587459-0061b7791b It looks like swift client is broken, isn't it ? Or ? Maybe kolla-ansible is creating bad roles and config ? (operator_roles, reselleradmin_roel ..etc ? ) Tempest is from master Thank you very much, Kevko Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>

3 5

[Diversity] D&I WG Meeting Time and IRC vs Video Poll
by Amy Marrich 14 Dec '21

14 Dec '21

Hi everyone, The Diversity and Inclusion WG is holding a poll to see if there would be interest in attending if it were on another day and time as well as if IRC vs Video would be preferred. We currently meet the first Monday of the month at 17:00 UTC. And hope to have a planning meeting as our first meeting of the year. Our first meeting of the new year is slated for January 3rd at 17:00 UTC and for IRC. We will take the poll results into consideration and may cancel the January meeting to allow folks to plan on attending in which case February's meeting would be the first of the year. Please vote for your preferred days and times AND also for IRC and/or Video. https://doodle.com/poll/mnzxkauzwf2isssm?utm_source=poll&utm_medium=link We are keeping to morning hours to encourage participation from EMEA but not overly early for PST folks to attend. We will keep the poll up through the end of the year. Please feel free to reach out with any questions or concerns and remember the Diversity and Inclusion WG is for ALL projects under the Open Infra Foundation! Thanks, Amy (spotz)

1 1

[keystone] OAuth2.0 implementation in Yoga
by Hiromu Asahina 14 Dec '21

14 Dec '21

Hi, Please, could any of the keystone core members give me some advice on this spec? https://review.opendev.org/c/openstack/keystone-specs/+/813152 We'd like to make the following points clear by the end of this year to forward the implementation. So, please kindly check it and please let me know your opinion. - OAuth2.0 scope [1]: As there are differences between OAuth2.0 scope format and the Application credentials access rule format and we haven't found a good solution to map them, we'd like to omit the implementation of the OAuth2.0 scope in Yoga. Is there any concerns? - Access policy configuration: - Which one is appropriate? (i) End-users can use the OAuth2.0 API if they have permission for the OAuth2.0 API even if they don't have permission for the Application credentials API (ii) End-users can use the OAuth2.0 API only if they have permission for both the OAuth2.0 API and the Application credentials API. - API endpoint: - Which one is appropriate? (i) `/identity/v3/auth/OS-OAUTH2/<user_id>/clients` (ii) `/identity/v3/users/{user_id}/OS-AUTH2/clients` (iii) other [1] https://datatracker.ietf.org/doc/html/rfc6749#page-23 Thanks, Hiromu Asahina (h_asahina)

1 0

[nova] Spawning instance that will do PXE booting
by Thomas Goirand 14 Dec '21

14 Dec '21

Hi, In order to test OCI [1] within OpenStack itself, I would need my instances to do PXE booting. This would be with something like this on the qemu command line: qemu-system-x86_64 -boot n I believe this would also mean setting-up network cards that can do PXE booting, like the e1000, which Qemu supports. If that is possible, then I would setup DHCP + tftp-hpa on another instance, wired on the same private network. Your thoughts? Is this possible? Cheers, Thomas Goirand (zigo) [1] https://salsa.debian.org/openstack-team/debian/openstack-cluster-installer

8 18

[all] testtools and support for Python 3.10 (error du to deprecation of distutils)
by Thomas Goirand 14 Dec '21

14 Dec '21

Hi, When I try to build rally-openstack, I get this, in the test discovery: /usr/lib/python3/dist-packages/rally/common/cfg.py:19: in <module> from oslo_config import fixture # noqa /usr/lib/python3/dist-packages/oslo_config/fixture.py:18: in <module> import fixtures /usr/lib/python3/dist-packages/fixtures/__init__.py:81: in <module> from fixtures.fixture import ( /usr/lib/python3/dist-packages/fixtures/fixture.py:34: in <module> from fixtures.callmany import ( /usr/lib/python3/dist-packages/fixtures/callmany.py:31: in <module> MultipleExceptions = try_import( /usr/lib/python3/dist-packages/testtools/helpers.py:30: in try_import __import__(module_name) /usr/lib/python3/dist-packages/testtools/__init__.py:99: in <module> from testtools.distutilscmd import TestCommand /usr/lib/python3/dist-packages/testtools/distutilscmd.py:7: in <module> from distutils.core import Command /usr/lib/python3.10/distutils/__init__.py:19: in <module> warnings.warn(_DEPRECATION_MESSAGE, E DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives This warning makes it impossible to discover rally-openstack tests, because of the imports here: https://github.com/testing-cabal/testtools/blob/master/testtools/distutilsc… Can someone work on removing distutils support from Testtools? Or is there a way to trick pytest to not fail? Help would be greatly appreciated here. Cheers, Thomas Goirand (zigo)

4 8

bug deputy report (week of Dec 6)
by Akihiro Motoki 14 Dec '21

14 Dec '21

Hi, I was a bug deputy last week. Here is a summary of last week. Two needs-attention bugs need what neutron should behave, so they need more investigation. Two OVN bugs and one gate-failure bug also need assignees and investigations. Thanks, Akihiro Motoki (amotoki) # Needs attention - https://bugs.launchpad.net/neutron/+bug/1953478 Resize and shelve server fails in the multinode CI jobs intemittent It was reported to nova by slawek, but gibi moved it to neutron as there is a question on when neutron send vif-plugged event to nova. We need to clarify when the vif-plugged event is sent and what is the expected behavior. - https://bugs.launchpad.net/neutron/+bug/1954384 Neutron doesn't use set dns-domain for Nova instance It would be nice if folks familiar with DNS integration can look into it. # OVN https://bugs.launchpad.net/neutron/+bug/1953510 neutron_ovn_metadata_agent doesn`t work after reconnect to new OVN Southbound leader DB https://bugs.launchpad.net/neutron/+bug/1953295 neutron-ovn-metadata-agent AttributeError: 'MetadataAgent' object has no attribute 'sb_idl' # Gate failures https://bugs.launchpad.net/neutron/+bug/1953479 Timeout in the scenario jobs' execution # Assigned https://bugs.launchpad.net/neutron/+bug/1953716 Improve message in the NetworkInUse exception # In Progress https://bugs.launchpad.net/neutron/+bug/1954316 In VXLAN interface creation, we must provide always a device https://bugs.launchpad.net/neutron/+bug/1954662 Quota driver "DbQuotaNoLockDriver" can lock when removing the expired reservations https://bugs.launchpad.net/neutron/+bug/1953480 Agents API test failed due to not expected "alive" status of the agent

1 0

[wallaby][ovn][Open vSwitch] HA for OVN DB servers using pacemaker
by Faisal Sheikh 14 Dec '21

14 Dec '21

Hi, I am using Openstack Wallaby release with OVN on Ubuntu 20.04. My environment consists of 2 compute nodes and 1 controller node. ovs-vswitchd (Open vSwitch) 2.15.0 Ubuntu Kernel Version: 5.4.0-88-generic - compute node1 172.16.30.1 - compute node2 172.16.30.3 - controller-khi01/Network node/Primary ovs-db IP 172.16.30.46 - backup ovs-db 172.16.30.47 I want to run OVSDB server to run in Active/Passive mode. Active OVSDB-server is on node "controller-khi01" and Passive OVSDB-server is on "controller02-khi01". I have setup Pacemaker to manage the ovn-northd(Open vSwitch) service between primary and backup ovn-db server. You can see the "pcs status" output below. But I am unable to replicate database state between primary and backup OVSDB server. If i execute "ovsdb-server --sync-from=server" command, getting below error. root@controller-khi01# ovsdb-server --sync-from=172.16.30.47 2021-12-14T09:16:29Z|00001|lockfile|WARN|/var/lib/openvswitch/.conf.db.~lock~: cannot lock file because it is already locked by pid 14121 ovsdb-server: I/O error: /etc/openvswitch/conf.db: failed to lock lockfile (Resource temporarily unavailable) root@controller-khi01# pcs status Cluster name: cluster1 Cluster Summary: * Stack: corosync * Current DC: controller-khi01 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Tue Dec 14 07:53:06 2021 * Last change: Tue Dec 14 06:16:21 2021 by hacluster via crmd on controller02-khi01 * 2 nodes configured * 3 resource instances configured Node List: * Online: [ controller-khi01 controller02-khi01 ] Full List of Resources: * Clone Set: ovndb_servers-clone [ovndb_servers] (promotable): * Masters: [ controller-khi01 ] * Slaves: [ controller02-khi01 ] * ovn-virtual-ip (ocf::heartbeat:IPaddr2): Started controller-khi01 Failed Resource Actions: * ovndb_servers_monitor_10000 on controller02-khi01 'master' (8): call=17, status='complete', exitreason='', last-rc-change='2021-12-14 06:48:26Z', queued=0ms, exec=0ms Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: active/enabled I would really appreciate any input in this regard. Best regards, Faisal Sheikh

1 0

[tripleo] Initial plans around stable/wallaby branch on CentOS Stream 9
by Chandan Kumar 14 Dec '21

14 Dec '21

Hello, The tripleo-ci team is working on drafting the plans for bootstrapping tripleo stable/wallaby branch on CentOS Stream 9. During adding the support of CentOS Stream 9 for tripleo master, we have added lots of patches for example: * tripleo-common: https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%252… * tripleo-heat-templates: https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%252… * https://review.opendev.org/q/%28topic:%2522cs9%2522+OR+hashtag:%2522cs9%252… Backporting these patches in chains for stable/wallaby, will create lots of merge conflicts (few of them are big changes) and might get messy. RDO wallaby DLRN builder bootstrap has also started. In order to avoid that, we are coming with following plan: - Pick the major change and backport that one and add all the remaining changes in that itself (not a clean backport): https://review.opendev.org/c/openstack/tripleo-common/+/821511 - Make sure these backported changes passed on CentOS-8 CI jobs - Once the RDO CS9 wallaby packages are available, Start bootstrapping the container and Image build job on CS9 via testproject. Let us know your thoughts around this. Thanks, Chandan Kumar

3 3

[openstack-helm] No Meetings Rest of 2021
by Gage Hugo 13 Dec '21

13 Dec '21

Hey team, Due to the upcoming holidays and the lack of topics for tomorrow's meeting the next 3 meetings are canceled. We will start back up in the new year on Jan 4th at the usual time. Happy Holidays!

1 0

[security][security sig] Retiring the security-specs repo
by Gage Hugo 13 Dec '21

13 Dec '21

Hey folks, The security SIG has been going through the current list of repositories that we are managing and one of them, the "security-specs"[0] repository, has been unused for several years now so the consensus was to retire the repo. If there are no objections, we will look to retire the repo here relatively soon. Should anyone have any other information about it, please let the security SIG know. Thanks! [0] https://github.com/openstack/security-specs

1 0

[nova] Next spec review day on Tuesday Dec 14th
by Sylvain Bauza 13 Dec '21

13 Dec '21

Hola, As agreed during today's Nova meeting, we will have another spec review day on Dec 14th. Please sharpen your pens and write your specs in advance, and just be around during this day if you want to discuss with the reviewers. Thanks, -Sylvain

1 1

[tempest][swift][kolla]
by Michal Arbet 13 Dec '21

13 Dec '21

Hello to eveyrone, Please, could someone help me with swift capabilities not working when I'm tempesting openstack test stack ? Tempest : rm -rf /tmp/tempest-lock/; refstack-client test -v -c /opt/tempest/tempest.conf -- --regex tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest (.venv) root@ca6353106d83:/opt/refstack-client# rm -rf /tmp/tempest-lock/; refstack-client test -v -c /opt/tempest/tempest.conf -- --regex tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest 2021-12-13 17:44:33.001 4358 INFO tempest [-] Using tempest config file /etc/tempest/tempest.conf 2021-12-13 17:44:33,839 refstack_client:518 INFO Starting Tempest test... 2021-12-13 17:44:33.839 4358 INFO refstack_client [-] Starting Tempest test... {0} setUpClass (tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest) [0.000000s] ... FAILED Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/opt/refstack-client/.tempest/tempest/test.py", line 181, in setUpClass raise value.with_traceback(trace) File "/opt/refstack-client/.tempest/tempest/test.py", line 174, in setUpClass cls.resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/test_account_quotas_negative.py", line 36, in resource_setup super(AccountQuotasNegativeTest, cls).resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/base.py", line 95, in resource_setup body = cls.capabilities_client.list_capabilities() File "/opt/refstack-client/.tempest/tempest/lib/services/object_storage/capabilities_client.py", line 32, in list_capabilities self._error_checker(resp, body) File "/opt/refstack-client/.tempest/tempest/lib/common/rest_client.py", line 799, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'} ============================== Failed 1 tests - output below: ============================== setUpClass (tempest.api.object_storage.test_account_quotas_negative.AccountQuotasNegativeTest) ---------------------------------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ Traceback (most recent call last): File "/opt/refstack-client/.tempest/tempest/test.py", line 181, in setUpClass raise value.with_traceback(trace) File "/opt/refstack-client/.tempest/tempest/test.py", line 174, in setUpClass cls.resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/test_account_quotas_negative.py", line 36, in resource_setup super(AccountQuotasNegativeTest, cls).resource_setup() File "/opt/refstack-client/.tempest/tempest/api/object_storage/base.py", line 95, in resource_setup body = cls.capabilities_client.list_capabilities() File "/opt/refstack-client/.tempest/tempest/lib/services/object_storage/capabilities_client.py", line 32, in list_capabilities self._error_checker(resp, body) File "/opt/refstack-client/.tempest/tempest/lib/common/rest_client.py", line 799, in _error_checker raise exceptions.Unauthorized(resp_body, resp=resp) tempest.lib.exceptions.Unauthorized: Unauthorized Details: {'code': 401, 'title': 'Unauthorized', 'message': 'The request you have made requires authentication.'} ====== Totals ====== Ran: 1 tests in 0.0000 sec. - Passed: 0 - Skipped: 0 - Expected Fail: 0 - Unexpected Success: 0 - Failed: 1 Sum of execute time for each test: 0.0000 sec. ============== Worker Balance ============== - Worker 0 (1 tests) => 0:00:00 2021-12-13 17:44:43,144 refstack_client:581 INFO Tempest test complete. 2021-12-13 17:44:43.144 4358 INFO refstack_client [-] Tempest test complete. 2021-12-13 17:44:43,146 refstack_client:582 INFO Subunit results located in: /opt/refstack-client/.tempest/.stestr/137 2021-12-13 17:44:43.146 4358 INFO refstack_client [-] Subunit results located in: /opt/refstack-client/.tempest/.stestr/137 2021-12-13 17:44:43,148 refstack_client:585 INFO Number of passed tests: 0 2021-12-13 17:44:43.148 4358 INFO refstack_client [-] Number of passed tests: 0 2021-12-13 17:44:43,150 refstack_client:597 INFO JSON results saved in: /opt/refstack-client/.tempest/.stestr/137.json 2021-12-13 17:44:43.150 4358 INFO refstack_client [-] JSON results saved in: /opt/refstack-client/.tempest/.stestr/137.json TEMPEST LOG : Response - Headers: {'date': 'Mon, 13 Dec 2021 16:44:41 GMT', 'server': 'Apache', 'content-length': '8013', 'x-subject-token': '<omitted>', 'vary': 'X-Auth-Token', 'x-openstack-request-id': 'req-00b11c98-7ffa-4a1a-88b1-a054fda5d7e9', 'content-type': 'application/json', 'connection': 'close', 'status': '201', 'content-location': 'http://192.168.205.254:35357/v3/auth/tokens'} Body: b'{"token": {"methods": ["password"], "user": {"domain": {"id": "default", "name": "Default"}, "id": "23ebe05900764afaa29f72519d40693a", "name": "refstack", "password_expires_at": null}, "audit_ids": ["4UgDYqQoSla7SWJOdjHXng"], "expires_at": "2021-12-14T16:44:42.000000Z", "issued_at": "2021-12-13T16:44:42.000000Z", "project": {"domain": {"id": "default", "name": "Default"}, "id": "704cf29c27d045199d11a11fe62206b6", "name": "refstack"}, "is_domain": false, "roles": [{"id": "89125ace2bc945af8f12d889c9f5589b", "name": "_member_"}, {"id": "47da66772503466881afc1ae391141e7", "name": "swiftoperator"}, {"id": "e47f85a3982f4a18a44d24d6c2ed6588", "name": "ResellerAdmin"}], "catalog": [{"endpoints": [{"id": "27daafd92ace480da6cf0fcaf4c054d7", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:8000/v1", "region": "RegionOne"}, {"id": "8ffc139d5a6c4d86b06557b01956dcb7", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:8000/v1", "region": "RegionOne"}, {"id": "e4b48ef6f9cd4bbea5f2e0fb9bf16af1", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:8000/v1", "region": "RegionOne"}], "id": "10b7ca67118d45dca197b8ac17f29349", "type": "cloudformation", "name": "heat-cfn"}, {"endpoints": [{"id": "06788107c3d94af9976b9fb4b3011d4f", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:5000", "region": "RegionOne"}, {"id": "0d745366b77546f7bd24259c04810b8b", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:5000", "region": "RegionOne"}, {"id": "1771c125743b4485b818a2aaa4d6f913", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:35357", "region": "RegionOne"}], "id": "1ee3179487894931a223ed3caaf8cdb5", "type": "identity", "name": "keystone"}, {"endpoints": [{"id": "1ce9a0af0c14454aa6043b5efe32dddb", "interface": "internal", "region_id": "RegionOne", "url": " http://192.168.205.254:9001", "region": "RegionOne"}, {"id": "5bcfbaa0af46423ab3de1e789affa187", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:9001", "region": "RegionOne"}, {"id": "cbc613e8806a48ac98cf4cc42cca80f2", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:9001", "region": "RegionOne"}], "id": "493ace4e817d4eae9aa4a1341bd01046", "type": "dns", "name": "designate"}, {"endpoints": [{"id": "18bea710b4284f5387081eac6833dc9e", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:8774/v2/704cf29c27d045199d11a11fe62206b6", "region": "RegionOne"}, {"id": "7f1bd52d8b154bc7973c0f32c57103f9", "interface": "internal", "region_id": "RegionOne", "url": " http://192.168.205.254:8774/v2/704cf29c27d045199d11a11fe62206b6", "region": "RegionOne"}, {"id": "c28543c29f574cc6b4320fba45394a83", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:8774/v2/704cf29c27d045199d11a11fe62206b6", "region": "RegionOne"}], "id": "52d1f52dc8f44e5ba7a40732a660a288", "type": "compute_legacy", "name": "nova_legacy"}, {"endpoints": [{"id": "33d722f6c2cf4865b3487b8c4ce96c14", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:9696", "region": "RegionOne"}, {"id": "4744e2aa77cb4ba186752fb0ef25e9d3", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:9696", "region": "RegionOne"}, {"id": "4a980da3677c429ebf645a0e1733949c", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:9696", "region": "RegionOne"}], "id": "56866ea275ec4f5e8f805a08f040c8e0", "type": "network", "name": "neutron"}, {"endpoints": [{"id": "4550e2b070aa4bd6a07ab00d72ef4266", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:8780", "region": "RegionOne"}, {"id": "86fc799751384f709c450db05d523d93", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:8780", "region": "RegionOne"}, {"id": "bfb36483e5dc40a5bfbf1b4ae6bf60cb", "interface": "internal", "region_id": _log_request_full /opt/refstack-client/.tempest/tempest/lib/common/rest_client.py:450 2021-12-13 17:44:42.789 4369 INFO tempest.lib.common.rest_client [req-4ee89585-59ff-4f5a-8ba3-9eebb1d5e6aa ] Request (AccountQuotasNegativeTest:setUpClass): 201 POST http://192.168.205.254:35357/v3/auth/tokens 0.548s 2021-12-13 17:44:42.790 4369 DEBUG tempest.lib.common.rest_client [req-4ee89585-59ff-4f5a-8ba3-9eebb1d5e6aa ] Request - Headers: {'Content-Type': 'application/json', 'Accept': 'application/json'} Body: <omitted> Response - Headers: {'date': 'Mon, 13 Dec 2021 16:44:42 GMT', 'server': 'Apache', 'content-length': '8015', 'x-subject-token': '<omitted>', 'vary': 'X-Auth-Token', 'x-openstack-request-id': 'req-4ee89585-59ff-4f5a-8ba3-9eebb1d5e6aa', 'content-type': 'application/json', 'connection': 'close', 'status': '201', 'content-location': 'http://192.168.205.254:35357/v3/auth/tokens'} Body: b'{"token": {"methods": ["password"], "user": {"domain": {"id": "default", "name": "Default"}, "id": "adcde758a0d5439ba6f8a1a35d641726", "name": "refstack2", "password_expires_at": null}, "audit_ids": ["0clvtk_FQQWVN-RRLSkCWg"], "expires_at": "2021-12-14T16:44:42.000000Z", "issued_at": "2021-12-13T16:44:42.000000Z", "project": {"domain": {"id": "default", "name": "Default"}, "id": "2aabe1b9860c44a08eabdc3133538089", "name": "refstack2"}, "is_domain": false, "roles": [{"id": "e47f85a3982f4a18a44d24d6c2ed6588", "name": "ResellerAdmin"}, {"id": "47da66772503466881afc1ae391141e7", "name": "swiftoperator"}, {"id": "89125ace2bc945af8f12d889c9f5589b", "name": "_member_"}], "catalog": [{"endpoints": [{"id": "27daafd92ace480da6cf0fcaf4c054d7", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:8000/v1", "region": "RegionOne"}, {"id": "8ffc139d5a6c4d86b06557b01956dcb7", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:8000/v1", "region": "RegionOne"}, {"id": "e4b48ef6f9cd4bbea5f2e0fb9bf16af1", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:8000/v1", "region": "RegionOne"}], "id": "10b7ca67118d45dca197b8ac17f29349", "type": "cloudformation", "name": "heat-cfn"}, {"endpoints": [{"id": "06788107c3d94af9976b9fb4b3011d4f", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:5000", "region": "RegionOne"}, {"id": "0d745366b77546f7bd24259c04810b8b", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:5000", "region": "RegionOne"}, {"id": "1771c125743b4485b818a2aaa4d6f913", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:35357", "region": "RegionOne"}], "id": "1ee3179487894931a223ed3caaf8cdb5", "type": "identity", "name": "keystone"}, {"endpoints": [{"id": "1ce9a0af0c14454aa6043b5efe32dddb", "interface": "internal", "region_id": "RegionOne", "url": " http://192.168.205.254:9001", "region": "RegionOne"}, {"id": "5bcfbaa0af46423ab3de1e789affa187", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:9001", "region": "RegionOne"}, {"id": "cbc613e8806a48ac98cf4cc42cca80f2", "interface": "public", "region_id": "RegionOne", "url": "https://api.refstack.ultimum.cloud:9001", "region": "RegionOne"}], "id": "493ace4e817d4eae9aa4a1341bd01046", "type": "dns", "name": "designate"}, {"endpoints": [{"id": "18bea710b4284f5387081eac6833dc9e", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:8774/v2/2aabe1b9860c44a08eabdc3133538089", "region": "RegionOne"}, {"id": "7f1bd52d8b154bc7973c0f32c57103f9", "interface": "internal", "region_id": "RegionOne", "url": " http://192.168.205.254:8774/v2/2aabe1b9860c44a08eabdc3133538089", "region": "RegionOne"}, {"id": "c28543c29f574cc6b4320fba45394a83", "interface": "admin", "region_id": "RegionOne", "url": " http://192.168.205.254:8774/v2/2aabe1b9860c44a08eabdc3133538089", "region": "RegionOne"}], "id": "52d1f52dc8f44e5ba7a40732a660a288", "type": "compute_legacy", "name": "nova_legacy"}, {"endpoints": [{"id": "33d722f6c2cf4865b3487b8c4ce96c14", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:9696", "region": "RegionOne"}, {"id": "4744e2aa77cb4ba186752fb0ef25e9d3", "interface": "internal", "region_id": "RegionOne", "url": "http://192.168.205.254:9696", "region": "RegionOne"}, {"id": "4a980da3677c429ebf645a0e1733949c", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:9696", "region": "RegionOne"}], "id": "56866ea275ec4f5e8f805a08f040c8e0", "type": "network", "name": "neutron"}, {"endpoints": [{"id": "4550e2b070aa4bd6a07ab00d72ef4266", "interface": "admin", "region_id": "RegionOne", "url": "http://192.168.205.254:8780", "region": "RegionOne"}, {"id": "86fc799751384f709c450db05d523d93", "interface": "public", "region_id": "RegionOne", "url": " https://api.refstack.ultimum.cloud:8780", "region": "RegionOne"}, {"id": "bfb36483e5dc40a5bfbf1b4ae6bf60cb", "interface": "internal", "region_id _log_request_full /opt/refstack-client/.tempest/tempest/lib/common/rest_client.py:450 2021-12-13 17:44:42.849 4369 INFO tempest.lib.common.rest_client [tx815e181e33fb4854b2631-0061b7787a ] Request (AccountQuotasNegativeTest:setUpClass): 401 GET https://api.refstack.ultimum.cloud:8080/info 0.049s 2021-12-13 17:44:42.849 4369 DEBUG tempest.lib.common.rest_client [tx815e181e33fb4854b2631-0061b7787a ] Request - Headers: {'Content-Type': 'application/json', 'Accept': 'application/json'} Body: None Response - Headers: {'content-type': 'application/json', 'content-length': '114', 'www-authenticate': 'Keystone uri=" http://192.168.205.254:5000"', 'x-trans-id': 'tx815e181e33fb4854b2631-0061b7787a', 'x-openstack-request-id': 'tx815e181e33fb4854b2631-0061b7787a', 'date': 'Mon, 13 Dec 2021 16:44:42 GMT', 'connection': 'close', 'status': '401', 'content-location': ' https://api.refstack.ultimum.cloud:8080/info'} Body: b'{"error": {"code": 401, "title": "Unauthorized", "message": "The request you have made requires authentication."}}' _log_request_full /opt/refstack-client/.tempest/tempest/lib/common/rest_client.py:450 Test from command line and from curl . /etc/kolla/refstack.sh ; curl -H "X-Auth-Token: $(openstack token issue -f value -c id)" https://api.refstack.ultimum.cloud:8080/info /usr/lib/python3/dist-packages/secretstorage/dhcrypto.py:15: CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead from cryptography.utils import int_from_bytes /usr/lib/python3/dist-packages/secretstorage/util.py:19: CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead from cryptography.utils import int_from_bytes {"swift": {"version": "2.27.1.dev9", "strict_cors_mode": true, "policies": [{"name": "Policy-0", "aliases": "Policy-0", "default": true}], "allow_account_management": true, "account_autocreate": true, "max_file_size": 5368709122, "max_meta_name_length": 128, "max_meta_value_length": 256, "max_meta_count": 90, "max_meta_overall_size": 4096, "max_header_size": 8192, "max_object_name_length": 1024, "container_listing_limit": 10000, "account_listing_limit": 10000, "max_account_name_length": 256, "max_container_name_length": 256, "extra_header_count": 0}, "container_sync": {"realms": {}}, "bulk_upload": {"max_containers_per_extraction": 10000, "max_failed_extractions": 1000}, "bulk_delete": {"max_deletes_per_request": 10000, "max_failed_deletes": 1000}, "tempurl": {"methods": ["GET", "HEAD", "PUT", "POST", "DELETE"], "incoming_remove_headers": ["x-timestamp"], "incoming_allow_headers": [], "outgoing_remove_headers": ["x-object-meta-*"], "outgoing_allow_headers": ["x-object-meta-public-*"], "allowed_digests": ["sha1", "sha256", "sha512"]}, "ratelimit": {"account_ratelimit": 0.0, "max_sleep_time_seconds": 60.0, "container_ratelimits": [], "container_listing_ratelimits": []}, "container_quotas": {}, "account_quotas": {}, "slo": {"max_manifest_segments": 1000, "max_manifest_size": 8388608, "yield_frequency": 10, "min_segment_size": 1, "allow_async_delete": false}} Swiftclient : ubuntu@deploy:/opt/kolla-ansible$ . /etc/kolla/refstack.sh ; swift --os-auth-url http://192.168.205.254:5000/v3 --auth-version 3 --os-project-name refstack --os-project-domain-name default --os-username refstack --os-user-domain-name default --os-password refstack capabilities /usr/lib/python3/dist-packages/secretstorage/dhcrypto.py:15: CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead from cryptography.utils import int_from_bytes /usr/lib/python3/dist-packages/secretstorage/util.py:19: CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead from cryptography.utils import int_from_bytes Capabilities GET failed: http://192.168.205.254:8080/info 401 Unauthorized [first 60 chars of response] b'{"error": {"code": 401, "title": "Unauthorized", "message": ' Failed Transaction ID: txc1d8607e26eb4cd587459-0061b7791b It looks like swift client is broken, isn't it ? Thank you very much, Kevko Michal Arbet Openstack Engineer Ultimum Technologies a.s. Na Poříčí 1047/26, 11000 Praha 1 Czech Republic +420 604 228 897 michal.arbet(a)ultimum.io *https://ultimum.io <https://ultimum.io/>* LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | Twitter <https://twitter.com/ultimumtech> | Facebook <https://www.facebook.com/ultimumtechnologies/timeline>

1 0

Is heat-cfntools still an active project?
by Thomas Goirand 13 Dec '21

13 Dec '21

Hi, The last release of heat-cfntools was in 2016, and in Debian, we're considering removing removing boto (as boto is unmaintained upstream, replaced by boto3). If nobody does anything, we may remove both boto and heat-cfntools from Debian. Thoughts anyone? Cheers, Thomas Goirand (zigo)

2 1

[CLOUDKITTY] Missed CloudKitty meeting today
by Rafael Weingärtner 13 Dec '21

13 Dec '21

Hello guys, I would like to apologize for missing the CloudKitty meeting today. I was concentrating on some work, and my alarm for the meeting did not ring. Isee that you guys already merged some things, thanks for picking the meeting up. I will add more alarms in my calendar, to avoid this situation in the future. If you need something, just let me know. Again, sorry for the inconvenience; see you guys at our next meeting. -- Rafael Weingärtner

1 0

[Triple0][Undercloud ] Deployment failed because of Bonds
by Lokendra Rathour 13 Dec '21

13 Dec '21

Hi Team, we have created a bond with name bond-mgmt for the provisioning n/w and passed that name as local interface: Undercloud.conf: *..* *..* *# Network interface on the Undercloud that will be handling the PXE* *# boots and DHCP for Overcloud instances. (string value)* *local_interface = bond-mgmt* *..* *..* Because of this undercloud deployment is getting failed with the error as below: [root@localhost ~]# ovs-vsctl show b3db7071-58f7-4201-8fd5-9577dec0020e Bridge br-ctlplane fail_mode: standalone Port bond-mgmt Interface bond-mgmt error: "could not open network device bond-mgmt (No such device)" Port br-ctlplane Interface br-ctlplane type: internal ovs_version: "2.12.0" [root@localhost ~]# Query: - is bonding supported in Undercloud installation for provisioning n/w? - if yes then what is the correct way to do so. we are trying to deploy Train on Centos 8. -- ~ Lokendra skype: lokendrarathour

2 5

[nova][cinder][devstack][qa] ceph installs python3-logutils which conflicts with neutron
by Sean Mooney 13 Dec '21

13 Dec '21

hi o/ gibi noticed that the nova-ceph-multistore job started failing this morning with ERROR: Cannot uninstall 'logutils'. It is a distutils installed project and thus we cannot accurately determine which files belong to it which would lead to only a partial uninstall. https://bugs.launchpad.net/nova/+bug/1954427 we quickly identifed that python3-logutils was beeing pulled in by the devstack-plugin-ceph as a sideeffect fo installing ceph. functions-common:apt_get:1207 : sudo DEBIAN_FRONTEND=noninteractive http_proxy= https_proxy= no_proxy= apt-get --option Dpkg::Options::=--force-confold --assume-yes install ceph libnss3- tools python3-rados python3-rbd Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: libboost-iostreams1.71.0 libboost-thread1.71.0 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ceph-base ceph-common ceph-mgr ceph-mgr-modules-core ceph-mon ceph-osd libbabeltrace1 libcephfs2 libdw1 libgoogle-perftools4 libjaeger libleveldb1d liblttng-ust-ctl4 liblttng-ust0 libnuma1 liboath0 librabbitmq4 librados2 libradosstriper1 librbd1 librdkafka1 librgw2 libsnappy1v5 libtcmalloc-minimal4 liburcu6 logrotate python-pastedeploy-tpl python3-bcrypt python3-bs4 python3-ceph-argparse python3-ceph-common python3-cephfs python3-cffi-backend python3-cherrypy3 python3-cryptography python3-dateutil python3-jwt python3-logutils python3-mako python3-markupsafe python3-openssl python3-paste python3-pastedeploy python3-pecan python3-prettytable python3-rgw python3-simplegeneric python3-singledispatch python3-soupsieve python3-tempita python3-waitress python3-webob python3-webtest python3-werkzeug to adress this i have proposed a patch based on how we workaround unremovable python packages in devstack fixup_tools script too the devstack-plugin-ceph repo to adress this. https://review.opendev.org/c/openstack/devstack-plugin-ceph/+/821396/ untill that merges expect to see all ceph based jobs to fail when installing neutron. regards sean

2 1