January 2022 - openstack-discuss - lists.openstack.org

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

[neutron] Bug Deputy Report January 03 - 10
by Lucas Alvares Gomes 11 Apr '22

11 Apr '22

Hi, This is the Neutron bug report from January 3rd to 10th. Critical: * https://bugs.launchpad.net/neutron/+bug/1956344 - "Functional test test_gateway_chassis_rebalance is failing intermittently" - Assigned to: Rodolfo Alonso High: * https://bugs.launchpad.net/neutron/+bug/1956034 - "ovn load balancer health monitor cause mac address conflict" - Unassigned * https://bugs.launchpad.net/neutron/+bug/1956745 - " [ovn-octavia-provider] Load Balancer remained with ACTIVE state even with PENDING_UPDATE listener" - Assigned to: Luis Tomas Bolivar * https://bugs.launchpad.net/neutron/+bug/1956763 - "[OVN] Overlapping configuration for security group logging is not applied correctly" - Assigned to: Elvira Garcia Ruiz Medium: * https://bugs.launchpad.net/neutron/+bug/1956035 - "ovn load balancer member failover not working when accessed from floating ip" - Unassigned * https://bugs.launchpad.net/neutron/+bug/1956632 - "DNS integration documentation and scenario tests need update after dns_assignment calculation was changed" - Assigned to: Miguel Lavalle * https://bugs.launchpad.net/neutron/+bug/1956785 - "Duplicate validator TypeError for dict values Edit" - Assigned to: Harald Jensås Low: * https://bugs.launchpad.net/neutron/+bug/1956476 - "[OVN] Disallow multiple physnets per bridge" - Assigned to: Rodolfo Alonso * https://bugs.launchpad.net/neutron/+bug/1956770 - " keepalived no_track implemented in >= 2.0.3" - Assigned to: Rodolfo Alonso Needs further triage: * https://bugs.launchpad.net/neutron/+bug/1956435 - "OVS: support multiple segments per host" - Unassigned * https://bugs.launchpad.net/neutron/+bug/1956460 - "The VM can't get metadata from dhcp-agent" - Unassigned * https://bugs.launchpad.net/neutron/+bug/1956846 - "ha router duplicated routes" - Unassigned Cheers, Lucas

4 7

[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

[infra] gerrit is:mergeable predicate
by Brian Rosmaita 15 Mar '22

15 Mar '22

Hello Infra team, In Gerrit 3.4, the is:mergeable predicate is disabled by default [0]. It was kind of handy to be able to screen out patches that are in merge conflict when looking for reviews. Is there an alternative way of doing this, or would you be averse to restoring the previous behavior? (I promise not to complain about gerrit performance.) cheers, brian [0] https://www.gerritcodereview.com/3.4.html#ismergeable-predicate-is-disabled…

2 3

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

28 Feb '22

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

5 10

[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

[puppet][tc] Propose changing the release model to cycle-with-rc
by Takashi Kajinami 14 Feb '22

14 Feb '22

Hello, I already discussed this with a few cores last year but I'm raising this topic in ML to make an official decision. Currently Puppet OpenStack is following cycle-with-intermediary and creates a release every milestone. However our code is tightly related to the actual service implementations and having only puppet releases is not very useful. Considering the above point, and effort required to cut off releases per milestone, I'll propose changing our release model to cycle-with-rc , and creating a single release. Because we already created milestone releases for Yoga, I'm thinking of applying the change from next cycle(Z). Please let me know if you have any concerns. Thank you, Takashi

5 5

[Skyline] Project mascot to review
by James Cole 09 Feb '22

09 Feb '22

Greetings everyone, I’m James, a designer with the OpenInfra Foundation. We have a been working on a new project mascot for Skyline and wanted to share a couple of options with you. The reference we were provided alluded to a nine-color-deer, so we created a deer illustration in the style of the other project mascots. The two options are essentially the same, but one is white with spots and the other is yellow with spots. Let me know if you like one or the other—or if we’re totally off on the theme—and we will add the text to the logo and finalize the assets. There is a PDF attached to this message or you can view the document by visiting this link <https://www.dropbox.com/s/d2ikaphzhml7tqb/20220120%20Mascots%20Project.pdf?…>. Thank you! -James

11 20

[kolla] [horizon] Custom logos (WAS: [Openstack-operators] Horizon Custom Logos (Queens, 13.0.1))
by Gregory Orange 09 Feb '22

09 Feb '22

We have been using Ubuntu VMs for the control plane until now, so it was a simple matter of inserting our logo-splash.svg and logo.svg into /var/lib/openstack-dashboard/static/dashboard/img/ and then restarting services. Now we're switching to Kolla, and the relevant path isn't mounted as is the case with the likes of /etc/kolla/horizon and /var/log/kolla. We don't (yet?) build our own container images, so I'm wondering what next. Did anyone get any further with this? On 21/8/18 9:28 pm, Nick Jones wrote: > Hi Erich. > > Yeah, I battled against this myself quite recently. Here's what I did > to add a logo to the Horizon splash page and to the header of each page > itself. > > Create a file called _splash.html, containing: > > <div class="text-center"> > <img class="splash-logo" src={% themable_asset "img/logo.png" %}> > </div> > > And a file called _brand.html, containing: > > {% load branding %} > {% load themes %} > > <a class="navbar-brand" href="{% site_branding_link %}" target="_self"> > <img class="openstack-logo" src="{% themable_asset 'img/logo.png' %}" > alt="{% site_branding %}"> > </a> > > I then created a folder > called /usr/share/openstack-dashboard/openstack_dashboard/themes/default/templates/auth/ > and copied _splash.html into there, copied _brand.html > into /usr/share/openstack-dashboard/openstack_dashboard/templates/header/, > and finally my 'logo.png' was copied > into /usr/lib/python2.7/site-packages/openstack_dashboard/static/dashboard/img/ > > Note that this approach might differ slightly from your setup, as in my > case it's a Kolla-based deployment so these changes are applied to the > image I'm using to deploy a Horizon container. But it's the same > release (Queens) and a CentOS base image, so in principle the steps > should work for you. > > Hope that helps. > > -- > > -Nick > > On 20 August 2018 at 17:40, Erich Weiler <weiler(a)soe.ucsc.edu > <mailto:weiler@soe.ucsc.edu>> wrote: > > Hi Y'all, > > I've been banging my head against a wall for days on this item and > can't find anything via google on how to get around it - I am trying > to install a custom logo onto my Horizon Dashboard front page (the > splash page). I have my logo ready to go, logo-splash.png. I have > tried following the instructions here on how to install a custom logo: > > https://docs.openstack.org/horizon/queens/admin/customize-configure.html > <https://docs.openstack.org/horizon/queens/admin/customize-configure.html> > > But it simply doesn't work. It seems this stanza... > > #splash .login { > background: #355796 url(../img/my_cloud_logo_medium.png) no-repeat > center 35px; > } > > ...doesn't actually replace the logo (which is logo-splash.svg), it > only seems to put my file, logo-splash.png as the *background* to > the .svg logo. And since the option there is "no-repeat center", it > appears *behind* the svg logo and I can't see it. I played around > with those options, removing "no-repeat" for example, and it > dutifully shows my logo repeating in the background. But I need the > default logo-splash.svg file to actually be gone and my logo to > exist in it's place. Maybe I'm missing something simple? > > I'm restarting apache and memchached after every change I make when > I was testing. > > And because the images directory is rebuilt every time I restart > apache, I can't even copy in a custom logo-splash.svg file. Which > wouldn't help anyway, as I want my .png file in there instead. I > don't have the means to create a .svg file at this time. ;) > > Help! > > As a side note, I'm using the Queens distribution via RedHat. > > Many thanks in advance, > erich > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators(a)lists.openstack.org > <mailto:OpenStack-operators@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators> > > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- Gregory Orange Cloud System Administrator Scientific Platforms Team building representative Pawsey Supercomputing Centre, CSIRO

3 3

[cinder] new driver freeze & exceptions
by Brian Rosmaita 03 Feb '22

03 Feb '22

Hello Argonauts, The new driver merge deadline passed at 20:00 UTC today. I'm extending the new driver merge deadline to Friday 28 January at 20:00 UTC for two drivers: 1. Lightbits: It has both a cinder and os-brick patch, and I want the team to have more time to look at the os-brick patch. I think the driver patch is close to ready; the developers have been quick to respond to comments and make revisions. Also, the third-party CI is functioning and responding on patches. cinder: https://review.opendev.org/c/openstack/cinder/+/821602 os-brick: https://review.opendev.org/c/openstack/os-brick/+/821603 2. NEC Storage V Series: the driver patch has one +2 and the third party CI is functioning and responding on patches; I don't see any reason to make this one wait for the Z release. https://review.opendev.org/c/openstack/cinder/+/815614 Cinder core reviewers: please continue to review the above patches. With respect to the other proposed drivers: - Pure Storage NVMe-RoCE: vendor decided to hold it for Z - Dell EMC PowerStore NFS driver: vendor decided to hold it for Z - HPE XP Storage FC & iSCSI: the code is very straightforward, but the CI is not ready yet, so this will have to wait for Z - YADRO Tatlin.UNIFIED driver: initial patch arrived yesterday (and has a -1 from Zuul); the CI appears to be running, but the cinder team needs to move on to reviewing os-brick and Yoga feature patches, so this will have to wait for Z also cheers, brian

3 4

[TripleO] Gate blocker - opstools repo
by Ronelle Landy 01 Feb '22

01 Feb '22

Hello All, We have an issue with tripleo-ci-centos-8-content-provider <https://zuul.opendev.org/t/openstack/build/b05d7482835f4b4d83180c29b12973b0> among other tests failing in check/gate due to missing 'centos-opstools' repo. Details are in: https://bugs.launchpad.net/tripleo/+bug/1959619. There are a few patch in flight to try address this issue: https://review.rdoproject.org/r/c/rdo-infra/ansible-role-dlrn/+/38673 - Use opstools packages from trunk.rdoproject.org in cs8 https://review.opendev.org/c/openstack/tripleo-quickstart/+/827111/ - Adds temporary rdoproject repo for collectd/opstools Centos-8 Please hold rechecks until we manage to merge the fixes. Thank you!

2 3

[all][infra][qa][tripleo][openstack-ansible][rally][aodh][cinder][kolla][chef][sahara] CentOS 8 EOL and removal from CI label/image lists
by Clark Boylan 01 Feb '22

01 Feb '22

As noted last month the OpenDev [0] team intends on removing CentOS 8 images from our CI system now that the release has gone EOL. A number of you have already shifted over to CentOS 8 Stream in CI (thank you!), but there is still quite a bit remaining based on codesearch and some manual digging. The OpenDev team has begun the process of removing some of the supporting infrastructure and testing as well [1]. This list is probably not comprehensive but is a start. These projects will need to look at removing their CentOS 8 CI jobs (optionally replacing them with CentOS 8 Stream jobs): * devstack (victoria and older branches) * tripleo-validations * tripleo-upgrade * openstack-ansible * rally * aodh * cinderlib * kolla-ansible * openstack-chef * sahara * tenks * validations-common * validations-lib One thing to keep in mind is that stable branches may also be affected. We'd like to do this cleanup as gracefully as possible, but reality is that some projects are unlikely to completely remove their use of CentOS 8. I think that we can give it until the end of January before we force merge updates to remove the nodeset and label from our configs. At that point any Zuul configuration still using CentOS 8 will enter an error state and correcting it will be necessary to make updates to those Zuul configs. [0] https://lists.opendev.org/pipermail/service-announce/2021-December/000029.h… [1] https://review.opendev.org/q/topic:%22remove-centos-8%22+status:open

7 8

[requirements] The version of zeroconf in upper constraints no longer supports python3.6
by William Szumski 01 Feb '22

01 Feb '22

The zeroconf package seems to have dropped support for python3.6 since 0.38.0, see: https://github.com/jstasiak/python-zeroconf#0380. We currently have 0.38.1 in upper-constraints. My understanding was that the yoga release would still support python3.6. This is important for RHEL8 based distributions that only ship python3.6. Do we need to constrain zeroconf to a version <=0.37.0?

7 6

[infra] Issue with the new pip
by Radosław Piliszek 01 Feb '22

01 Feb '22

Hi! It seems that the new pip is breaking on infra's package indices. Several jobs crash with: """ ValueError: HTML doctype missing or incorrect. Expected <!DOCTYPE html>. If you believe this error to be incorrect, try passing the command line option --use-deprecated=html5lib and please leave a comment on the pip issue at https://github.com/pypa/pip/issues/10825. [0m [31m """ Example from kolla: https://zuul.opendev.org/t/openstack/build/e1bab19dd7c1487e93afeb67284a695e Example from manila: https://zuul.opendev.org/t/openstack/build/984ed9f10f0845ceba59b573e25bbb87 -yoctozepto

4 6

[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][placement] Openstack only building one VM per machine in cluster, then runs out of resources
by Eugen Block 01 Feb '22

01 Feb '22

Hi all, I would like to follow up on a discussion from last year [1] since the issue is still present. In a fresh Victoria deployment we faced the same issue and my colleague tracked it down to a reoccuring issue within MariaDB [2]. Quoting from his response to a different thread [3]: ---snip--- MariaDB is version 10.6.5. When running placement API in debug mode, its log reveals a message like "Over capacity for VCPU on resource provider . Needed: 1, Used: 4118, Capacity: 768.0" but checking the entries in the placement db / allocations table shows that "4118" is the sum of all resources for the resource provided, not only for the CPU class. The problem results from errors in the DBMS handling the "outer join" with a subquery while retrieving the currently allocated resources. ---snip--- We found a workaround for this environment, but I wanted to bring some more attention to this, hoping that this will be fixed in MariaDB. Regards, Eugen [1] https://lists.openstack.org/pipermail/openstack-discuss/2021-July/023430.ht… [2] https://jira.mariadb.org/browse/MDEV-25714 [3] https://serverfault.com/questions/1064579/openstack-only-building-one-vm-pe…

2 1

[ironic] Deprecate/Remove PowerPC prep partition support?
by Julia Kreger 31 Jan '22

31 Jan '22

Greetings folks, I've been curious if anyone sees a reason to keep PowerPC PReP partition support in Ironic? A few things to consider: * This is/was to support partition images. * We generally shy away from partition images at this point. We recommend whole disk images. * PowerPC.... And I don't think many (any?) operators will be doing power deployments of Z* and beyond OpenStack once it is released. * This is not tested in CI, because Power hardware... Thoughts? Feelings? Concerns? -Julia

1 0

[all][tc] Technical Committee next weekly meeting on Feb 3rd at 1500 UTC
by Ghanshyam Mann 31 Jan '22

31 Jan '22

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

1 0

[job] What is the best list for posting an OpenStack job opening?
by Chris DiLorenzo 31 Jan '22

31 Jan '22

Hello, My company has an open position for an OpenStack engineer. We haven't gotten a lot of traction or the candidates we do get lack the OpenStack experience we're looking for. Is it appropriate to post here? Thanks Chris

3 2

[watcher][core] Resignation from Watcher core
by info＠dantalion.nl 31 Jan '22

31 Jan '22

Dear all, Unfortunately I have had increasingly little available free time to spent on the Watcher project over the years. Combined with loss of access to a test environment to debug an actual Watcher deployment for which it has become apparent it will not be reinstated. These combined events inhibit me from effectively making and reviewing patches. As of such I feel it is only right to resign as Watcher core reviewer. I will remove my roles from opendev and launchpad where appropriate as well as remove myself as reviewer from any pending patches. Kind regards & stay safe, Corne (Dantali0n)

1 0

[neutron] Bug Deputy Report January 24 - 30
by Nurmatov Mamatisa 31 Jan '22

31 Jan '22

Hi, I was bug deputy last week. Below is the week summary. I would like to highlight critical bug that affects CI and unassigned #1955008 '[functional] Failure of "test_floatingip_mac_bindings"' Also let me ask OVN team to help with triage OVN related bugs (end of list below). Details: Critical --------- - https://bugs.launchpad.net/neutron/+bug/1955008 - [functional] Failure of "test_floatingip_mac_bindings" - Confirmed - Unassigned! Note: Reported in December but was new occurrences - https://bugs.launchpad.net/neutron/+bug/1959196 - New Secure RBAC policies broke devstack-enforce-scope job - Confirmed - Assigned to Slawek Kaplonski High ---- - https://bugs.launchpad.net/neutron/+bug/1959028 - [OVN][Octavia] Fix the functional CI jobs - Fix Released: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826323 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/1959176 - neutron fullstack/functional jobs TIMED_OUT randomly - Confirmed - Unassigned - https://bugs.launchpad.net/neutron/+bug/1959151 - Don't set HA ports down while L3 agent restart - In progress: https://review.opendev.org/c/openstack/neutron/+/826545 - Assigned to Krzysztof Tomaszewski Medium ------ - https://bugs.launchpad.net/neutron/+bug/1959125 - OVN mech driver failing to check the L2/L3 connectivity - In progress: https://review.opendev.org/c/openstack/neutron/+/826502 - Assigned to Rodolfo Alonso - https://bugs.launchpad.net/neutron/+bug/1959331 - Router's external gateway isn't properly updated when new subnet is added - In progress: https://review.opendev.org/c/openstack/neutron/+/826828 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959332 - With new secure RBAC external gateway ports can't be visible in the API - Confirmed - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959333 - Error 500 after request with Invalid Scope - In progress: https://review.opendev.org/c/openstack/neutron/+/826872 - Assigned to Slawek Kaplonski - https://bugs.launchpad.net/neutron/+bug/1959184 - [tempest] Test "test_list_policy_filter_by_name" failing - Fix released: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/826827 - Assigned to yatin - https://bugs.launchpad.net/neutron/+bug/1958964 - Fully Populated Load Balancer creation with OVN provider leaves pools as PENDING_CREATE - In progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826257 - Assigned to Fernando Royo Undecided --------- - https://bugs.launchpad.net/neutron/+bug/1959098 - [ovn] metadata route missing on the guest - New - Unassigned - https://bugs.launchpad.net/neutron/+bug/1958961 - [ovn-octavia-provider] lb create failing with with ValueError: invalid literal for int() with base 10: '24 2001:db8::131/64' - In progress: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/826896 - Assigned to Slawek Kaplonski Thanks, Mamatisa --- Advanced Software Technology Lab Huawei, Moscow

2 1

[neutron] CI meeting 1.02.2022 cancelled
by Slawek Kaplonski 31 Jan '22

31 Jan '22

Hi, Due to overlapping internal meetings tomorrow I have to cancel this week Neutron CI meeting. Next week I will be on PTO but meeting (8.02) will be chair by ralonsoh - thx for that. I will be back on the CI meetings in two weeks - 15.02. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Re: Can neutron-fwaas project be revived?
by Heng Zhou (周恒)-浪潮数据 30 Jan '22

30 Jan '22

Hi Lajos， I understand that the process is to retire neutron-fwaas first, and then create a new project in the X namespace. If want to retire the project, do we need to wait until the stable version(Victoria) of the project is no longer maintained(Extended Maintenance estimated 2022-04-27)? 发件人: Lajos Katona [mailto:katonalala@gmail.com] 发送时间: 2022年1月18日 0:15 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com> 抄送: miguel(a)mlavalle.com; openstack-discuss(a)lists.openstack.org; Heng Zhou (周恒)-浪潮数据 <zhouhenglc(a)inspur.com> 主题: Re: Can neutron-fwaas project be revived? Hi, Neutron team discussed this question on the Drivers meeting, see the logs: https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.… The agreement is to move neutron-fwaas to x/ namespace, and revive it as x/neutron-fwaas. Best regards Lajos Katona (lajoskatona) Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > ezt írta (időpont: 2022. jan. 6., Cs, 2:30): Hi，Miguel， Ok，let’s meet at January 14th. Best regards 发件人: Miguel Lavalle [mailto:miguel@mlavalle.com <mailto:miguel@mlavalle.com> ] 发送时间: 2022年1月6日 9:12 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > 抄送: openstack-discuss(a)lists.openstack.org <mailto:openstack-discuss@lists.openstack.org> 主题: Re: Can neutron-fwaas project be revived? Hi Qin, Unfortunately, this coming January 7th several members of the drivers team will be off on holiday. We won't have a quorum to discuss your proposal. I hope that January 14th works for you and your team. Best regards Miguel On Fri, Dec 24, 2021 at 10:18 AM Miguel Lavalle <miguel(a)mlavalle.com <mailto:miguel@mlavalle.com> > wrote: Hi Qin, I have added this topic to the drivers meeting agenda (see on demand agenda close to the bottom): https://wiki.openstack.org/wiki/Meetings/NeutronDrivers Cheers On Thu, Dec 23, 2021 at 7:42 PM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi Miguel, Thank you for your suggestion. My colleague HengZhou will submit relevant documents as soon as possible in accordance with the official neutron rules. Yes，we will attend the neutron drivers meeting on January 7th. Merry Christmas! Best wish for you! 发件人: Miguel Lavalle [mailto:miguel@mlavalle.com <mailto:miguel@mlavalle.com> ] 发送时间: 2021年12月24日 0:43 收件人: Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > 抄送: openstack-discuss(a)lists.openstack.org <mailto:openstack-discuss@lists.openstack.org> 主题: Re: Can neutron-fwaas project be revived? Hi Qin, In preparation for your meeting with the drivers team, I suggest we follow as a starting point the Neutron Stadium Governance rules and processes as outlined in the official documentation: https://docs.openstack.org/neutron/latest/contributor/stadium/governance.ht…. In the past, we have re-incorporated projects to the Stadium, like for example in the case of neutron-vpnaas. This document in the Neutron specs repo summarizes how we assessed the readiness of vpnaas for the stadium: https://specs.openstack.org/openstack/neutron-specs/specs/stadium/queens/ne… (https://review.opendev.org/c/openstack/neutron-specs/+/506012) I suggest you start a similar document for fwaas in the folder for the current cycle: https://specs.openstack.org/openstack/neutron-specs/specs/yoga/index.html. As soon as you can, please push it to gerrit, so we can start reviewing it. Did I understand correctly that you will attend the drivers meeting on January 7th? Best regards Miguel On Wed, Dec 22, 2021 at 8:09 PM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: Hi Miguel, I am glad to hear this news. How about our discussion on January 7th, this Friday is not convenient, what do I need to prepare before the discussion, do I need to submit rfe or other descriptions? 发件人: Miguel Lavalle [mailto: <mailto:miguel@mlavalle.com> miguel(a)mlavalle.com] 发送时间: 2021年12月23日 0:20 收件人: Dazhong Qin (秦海中)-云数据中心集团 < <mailto:qinhaizhong01@inspur.com> qinhaizhong01(a)inspur.com> 抄送: <mailto:openstack-discuss@lists.openstack.org> openstack-discuss(a)lists.openstack.org 主题: Re: Can neutron-fwaas project be revived? Hi Qin, I think that in principle the community will be delighted if you and your team can reactivate the project and maintain it. Probably the best next step is for you to attend the next Neutron drivers meeting (https://wiki.openstack.org/wiki/Meetings/NeutronDrivers) so we can discuss the specifics of your proposal. This meeting takes place on Fridays at 1400 UTC over IRC in oftc.net <http://oftc.net> , channel #openstack-neutron. Due to the end of year festivities in much of Europe and America, the next meeting will take place until January 7th. Is that a good next step for you? If yes, I'll add this topic to the meeting's agenda. Best regards On Tue, Dec 21, 2021 at 10:29 AM Dazhong Qin (秦海中)-云数据中心集团 <qinhaizhong01(a)inspur.com <mailto:qinhaizhong01@inspur.com> > wrote: 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 ?

5 9

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

28 Jan '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week 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/2022/tc.2022-01-27-15.00.log.html * Next week's meeting is on 3rd Feb Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 2nd Feb. 2. What we completed this week: ========================= * "FIPS compatibility and compliance" community-wide goal proposal is merged[2] * Renamed Skyline repo to openstack/ namespace[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. 2 out of 9 items are completed. Open Reviews ----------------- * 3 open reviews for ongoing activities[5]. Renaming all `master` branches on all repos to `main` --------------------------------------------------------------- lourot brought this topic and we discussed if we want to do that. Key point here is how much effort it will take to do for all the existing repo in term of make it working in CI/integration testing tooling/other scripts or not. And we should do it for new repo only. All these are unknown as of now. As first step, lourot will try the project-config importing of dummy project with 'main' branch from GitHub. Based on that, we will discuss it further. Z release cycle name ------------------------- Name nomination is closed, election for proposed names are in-progress. Follow the ML thread for updates[6]. Z release cycle Technical Election --------------------------------------- Election schedule is under review [7], please review and add your feedback. Remove the tags framework --------------------------------- yoctozepto has proposed the WIP patch to remove the tag framework, feel free to review and provide early feedback[8]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[9] and Rico will inform you about the next meeting details. TC position on release cadence ------------------------------------- Dan started the skip level upgrade in grenade and made its working for stable/wallaby to master[10]. TC is planning to meet and discuss the release cadence on 3rd Feb 16 UTC. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [12] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[13]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [14] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://governance.openstack.org/tc/goals/proposed/fips.html [3] https://review.opendev.org/c/openstack/governance/+/826243 [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/2022-January/026810.… [7] https://review.opendev.org/c/openstack/election/+/825017 [8] https://review.opendev.org/c/openstack/governance/+/822900 [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [10] https://review.opendev.org/c/openstack/grenade/+/826101 [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] https://review.opendev.org/c/openstack/governance/+/798540 [13] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [14] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Secure Boot VM issues (libvirt / SMM) | Secure boot requires SMM feature enabled
by Imran Hussain 28 Jan '22

28 Jan '22

Hi, Deployed Wallaby on Ubuntu 20.04 nodes. Having issues with libvirt XML being incorrect, I need the smm bit (<smm state='on'/>) and it isn't being added to the XML. Anyone seen this before? Or any ideas? More info below... Error message: : libvirt.libvirtError: unsupported configuration: Secure boot requires SMM feature enabled Versions: libvirt version: 6.0.0, package: 0ubuntu8.15 QEMU emulator version 4.2.1 (Debian 1:4.2-3ubuntu6.18) Nova 23.1.1 (deployed via kolla, so kolla/ubuntu-source-nova-compute:wallaby is the image) ovmf 0~20191122.bd85bf54-2ubuntu3.3 Context: https://specs.openstack.org/openstack/nova-specs/specs/wallaby/implemented/… Image metadata: hw_firmware_type: uefi hw_machine_type: q35 os_secure_boot: required os_hidden: false hw_disk_bus: scsi hw_qemu_guest_agent: yes hw_scsi_model: virtio-scsi hw_video_model: virtio os_require_quiesce: yes os_secure_boot: required os_hidden: false XML snippets taken from nova-compute.log: <sysinfo type="smbios"> <system> <entry name="manufacturer">OpenStack Foundation</entry> <entry name="product">OpenStack Nova</entry> <entry name="version">23.1.1</entry> <entry name="serial">2798e3fe-ffae-4c26-955b-ef150b849561</entry> <entry name="uuid">2798e3fe-ffae-4c26-955b-ef150b849561</entry> <entry name="family">Virtual Machine</entry> </system> </sysinfo> <os> <type machine="q35">hvm</type> <loader type="pflash" readonly="yes" secure="yes">/usr/share/OVMF/OVMF_CODE.ms.fd</loader> <nvram template="/usr/share/OVMF/OVMF_VARS.ms.fd"/> <boot dev="cdrom"/> <smbios mode="sysinfo"/> </os> <features> <acpi/> <apic/> </features> Other info: # cat /usr/share/qemu/firmware/40-edk2-x86_64-secure-enrolled.json { "description": "UEFI firmware for x86_64, with Secure Boot and SMM, SB enabled, MS certs enrolled", "interface-types": [ "uefi" ], "mapping": { "device": "flash", "executable": { "filename": "/usr/share/OVMF/OVMF_CODE.ms.fd", "format": "raw" }, "nvram-template": { "filename": "/usr/share/OVMF/OVMF_VARS.ms.fd", "format": "raw" } }, "targets": [ { "architecture": "x86_64", "machines": [ "pc-q35-*" ] } ], "features": [ "acpi-s3", "amd-sev", "enrolled-keys", "requires-smm", "secure-boot", "verbose-dynamic" ], "tags": [ ] }

2 3

[release] Release countdown for week R-8, Jan 31 - Feb 04
by Előd Illés 28 Jan '22

28 Jan '22

General Information ------------------- The following cycle-with-intermediary deliverables have not done any intermediary release yet during this cycle. The cycle-with-rc release model is more suited for deliverables that plan to be released only once per cycle. As a result, we have proposed[1] to change the release model for the following deliverables: ovn-octavia-provider ironic-prometheus-exporter ironic-python-agent-builder ironic-ui networking-baremetal networking-generic-switch patrole swift [1] https://review.opendev.org/q/topic:not-yet-released-yoga PTLs and release liaisons for each of those deliverables can either +1 the release model change, or propose an intermediary release for that deliverable. In absence of answer by the end of R-8week we'll consider that the switch to cycle-with-rc is preferable. We also published a proposed release schedule for the upcoming Zcycle. Please check out the separate thread: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026696.… Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 17th, 2022(R-6 week) Client library freeze: February 24th, 2022(R-5 week) Yoga-3 milestone: February 24th, 2022(R-5 week) Yoga final release: March 30th, 2022 Next PTG: April 4 - 8, 2022 (virtual) Előd Illés irc: elodilles

1 0

[sdk][devstack] openstacksdk-functional-devstack job failing on stable branches
by Brian Rosmaita 28 Jan '22

28 Jan '22

openstacksdk-functional-devstack began failing in the stable branches (xena through ussuri) shortly after 2022-01-24 11:53:49 with the error openstack.exceptions.ResourceNotFound: ResourceNotFound: 404: Client Error for url: https://{ip_address}:9696/v2.0/qos/policies/69e472c0-37d2-46e0-9b9e-727c962c5511/minimum_packet_rate_rules, The resource could not be found. for these four tests: openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_find openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_get openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_list openstack.tests.functional.network.v2.test_qos_minimum_packet_rate_rule.TestQoSMinimumPacketRateRule.test_update job build history: https://zuul.opendev.org/t/openstack/builds?job_name=openstacksdk-functiona… It's passing in master and stable/{train,stein,rocky}. Anyone know what's up?

6 6

[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

[cyborg] cancel weekly meeting in on February 4, 2022
by Brin Zhang(张百林) 27 Jan '22

27 Jan '22

Hi all, February 1~ February 6, 2022 are the Spring Festival of China, so we will cancel next weekly meeting, if you have some questions you can ping us by email. best regard brinzhang

1 0

[neutron] Drivers meeting agenda - 28.01.2022
by Lajos Katona 27 Jan '22

27 Jan '22

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. There is no RFE proposed this week, but I would like to discuss again how to handle neutron-fwaas. To simplify things TC asked to keep neutron-fwaas under openstack/ namespace, see the discussion on #openstack-tc: https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2022-0… [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 0

[rbac][keystone][kolla][osa][tripleo][charms] RBAC in Yoga for deployment projects
by Mark Goddard 27 Jan '22

27 Jan '22

Hi, If you haven't been paying close attention, it would be easy to miss some of the upcoming RBAC changes which will have an impact on deployment projects. I thought I'd start a thread so that we can share how we are approaching this, get answers to open questions, and ideally all end up with a fairly consistent approach. The secure RBAC work has a long history, and continues to evolve. According to [1], we should start to see some fairly substantial changes over the next few releases. That spec is fairly long, but worth a read. In the yoga timeline [2], there is one change in particular that has an impact on deployment projects, "3. Keystone enforces scope by default". After this change, all of the deprecated policies that many still rely on in Keystone will be removed. In kolla-ansible, we have an etherpad [5] with some notes, questions and half-baked plans. We made some changes in Xena [3] to use system scope in some places when interacting with system APIs in Ansible tasks. The next change we have staged is to add the service role to all service users [4], in preparation for [2]. Question: should the role be added with system scope or in the existing service project? The obvious main use for this is token validation, which seems to allow system or project scope. We anticipate that some service users may still require some project-scoped roles, e.g. when creating resources for octavia. We'll deal with those on a case by case basis. In anticipation of keystone setting enforce_scope=True and removing old default policies (which I assume effectively removes enforce_new_defaults?), we will set this in kolla-ansible, and try to deal with any fallout. Hopefully the previous work will make this minimal. How does that line up with other projects' approaches? What have we missed? Mark [1] https://opendev.org/openstack/governance/src/branch/master/goals/selected/c… [2] https://opendev.org/openstack/governance/src/branch/master/goals/selected/c… [3] https://opendev.org/openstack/kolla-ansible/commit/2e933dceb591c3505f35c2c1… [4] https://review.opendev.org/c/openstack/kolla-ansible/+/815577 [5] https://etherpad.opendev.org/p/enabling-system-scope-in-kolla-ansible

6 23

[manila][cinder][glance][nova] Pop-up team for design and development of a Cephadm DevStack plugin
by Victoria Martínez de la Cruz 27 Jan '22

27 Jan '22

Hi all, I'm reaching out to you to let you know that we will start the design and development of a Cephadm DevStack plugin. Some of the reasons on why we want to take this approach: - devstack-plugin-ceph worked for us for a lot of years, but the development of it relies on several hacks to adapt to the different Ceph versions we use and the different distros we support. This led to a monolithic script that sometimes is hard to debug and break our development environments and our CI - cephadm is the deployment tool developed and maintained by the Ceph community, it allows their users to get specific Ceph versions very easily and enforces good practices for Ceph clusters. From their docs, "Cephadm manages the full lifecycle of a Ceph cluster. It starts by bootstrapping a tiny Ceph cluster on a single node (one monitor and one manager) and then uses the orchestration interface (“day 2” commands) to expand the cluster to include all hosts and to provision all Ceph daemons and services. [0]" - OpenStack deployment tools are starting to use cephadm as their way to deploy Ceph, so it would be nice to include cephadm in our development process to be closer with what is being done in the field I started the development of this in [1], but it might be better to change devstack-plugin-ceph to do this instead of having a new plugin. This is something I would love to discuss in a first meeting. Having said this, I propose using the channel #openstack-cephadm in the OFTC network to talk about this and set up a first meeting with people interested in contributing to this effort. Thanks, Victoria [0] https://docs.ceph.com/en/pacific/cephadm/ [1] https://github.com/vkmc/devstack-plugin-cephadm

5 6

[TripleO] gate blocker centos-9 please hold rechecks
by Marios Andreou 27 Jan '22

27 Jan '22

o/ Hi folks please hold rechecks especially if you see failing centos9 jobs (should be all of master tripleo repos now) we have a gate blocker there https://bugs.launchpad.net/tripleo/+bug/1959181 thank you, marios (on behalf of tripleo-ci team - #oooq and #tripleo channels)

1 1

Neutron issue || Remote error: TimeoutError QueuePool limit of size 5 overflow 50 reached
by Md. Hejbul Tawhid MUNNA 27 Jan '22

27 Jan '22

Hi, Suddenly we have observed few VM down . then we have found some agent are getting down (XXX) , agents are getting UP and down randomly. Please check the attachment. //////////////////////////////////////////////////////////////////////////////////////////////////// /sqlalchemy/pool.py", line 788, in _checkout\n fairy = _ConnectionRecord.checkout(pool)\n', u' File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 532, in checkout\n rec = pool._do_get()\n', u' File "/usr/lib64/python2.7/site-packages/sqlalchemy/pool.py", line 1186, in _do_get\n (self.size(), self.overflow(), self._timeout), code="3o7r")\n', u'TimeoutError: QueuePool limit of size 5 overflow 50 reached, connection timed out, timeout 30 (Background on this error at: http://sqlalche.me/e/3o7r)\n']. 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent Traceback (most recent call last): 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/neutron/agent/l3/agent.py", line 837, in _report_state 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent True) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/neutron/agent/rpc.py", line 97, in report_state 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent return method(context, 'report_state', **kwargs) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 179, in call 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent retry=self.retry) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 133, in _send 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent retry=retry) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 645, in send 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent call_monitor_timeout, retry=retry) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 636, in _send 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent raise result 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent RemoteError: Remote error: TimeoutError QueuePool limit of size 5 overflow 50 reached, connection timed out, timeout 30 (Background on this error at: http://sqlalche.me/e/3o7r) 2022-01-24 01:05:39.592 302841 ERROR neutron.agent.l3.agent [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 163, in _process_incoming\n res = self.dispatcher.dispatch(message)\n', u' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 265, in dispatch\n return self._do_dispatch(endpoint, method, ctxt, args)\n', u' File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch\n ///////////////////////////////////////////////////////////////////////////////// Is there anything related with the following default configuration. /etc/neutron/neutron.conf #max_pool_size = 5 #max_overflow = 50 regards, Munna

4 7

[all][tc] Technical Committee next weekly meeting on Jan 27th at 1500 UTC
by Ghanshyam Mann 26 Jan '22

26 Jan '22

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

1 1

[cinder] Bug deputy report for week of 01-26-2022
by Sofia Enriquez 26 Jan '22

26 Jan '22

This is a bug report from 01-19-2022 to 01-26-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- The cinder bug meeting will return on Feb 16th. If you have an urgent bug, please bring it to the main cinder meeting! Medium - https://bugs.launchpad.net/cinderlib/+bug/1958159 "stable/ussuri: cinderlib-lvm-functional job is failing." Fix proposed to stable/ussuri and master. Assigned to Takashi Kajinami. - https://bugs.launchpad.net/cinder/+bug/1958632 "SVC storwize regression after fixing 1913363." Unassigned. Incompleted - https://bugs.launchpad.net/cinder/+bug/1958845 "Rbd: possibility of data loss during revert-to-snap." Fix proposed to master. 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

[swift] Dropping support for py27
by Timothy Burke 26 Jan '22

26 Jan '22

The Swift team plans for the coming Yoga release to be the final Swift release to support Python 2.7. This is long overdue; it is now two years since the official Python 2.7 end-of-life. We were relatively late in adding Python 3 support, however, and wanted to ensure a long-enough period to root out Python 3 bugs and transition existing Python 2 clusters. We've used that time effectively; now it's time to move forward. We'll do what we can to ensure subsequent releases are *not* considered for installation on unsupported versions of Python. Notably, we'll ensure wheels are no longer flagged as universal, and `python_requires` will be set. If you have a continued interest in running latest Swift on Python 2.7, please get in touch with us, either here on the mailing list or in #openstack-swift on OFTC. Tim Burke Swift PTL

1 0

[cinder] Bug deputy report for week of 01-19-2022
by Sofia Enriquez 26 Jan '22

26 Jan '22

This is a bug report from 01-12-2022 to 01-19-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- Medium - https://bugs.launchpad.net/cinder/+bug/1957804 "RBD deferred deletion causes undeletable RBD snapshots." In Progress. Assigned to Eric. - https://bugs.launchpad.net/cinder/+bug/1958122 "HPE 3PAR: In multi host env, multi-detach works partially if volume is attached to instances from separate hosts." In Progress. Assigned to Raghavendra Tilay. Low - https://bugs.launchpad.net/cinder/+bug/1958023 "Solidfire: there are some references to the removed parameters left." In Progress. Assigned to kajinamit. - https://bugs.launchpad.net/cinder/+bug/1958245 "NetApp ONTAP driver shows type error exception when replicating FlexGroups." 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>

2 2

[heat][interop] StackBuildErrorException on a master job
by Martin Kopec 26 Jan '22

26 Jan '22

Hi there, our interop master job (jobs for older OpenStack releases are fine) is constantly failing on 2 heat tests: heat_tempest_plugin.tests.functional.test_software_config.ParallelDeploymentsTest.test_deployments_metadata heat_tempest_plugin.tests.functional.test_software_config.ParallelDeploymentsTest.test_deployments_timeout_failed Full log at: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/… Patch where you can see all the jobs - master one failing and the rest passing: https://review.opendev.org/c/openinfra/refstack-client/+/819918 We can't figure out what's going on there. Maybe additional configuration of the deployment is required? New requirements? Any ideas what the job is missing? Thank you, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

2 3

2021 OpenInfra Foundation Annual Report Now Available
by Kendall Nelson 26 Jan '22

26 Jan '22

Hello Everyone! The 2021 OpenInfra Annual Report is live! It includes sections on all OpenInfra projects, Foundation updates, open infrastructure growth, SIG and WG updates, and more. You can find the 2021 OpenInfra Annual Report here: https://openinfra.dev/annual-report/2021 Thanks! Kendall (diablo_rojo)

1 0

[release][infra] SSH host key issue - RedFlag stop approving
by Előd Illés 26 Jan '22

26 Jan '22

Hi, tag-release jobs started to fail today and what i see is mostly that ECDSA host key for IP address X not in list of known hosts [1][2][3] Please don't approve release patches until we haven't figure out what is the problem. [1] https://zuul.opendev.org/t/openstack/build/a490703c83514eb7ba9d0ff6307f7371… [2] https://zuul.opendev.org/t/openstack/build/00d3f765ea6847a3bf7ea53294cf2a88… [3] https://zuul.opendev.org/t/openstack/build/d8aaeff52dac442e89fd3e253596e0c2… Thanks, Előd irc:elodilles @ #openstack-release

2 4

[monasca] [Release-job-failures] Release of openstack/monasca-agent for ref refs/tags/4.0.1 failed
by Előd Illés 26 Jan '22

26 Jan '22

Hi Monasca team, The forwarded mail contains a release job failure, specifically the publish-monasca-agent-docker-images job failed [1] with a missing package during docker image build. Can you please have a look at the issue? [1] https://zuul.opendev.org/t/openstack/build/2ebcbfec634c4c068e9f7625473ea726 Thanks in advance, Előd irc:elodilles @ #openstack-release -------- Forwarded Message -------- Subject: [Release-job-failures] Release of openstack/monasca-agent for ref refs/tags/4.0.1 failed Date: Wed, 26 Jan 2022 11:57:09 +0000 From: zuul(a)openstack.org Reply-To: openstack-discuss(a)lists.openstack.org To: release-job-failures(a)lists.openstack.org Build failed. - openstack-upload-github-mirror https://zuul.opendev.org/t/openstack/build/bba91d0025a2496087a29803451a314f : SUCCESS in 45s - release-openstack-python https://zuul.opendev.org/t/openstack/build/a749eb25de1d426e845740cae1876afe : SUCCESS in 3m 50s - announce-release https://zuul.opendev.org/t/openstack/build/551dd5bd118347908b7113a5e2fa5c5e : SUCCESS in 5m 37s - propose-update-constraints https://zuul.opendev.org/t/openstack/build/e95a5bee9817491d84c89f89758872d6 : SUCCESS in 4m 18s - publish-monasca-agent-docker-images https://zuul.opendev.org/t/openstack/build/2ebcbfec634c4c068e9f7625473ea726 : POST_FAILURE in 7m 08s _______________________________________________ Release-job-failures mailing list Release-job-failures(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures

2 1

Z Release Naming ...
by Jay Bryant 26 Jan '22

26 Jan '22

All, As in the past, I would like the community's input on the 'Z' release name [1] . I have narrowed the list down to my top 4 choices. Please take a few minutes to vote. The poll closes around 14:30 UTC on 1/28/22. Thanks for your input! Jay (jungleboyj) [1] https://twitter.com/jungleboyj/status/1486344910693441541

1 0

[horizon] Cancelling Today's weekly meeting
by vishal manchanda 26 Jan '22

26 Jan '22

Hello Team, Since there are no agenda items [1] to discuss for today's horizon weekly meeting. Also, Today is a holiday for me. So let's cancel today's weekly meeting. The next weekly meeting will be on 2nd February. Thanks & Regards, Vishal Manchanda [1] https://etherpad.opendev.org/p/horizon-release-priorities

1 0

[TripleO] Proposing Juan Badia Payno for TripleO core reviewer.
by Carlos Camacho Gonzalez 26 Jan '22

26 Jan '22

Hi everyone! I'd like to propose Juan Badia Paino [1][2][3] as a core reviewer on the TripleO repositories that are or might be related to the backup and restore efforts (openstack/tripleo-ci, openstack/tripleo-ansible, openstack/python-tripleoclient, openstack/tripleo-quickstart-extras, openstack/tripleo-quickstart). Juan has been around since 2016 making useful contributions and code reviews to the community and I believe adding him to our core reviewer group will help us improve the review and coding speed for the backup and restore codebase. As usual, consider this email as an initial +1 from my side, I will keep an eye on this thread for a week, and based on your feedback and if there are no objections I will add him as a core reviewer in two weeks. [1]: https://review.opendev.org/q/owner:jbadiapa%2540redhat.com [2]: https://www.stackalytics.io/?project_type=all&metric=commits&user_id=jbadia… [3]: https://www.stackalytics.io/report/contribution?module=tripleo-group&projec… Cheers, Carlos.

9 9

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

Compute Node Not Getting PXE boot During Scale-In/Out Activity
by Pradeep Antil 25 Jan '22

25 Jan '22

Hello Folks, Hope you are doing well ! I have a compute node (SRIOV) in my RedHat Openstack 13 Lab. I have a task to remove the sriov compute and add it back as a dpdk compute node. After removing this node as scale-in activity via overcloud stack when I tried to add it again, introspection for this node is failing. After looking into the logs in undercloud , it appears like it is not getting the ip address from pxe. # cat /var/log/messages|grep -i "0c:42:a1:45:03:10" --color [image: image.png] [root@director ~]# tcpdump -n -i br-ctlplane -e | grep -i "0c:42:a1:45:03:10" --color tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on br-ctlplane, link-type EN10MB (Ethernet), capture size 262144 bytes 23:54:08.653057 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 394 23:54:12.669877 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 394 23:54:20.744605 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 394 23:54:36.839226 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 436: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 394 23:56:48.967623 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 23:56:49.044752 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 23:56:49.269645 0c:42:a1:45:03:10 > 33:33:ff:45:03:10, ethertype IPv6 (0x86dd), length 86: :: > ff02::1:ff45:310: ICMP6, neighbor solicitation, who has fe80::e42:a1ff:fe45:310, length 32 23:56:49.781577 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 23:56:50.271663 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: fe80::e42:a1ff:fe45:310 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 23:56:50.271922 0c:42:a1:45:03:10 > 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::e42:a1ff:fe45:310 > ff02::2: ICMP6, router solicitation, length 16 23:56:50.368576 0c:42:a1:45:03:10 > 33:33:00:00:00:16, ethertype IPv6 (0x86dd), length 90: fe80::e42:a1ff:fe45:310 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 23:56:54.274049 0c:42:a1:45:03:10 > 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::e42:a1ff:fe45:310 > ff02::2: ICMP6, router solicitation, length 16 23:56:54.675024 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 23:56:58.282332 0c:42:a1:45:03:10 > 33:33:00:00:00:02, ethertype IPv6 (0x86dd), length 70: fe80::e42:a1ff:fe45:310 > ff02::2: ICMP6, router solicitation, length 16 23:57:07.638252 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 23:57:10.053205 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 23:57:18.720085 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 23:57:32.817306 0c:42:a1:45:03:10 > Broadcast, ethertype IPv4 (0x0800), length 342: 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 0c:42:a1:45:03:10, length 300 Physical connectivity of this node is intact. Any idea and suggestions ? how this issue can be fixed. -- Best Regards Pradeep Kumar

1 0

[neutron] Bug Deputy Report Jan 17 - 23
by Oleg Bondarev 25 Jan '22

25 Jan '22

Hi everyone, Please find Bug Deputy report for the week Jan 17 - 23rd below. 1 Critical bug (with a related logs-improving patch from Slawek) looks for volunteers. A couple of Medium bugs: an l3-bgp bug to be verified by bgp team - 1958627, and an ipv6+ovs firewall bug - 1958643. Also several OVN bug needs some triage from OVN folks + assignees. Details: Critical -------- - https://bugs.launchpad.net/neutron/+bug/1958363 - Notifications to nova disabled causing tests failures - Confirmed - Related patch: https://review.opendev.org/c/openstack/neutron/+/825513 - Unassigned! Medium ---------- - https://bugs.launchpad.net/neutron/+bug/1958627 - Incomplete ARP entries on L3 gw namespace - Opinion - Unassigned! - https://bugs.launchpad.net/neutron/+bug/1958149 - ha backup router ipv6 accept_ra broken - In progress: https://review.opendev.org/c/openstack/neutron/+/824947 - Assigned to Maximilian Stinsky - https://bugs.launchpad.net/neutron/+bug/1958364 - [ovn]Set NB/SB connection inactivity_probe does not work for cluster - In progress: https://review.opendev.org/c/openstack/neutron/+/825269 - Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/1958225 - [ovn]chassis available zone changed, not reschedule router gateway_chassis - In progress: https://review.opendev.org/c/openstack/neutron/+/825073 - Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/1958353 - [ovn]Gateway port is down after gateway chassis changed - In progress: https://review.opendev.org/c/openstack/neutron/+/825041 - Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/1958501 - [ovn]Refusing to bind port to dead agent - In progress: https://review.opendev.org/c/openstack/neutron/+/825428 - Assigned to ZhouHeng - https://bugs.launchpad.net/neutron/+bug/1958643 - Unicast RA messages for a VM are filtered out by ovs rules - Confirmed - Unassigned! Low ----- - https://bugs.launchpad.net/neutron/+bug/1958513 - [test]The unit test file ovn_l3.test_plugin cannot be run alone - In progress: https://review.opendev.org/c/openstack/neutron/+/825478 - Assigned to ZhouHeng Undecided ------------- - https://bugs.launchpad.net/neutron/+bug/1958355 - Undecided - Unassigned! - https://bugs.launchpad.net/neutron/+bug/1958561 - [ovn-octavia-provider] Listner/Pool Stuck in PENDING_CREATE Using Fully Populated LB API - Undecided - Unassigned! - https://bugs.launchpad.net/neutron/+bug/1958593 - [ovn]neutron-server allow more efficient reconnections when connecting to clustered OVSDB servers - Undecided - Unassigned! Invalid -------- - https://bugs.launchpad.net/neutron/+bug/1958128 - Neutron l3 agent keeps restarting (Ubuntu) Expired --------- - https://bugs.launchpad.net/neutron/+bug/1939680 - Neutron - set "dns_domain" for existing network is passively failing when Designate DNS extension is not enabled for Neutron - Undecided - Unassigned Thanks, Oleg --- Advanced Software Technology Lab Huawei

1 0

[Oslo] First IRC meeting of the year.
by Daniel Mats Niklas Bengtsson 25 Jan '22

25 Jan '22

Hi there, Yesterday we had the first oslo IRC meeting. You can find the log[1] on the meeting. Sorry I forget the ping and I confused the hour, but I will do better job next time. [1] https://meetings.opendev.org/meetings/oslo/2022/

1 0

Openstack+Magnum for edge
by Vikarna Tathe 24 Jan '22

24 Jan '22

Hello All, Is there a solution available for OpenStack controllers at a central location and computes at the edge (far from central)? If not what's the alternative? Any help would be appreciated. Thanks, Vikarna

1 0

[openstack-helm] No meeting tomorrow
by Gage Hugo 24 Jan '22

24 Jan '22

Hey team, Since there's nothing on the agenda for tomorrow's meeting, it has been cancelled. We will meet again next week.

1 0

答复: [cyborg] Proposing core reviewers
by Brin Zhang(张百林) 24 Jan '22

24 Jan '22

> ��: Brin Zhang(�Ű��) > ��ʱ��: 2022��1��17�� 9:13 > �ռ��: 'openstack-discuss(a)lists.openstack.org' <openstack-discuss(a)lists.openstack.org> > ��: 'xin-ran.wang(a)intel.com' <xin-ran.wang(a)intel.com>; Alex Song (��ƽ) <songwenping(a)inspur.com>; 'huangzhipeng(a)huawei.com' <huangzhipeng(a)huawei.com>; 'liliueecg(a)gmail.com' <liliueecg(a)gmail.com>; 'shogo.saito.ac(a)hco.ntt.co.jp' <shogo.saito.ac(a)hco.ntt.co.jp>; 'sundar.nadathur(a)intel.com' <sundar.nadathur(a)intel.com>; 'yumeng_bao(a)yahoo.com' <yumeng_bao(a)yahoo.com>; 'chen.ke14(a)zte.com.cn' <chen.ke14(a)zte.com.cn>; '419546439(a)qq.com' <419546439(a)qq.com>; 'shaohe.feng(a)intel.com' <shaohe.feng(a)intel.com>; 'wangzhengh(a)chinatelecom.cn' <wangzhengh(a)chinatelecom.cn>; 'zhuli2317(a)gmail.com' <zhuli2317(a)gmail.com> >��: [cyborg] Proposing core reviewers > Hello all, > Eric xie has been actively contributing to Cyborg in various areas, adding new features, improving quality, reviewing patches. Despite the relatively short time, he has been one of the most prolific contributors, > and brings an enthusiastic and active mindset. I would like to thank and acknowledge him for his steady valuable contributions, and propose him as a core reviewer for Cyborg. fwiw, saw no negative votes, so added Eric to cyborg-core group. Welcome Eric on board and thanks for helping the community ! > Some of the currently listed core reviewers have not been participating for a lengthy period of time. It is proposed that those who have had no contributions for the past 18 months > �C i.e. no participation in meetings, no code contributions, not participating in Cyborg open source activities and no reviews �C be removed from the list of core reviewers. > -- The Cyborg team recognizes everyone's contributions, but we need to ensure the activity of the core-reviewer list. If you are interested in rejoining the cyborg team, feel free to ping us to restore the core reviewer for you. > If no objections are made known by January 24, I will make the changes proposed above.. > Regards, > Brin Zhang

1 0

[PTG] April 2022 Virtual PTG Dates & Registration
by Kendall Nelson 24 Jan '22

24 Jan '22

Hello Everyone! We're happy to announce the next virtual PTG[1] will take place April 4-8, 2022! Registration is now open[2]. The virtual PTG is free to attend, but make sure to register so you receive important communications like schedules, passwords, and other relevant updates. Next week, keep an eye out for info regarding team sign-ups. Can't wait to see you all there! -Kendall (diablo_rojo) [1] https://www.openstack.org/ptg/ [2] https://openinfra-ptg.eventbrite.com/

1 0

[sdk] R1 branch merged into master
by Artem Goncharov 24 Jan '22

24 Jan '22

Hi everybody, Just wanted to give a hint that feature/r1 branch of the OpenStackSDK is now merged into the master. While most of the challenging things are now completed the work is not finished yet, but will soon be. Most important: most of the work is backward compatible, but few things were not. I took care on keeping things working and testing, but there might be side effects that I have not expected. Please let me know if jobs in your projects start failing. Regards, Artem

2 2

[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

[TripleO] Horizon login failed with Something went wrong error in IPv6
by Anirudh Gupta 23 Jan '22

23 Jan '22

Hi Team, We are trying to deploy the Tripleo Train with IPv6. All the overcloud control plane networks - internal, management etc are also on the IPv6 subnet. Upon successful completion of overcloud, when I am trying to open the page, it does open. But when I enter the correct login credentials, it says something went wrong. [image: image.png] Upon looking into error logs, I found 2022-01-21 12:33:34.825 324 WARNING keystone.server.flask.application [req-0660e62c-dff7-4609-89fe-225e177a84f8 f908417368a24cc685818bb5fc54fe12 - - default -] *Authorization failed. The request you have made requires authentication. from fd00:fd00:fd00:2000::359: keystone.exception.Unauthorized: The request you have made requires authentication.* where *fd00:fd00:fd00:2000::359 is my internal IP address which is reachable.* Regards Anirudh Gupta

3 2

[xena][nova] Libvirt Live Migration Lock
by Ammad Syed 23 Jan '22

23 Jan '22

Hi, I have a weird error while performing live migration of trove instances. The instance has a root disk residing on a local compute node and a second a second disk is attached from shared storage via cinder. There are two networks attached with the instance, one is vlan backed and other one is geneve. When I try to perform its live migration, it fails. I see below errors in libvirt logs and the same in nova-compute logs. Jan 19 15:56:54 host03.cloud.com libvirtd[731030]: Cannot start job (query, none, none) for domain instance-00000819; current job is (none, none, migration in) owned by (0 <null>, 0 <null>, 0 remoteDispatchDomainMigratePrepare3Params (flags=0x9b)) for (0s, 0s, 61s) Jan 19 15:56:54 host03.cloud.com libvirtd[731030]: Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainMigratePrepare3Params) Jan 19 15:36:30 host03.cloud.com libvirtd[731030]: migration successfully aborted Any advise how to fix it ? I am using below libvirt version. libvirt 6.0 qemu-kvm 4.2 kernel 5.4 nova 24.0 Ammad

1 1

[neutron] Welcome Oleg Bondarev in the drivers team
by Lajos Katona 23 Jan '22

23 Jan '22

Hi, Oleg is one of the most active and experienced developers around Neutron, and long served to be a member of the Drivers team (see: [0]). We all agreed that Oleg deserves to be part of the team and he will be a great member (see [1]), so I just added him to the neutron-drivers group. Welcome to the team Oleg! [0]: https://review.opendev.org/admin/groups/5b063c96511f090638652067cf0939da1cb… [1]: http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026690.… Lajos Katona (lajoskatona)

3 2

[all][tc] What's happening in Technical Committee: summary 21st Jan, 21: Reading: 5 min
by Ghanshyam Mann 21 Jan '22

21 Jan '22

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week 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/2022/tc.2022-01-20-15.00.log.html * Next week's meeting is on 27th Jan Thursday 15:00 UTC, feel free add the topic on the agenda[1] by 26th Jan. 2. What we completed this week: ========================= * [masakari] Transfer PTL role to suzhengwei[2] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[3]. 2 out of 9 items are completed. Open Reviews ----------------- * 4 open reviews for ongoing activities[4]. Z release cycle name ------------------------- Z release cycle naming process schedule is merged[5]. Follow the ML thread for updates[6]. Z release cycle Technical Election --------------------------------------- Its time for Z release Technical Election, I have proposed the election dates (combined PTL + TC) [7], please review and add your feedback. Remove the tags framework --------------------------------- yoctozepto has proposed the WIP patch to remove the tag framework, feel free to review and provide early feedback[8]. OpenStack Pain points discussion ---------------------------------------- No updates in this week. Stay tuned on the ML thread[9] 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[10]. No other updates from TC on this and we will set up a separate call to continue the discussion. Fixing Zuul config error ---------------------------- Requesting projects with zuul config error to look into those and fix them which should not take much time[11]. Adjutant need maintainers and PTLs ------------------------------------------- We are still waiting to hear from Braden, Albert on permission to work on this project[12], we discussed it in this week TC meeting and there is blocker for Yoga release. We will leave this item from monitoring now and check the situation at the time of Z release election. I hope till that time, we will have more maintainer/leaders to lead this project. Project updates ------------------- * Retire js-openstack-lib (waiting on Adjutant to have new PTL/maintainer) [13] 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[14]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [15] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. Welcome back from the holidays and stay safe! [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/824509 [3] https://etherpad.opendev.org/p/tc-yoga-tracker [4] https://review.opendev.org/q/projects:openstack/governance+status:open [5] https://review.opendev.org/c/openstack/governance/+/824201 [6] http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026810.… [7] https://review.opendev.org/c/openstack/election/+/825017 [8] https://review.opendev.org/c/openstack/governance/+/822900 [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026245… [10] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [11] https://etherpad.opendev.org/p/zuul-config-error-openstack [12] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [13] https://review.opendev.org/c/openstack/governance/+/798540 [14] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [15] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all] Nomination open for OpenStack "Z" Release Naming
by Ghanshyam Mann 21 Jan '22

21 Jan '22

Hello Everyone, We are now starting the process for the OpenStack 'Z' release name. We are a little late to start it, sorry for that. I have proposed to close the nomination on 24th Jan[1]. I am hoping that is enough time to collect the names, If not please reply to this thread or in gerrit review[1]. Once the governance patch is merged I will update the final dates of nomination close and polls here, meanwhile in parallel please start proposing the name on the wiki page. Criteria: ====== - Refer to the below governance page for the naming criteria: https://governance.openstack.org/tc/reference/release-naming.html#release-n… - Any community members can propose the name to the below wiki page: https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals We encourage all community members to participate in this process. [1] https://review.opendev.org/c/openstack/governance/+/824201 -gmann

1 2

Bug Fix - openstack-archive/syntribos
by Abdullah Zaman Babar 21 Jan '22

21 Jan '22

Dear Sir/Madam, I hope this email finds you well. Recently I was working with syntribos and I found a bug in the code which I wanted to report but the repository is archived and I'm unable to generate a pull request. Could you please guide me to contribute to the repository? It will be my first ever contribution to open-source. Regards Abdullah Zaman Babar

3 2

[gate][nova][qa] tempest-*-centos-8-stream job failing consistently since yesterday
by Ghanshyam Mann 21 Jan '22

21 Jan '22

Hello Everyone, You might have noticed that 'tempest-integrated-compute-centos-8-stream' and 'tempest tempest-full-py3-centos-8-stream' job started failing the below two tests consistently since yesterday (~7 PM CST) - https://169dddc67bd535a0361f-0632fd6194b48b475d9eb0d8f7720c6c.ssl.cf2.rackc… I have filed the bug and to unblock the gate (nova & tempest), I have pushed patch to make these job non voting until bug is fixed. - https://review.opendev.org/c/openstack/tempest/+/824740 Please hold the recheck on nova or tempest (or any other effected project). ralonsoh mentioned that this is not the same issue which is raised in - http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026682.… or may be triggered due to same root cause? -gmann

4 6

[magnum][tc] Proposing Jake Yip for core-reviewer
by Spyros Trigazis 21 Jan '22

21 Jan '22

Dear all, I would like to nominate Jake Yip for core reviewer in the magnum project. Jake has been doing code reviews for the past years in magnum at a steady rate and is running magnum as well in their organization. With very good knowledge of the magnum codebase, I am confident that Jake will help increase the pace of development in the project. Cheers, Spyros

4 3

[outreachy] Stepping down as Outreachy co-organizer
by Samuel de Medeiros Queiroz 21 Jan '22

21 Jan '22

Hi all, Outreachy is a wonderful program that promotes diversity in open source communities by giving opportunities to people in underrepresented groups. This was a hard decision to make, but I have not been committing the time this project deserves. For that reason, I would like to give visibility that I am stepping down as an Outreachy organizer. It was a great honor to serve as co-organizer since late 2018, and we had 19 internships since then. I also had the pleasure to serve twice (2016 and 2017) as a mentor. Mahati, it was a great pleasure co-organizing Outreachy in this community with you. Thanks! Samuel Queiroz

5 4

[Infra]CentOS Stream 8 based jobs are hitting RETRY or RETRY_LIMIT
by Chandan Kumar 20 Jan '22

20 Jan '22

Hello, Currently CentOS Stream 8 based jobs are hitting RETRY or RETRY_LIMIT. https://zuul.opendev.org/t/openstack/builds?result=RETRY&result=RETRY_LIMIT… Based on the logs, all are hitting with : ``` rrors during downloading metadata for repository 'appstream': 2022-01-20 09:34:18.119377 | primary | - Status code: 404 for https://mirror-int.iad.rax.opendev.org/centos/8-stream/AppStream/x86_64/os/… (IP: 10.208.224.52) 2022-01-20 09:34:18.119443 | primary | - Status code: 404 for https://mirror-int.iad.rax.opendev.org/centos/8-stream/AppStream/x86_64/os/… (IP: 10.208.224.52) ``` While taking a look at https://opendev.org/opendev/system-config/src/branch/master/playbooks/roles… ``` 404 for http://mirror.dal10.us.leaseweb.net/centos/8-stream/AppStream/x86_64/os/re podata/09255ba7c10e01afeb0d343667190f9c3e42d0a6099f887619abcb92ea0378db-filelists.xml.gz (IP: 209.58.153.1) ``` It seems the centos mirror have issues. https://review.opendev.org/c/opendev/system-config/+/825446 make the switch to facebook mirror. It might fix the issue. Thanks Alfredo for debugging it. Thanks, Chandan Kumar

2 3

[all][infra][kayobe][kolla] ping not permitted on latest centos-8-stream images
by Pierre Riteau 20 Jan '22

20 Jan '22

Hello, Late yesterday, I noticed many Kayobe CI jobs started failing with "ping: socket: Operation not permitted". I investigated the issue with clarkb on #openstack-infra, with help from #centos-devel as well (on Libera). This happens on the latest CentOS Stream 8 images and is caused by iputils 20180629-8.el8 removing capabilities on the ping binary [1]. This should have been shipped with a sysctl configuration allowing any group to access unprivileged ICMP echo sockets [2], but this is not in the systemd package yet. As a result, using ping without root privileges fails. TripleO is also impacted. They have fixed it in their CI jobs [3]. It is possible other projects are affected. There are multiple places within Kayobe and Kolla where we would need to set this sysctl to fix our CI, including backports to all supported branches. I was wondering if infra could instead customise their stream image or apply the sysctl in one of the common roles from zuul/zuul-jobs that are run at the beginning of each job? Many thanks. Best wishes, Pierre Riteau (priteau) [1] https://git.centos.org/rpms/iputils/c/efa64b5e05ccb2c1332304ad493acc874b61e… [2] https://github.com/redhat-plumbers/systemd-rhel8/pull/246 [3] https://review.opendev.org/c/openstack/tripleo-ci/+/824635

4 8

[Diversity] Diversity and Inclusion WG new meeting time
by Amy Marrich 20 Jan '22

20 Jan '22

Thank you to those who responded to the Doodle for our meeting time. The day and time selected was Friday at 15:00 UTC so we will move to that in February with our first meeting being on 2/4. As usual, should we need to cancel the first Friday of the month we have the backup date of the third week. Should we end up having to do that too frequently ,as Fridays are popular for holidays and vacations, we'll readdress the meeting time again. Also chosen was to switch to a video platform and we will work on choosing one before the meeting reminder goes out Thanks, Amy (spotz)

1 0

[neutron] Drivers meeting - Friday 21.01.2022 - cancelled
by Lajos Katona 20 Jan '22

20 Jan '22

Hi Neutron Drivers! Due to the lack of agenda, let's cancel tomorrow's drivers meeting. See You on the meeting next week. [0]: https://meetings.opendev.org/meetings/neutron_drivers/2021/neutron_drivers.…

1 0

Tesla V100 32G GPU with openstack
by Satish Patel 20 Jan '22

20 Jan '22

Folk, We have Tesla V100 32G GPU and I’m trying to configure with openstack wallaby. This is first time dealing with GPU so I have couple of question. 1. What is the difference between passthrough vs vGPU? I did google but not very clear yet. 2. If I configure it passthrough then does it only work with single VM ? ( I meant whole GPU will get allocate to single VM correct? 3. Also some document saying Tesla v100 support vGPU but some folks saying you need license. I have no idea where to get that license. What is the deal here? 3. What are the config difference between configure this card with passthrough vs vGPU? Currently I configure it with passthrough based one one article and I am able to spun up with and I can see nvidia card exposed to vm. (I used iommu and vfio based driver) so if this card support vGPU then do I need iommu and vfio or some other driver to make it virtualize ? Sent from my iPhone

4 11

[nova] [placement] Proposing Sean Mooney as nova-core
by Sylvain Bauza 20 Jan '22

20 Jan '22

Hi all, I would like to propose Sean as an addition to the nova-core team (which includes placement merge rights as nova-core is implicitly a subgroup). As we know, he's around for a long time, is already a nova-specs-core and has proven solid experience in reviews. Cores, please vote (-1, 0, +1) before next Wednesday Jan 19th 1600UTC. Cheers, -Sylvain

6 6

Cannot ssh/ping instance
by Celinio Fernandes 20 Jan '22

20 Jan '22

Hi, I am running Ubuntu Server 20.04 LTS on Virtualbox. I installed OpenStack (Xena release) through Devstack. Here is the content of my /opt/stack/devstack/local.conf file : [[local|localrc]] ADMIN_PASSWORD=secret DATABASE_PASSWORD=$ADMIN_PASSWORD RABBIT_PASSWORD=$ADMIN_PASSWORD SERVICE_PASSWORD=$ADMIN_PASSWORD HOST_IP=10.0.2.15 I created an instance through Horizon. The security group contains the 2 rules needed (one to be able to ping and one to be able to ssh the instance). I also allocated and associated a floating IP address. And a ssh key pair. Here is the configuration : openstack server list ---------------------------------+--------------------------+---------+ | ID | Name | Status | Networks | Image | Flavor | ---------------------------------+--------------------------+---------+ | f5f0fdd5-298b-4fa3-9ee9-e6e4288f4327 | InstanceJanvier | ACTIVE | shared=172.24.4.133, 192.168.233.165 | cirros-0.5.2-x86_64-disk | m1.nano | ------------------------------------------------------+ openstack network list : ------------------------------------------------------+ | ID | Name | Subnets | ------------------------------------------------------+ | 96a04799-7fc7-4525-b05c-ad57261aed38 | public | 07ce42db-6f3f-4135-ace7-2fc104ea62a0, 6dba13fc-b10c-48b1-b1b4-e1f1afe25b53 | | c42638dc-fa56-4644-ad34-295fce4811d2 | shared | a4e2d8cc-02b2-42e2-a525-e0eebbb08980 | | ffb8a527-266e-4e96-ad60-f7e9aba8f0c1 | private | 42e36677-cf3c-4df4-88a1-8cf79b9d6060, e507e6dd-132a-4249-96b1-83761562dd73 | ------------------------------------------------------+ openstack router list : +--------------------------------------+----------------+--------+------ | ID | Name | Status | State | Project | +--------------------------------------+----------------+--------+------ | b9a15051-a532-4c93-95ad-53c057720c62 | Virtual_router | ACTIVE | UP | 6556c02dd88f4c45b535c2dbb8ba1a04 | +--------------------------------------+----------------+--------+------ I cannot ping/ssh neither the fixed IP address or the floating IP address : ping -c 3 172.24.4.133 PING 172.24.4.133 (172.24.4.133) 56(84) bytes of data. --- 172.24.4.133 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2035ms ping -c 3 192.168.233.165 PING 192.168.233.165 (192.168.233.165) 56(84) bytes of data. --- 192.168.233.165 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2035ms Maybe that has something to do with the network namespaces configuration on Ubuntu. Does anyone know what could go wrong or what is missing ? Thanks for helping.

2 6

[cinder] review priorities for the next 2 days
by Brian Rosmaita 20 Jan '22

20 Jan '22

Not surprisingly, the review priority for the next 2 days is to review new driver patches. The merge deadline is tomorrow (21 January) at 20:00 UTC. To be more specific: We have 2 new drivers that depend on the following patches that generalize the hitachi driver: - https://review.opendev.org/c/openstack/cinder/+/786873 - https://review.opendev.org/c/openstack/cinder/+/815461 Then there are the 2 drivers that depend on the above; they are small patches and each of their third-party CIs is running: - https://review.opendev.org/c/openstack/cinder/+/815582 - https://review.opendev.org/c/openstack/cinder/+/815614 So those should be fairly quick reviews. The teams have been quick to respond to comments. There is also the Lightbits driver; it has both cinder and os-brick patches: - https://review.opendev.org/c/openstack/cinder/+/821602 - https://review.opendev.org/c/openstack/os-brick/+/821603 Their third-party CI is running and they have been very responsive to reviews. So really, only 3 new drivers to review! Other drivers: - TOYOU NetStor - merged! \o/ - Pure NVMe-RoCE - vendor is now aiming to merge in Z - Dell EMC PowerStore NFS - vendor is now aiming to merge in Z - YADRO Tatlin - initial commit posted today; has not yet passed Zuul. (Look at it if you have spare time, but please prioritize the patches listed above.)

1 0

[nova][libvirt] Secure boot with SMM support
by Imran Hussain 20 Jan '22

20 Jan '22

Hi, I posted yesterday about my issue http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026796.… but having looked in to it I think it's a Nova problem and should be solved by Nova Compute. I've pushed up a quick patch I wrote https://review.opendev.org/c/openstack/nova/+/825496 that's running on my systems. Thoughts? Thanks, Imran

1 0

[charms] Welcome Hemanth Nakkina to the charms core
by Alex Kavanagh 20 Jan '22

20 Jan '22

Hello Just a quick note to let you know that Hemanth has joined the core charms team, so a huge welcome to him! Thanks for joining the team. Hemanth has been a trusted and helpful reviewer and contributor to the charms, and received many +1s and comments on his proposal. All the best Alex. -- Alex Kavanagh - Software Engineer OpenStack Engineering - Data Centre Development - Canonical Ltd

1 0

[cyborg] Proposing core reviewers
by Brin Zhang(张百林) 19 Jan '22

19 Jan '22

Hello all, Eric xie has been actively contributing to Cyborg in various areas, adding new features, improving quality, reviewing patches. Despite the relatively short time, he has been one of the most prolific contributors, and brings an enthusiastic and active mindset. I would like to thank and acknowledge him for his steady valuable contributions, and propose him as a core reviewer for Cyborg. Some of the currently listed core reviewers have not been participating for a lengthy period of time. It is proposed that those who have had no contributions for the past 18 months �C i.e. no participation in meetings, no code contributions, not participating in Cyborg open source activities and no reviews �C be removed from the list of core reviewers. -- The Cyborg team recognizes everyone's contributions, but we need to ensure the activity of the core-reviewer list. If you are interested in rejoining the cyborg team, feel free to ping us to restore the core reviewer for you. If no objections are made known by January 24, I will make the changes proposed above.. Regards, Brin Zhang

4 4

[all][tc] Technical Committee next weekly meeting on Jan 20th at 1500 UTC
by Ghanshyam Mann 19 Jan '22

19 Jan '22

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

1 1

[Neutron][drivers] Proposing Oleg Bondarev (obondarev) to the Drivers team
by Lajos Katona 19 Jan '22

19 Jan '22

Hi Neutron Drivers, I would like to propose Oleg Bondarev to be a member of the Neutron Drivers team. He has long experience with Neutron, he has been always around to help with advice and reviews, and enthusiastically participated in the Drivers meeting (big +1 as it is on Friday 1400UTC, quite late afternoon in his timezone :-)). Neutron drivers, please vote before the next Drivers meeting (next Friday, 21. January). Best Regards Lajos Katona (lajoskatona)

7 6

[kolla-anbsible][centos-stream][novnc]
by Franck VEDEL 19 Jan '22

19 Jan '22

Hello, what is the solution to adjust the size of novnc consoles. I found for ubuntu (https://docs.openstack.org/nova/rocky/admin/remote-console-access.html) but not for centos-stream which I use with kolla-ansible. thanks in advance Franck

1 0

[cinder] yoga R-9 virtual midcycle on 26 January
by Brian Rosmaita 19 Jan '22

19 Jan '22

As decided at today's weekly meeting, the Cinder Yoga R-9 virtual midcycle will be held: DATE: Wednesday 26 January 2022 TIME: 1400-1600 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. Please add topics to the midcycle etherpad: https://etherpad.opendev.org/p/cinder-yoga-midcycles cheers, brian

1 0

[kolla] Calling Kolla-ansible in an ansible playbook
by J-P Methot 19 Jan '22

19 Jan '22

Hi, I've been trying to write an ansible-playbook to run some kolla tasks and I've been wondering if this is even possible? I have kolla running inside a virtual environment, so of course I'm running into issues having ansible running it. The current task looks like this: - name: run kolla-ansible upgrade on controllers command: "{{ venv }}/bin/kolla-ansible --limit {{ item }} -i multinode upgrade" loop: - control - monitoring - storage When run, it's complaining that ansible isn't installed in the current virtual environment. I was under the impression that specifying the whole path to my executable would have it automatically run in that virtual environment, but visibly this excludes access to ansible that's installed there. So, basically, is what I'm trying to do even possible? And if so, what would be the best way to do it? -- Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc.

2 2

[cinder] festival of XS reviews 21 January 2022
by Brian Rosmaita 19 Jan '22

19 Jan '22

Hello Argonauts, This is a reminder that the most recent edition of the Cinder Festival of XS Reviews will be held at the end of this week on Friday 21 January. who: Everyone! what: The Cinder Festival of XS Reviews when: Friday 21 January 2022 from 1400-1600 UTC where: https://meetpad.opendev.org/cinder-festival-of-reviews etherpad: https://etherpad.opendev.org/p/cinder-festival-of-reviews This recurring meeting can be placed on your calendar by using this handy ICS file: http://eavesdrop.openstack.org/calendars/cinder-festival-of-reviews.ics See you there! brian

1 0

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

[largescale-sig] Next meeting: Jan 19th, 15utc
by Thierry Carrez 19 Jan '22

19 Jan '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. You can doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220119T15 We will be finalizing the discussion of our next OpenInfra Live episode. You can add other topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[Oslo] IRC meeting.
by Daniel Mats Niklas Bengtsson 19 Jan '22

19 Jan '22

Hi there, There were no more oslo meetings but I will take over the role of facilitator and organize the meetings. I think it's important and help to have a status and follow some topics. The next meeting will be Monday, then we will resume the old rhythm with a meeting on the first and third Monday of the month. Please feel free to update your name in the pinglist[1] if you want to join it or on the contrary if you do not want to. [1] https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_Template

1 0

[heat-tempest-plugin] call for help from plugin's maintainers
by Martin Kopec 19 Jan '22

19 Jan '22

Hello, most of the tests of heat-tempest-plugin have started failing. We noticed that in interop [1], however, we reproduced that in the project's gates as well [2]. I suspect it might be an issue with the new gabbi package - there has been an update recently. Could you please have a look. [1] https://review.opendev.org/c/openinfra/ansible-role-refstack-client/+/824832 [2] https://review.opendev.org/c/openstack/heat-tempest-plugin/+/823794 Thank you, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

3 6

[rbac][keystone][kolla][openstack-ansible][tripleo] RBAC in Yoga for deployment projects
by Mark Goddard 19 Jan '22

19 Jan '22

Hi,

1 0

[Ironic][docs] Moving API Documentation closer to code
by Mahnoor Asghar 19 Jan '22

19 Jan '22

Dear all, I am an Outreachy intern, working with OpenStack Ironic on improving their API reference documentation mechanism. Currently, the API documentation is kept separately from the code (in the Ironic repository), which means it diverges from the code, and is difficult to maintain and manage as development progresses. It would be desirable to auto-document our REST API interactions and data structures in code along with the very classes they come from. This way, we can clearly understand the request, the response, and any other important interaction details from a single point of view inside the code. It will also be a lot easier to maintain. The current Ironic API documentation is being generated by Sphinx, using the os-api-ref extension. It would be a viable solution to move the documentation from the separate sub-directory to docstrings within the code files itself, and develop a Sphinx extension that provides essential features to generate the documentation from docstrings. More details about the proposed extension, and its features can be found on the Ironic Storyboard [1]. The wider OpenStack community may be facing similar problems maintaining their documentation, and it would be helpful to understand their perspective and concerns - with respect to using such an extension, their expectations from it, collaborating on it, and whether they have additional ideas about how we may bring API documentation closer to the code. [1]: https://storyboard.openstack.org/#!/story/2009785 Thank you and regards, Mahnoor Asghar

4 6

[ironic] [release] RFC: stop doing bugfix branches for Bifrost?
by Dmitry Tantsur 19 Jan '22

19 Jan '22

Hi team! Some time ago we introduced bugfix/X.Y branches [1] to some of the Ironic projects. This has worked pretty well and has been very helpful in ironic/inspector/IPA, but I have second thoughts about Bifrost. First, maintaining Bifrost branches is tedious enough because of how many distros we support and how quickly they change. Second, our recommended approach to using Bifrost is to git-clone master and work from it. I'm honestly unsure if the regular stable branches are used (outside of the Kolla CI), let alone bugfix branches. (I also doubt that Bifrost releases are very popular or even meaningful, but that's another topic.) As one of few people who is maintaining bugfix branches, I suggest we stop making them for Bifrost and switch Bifrost back to normal cycle-with-intermediaries. We can keep releasing 3x per cycle, just to have checkpoints, but only create "normal" stable branches. Thoughts? Dmitry [1] https://specs.openstack.org/openstack/ironic-specs/specs/approved/new-relea… -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

5 4

[VGPU] Multiple VGPUs on one VM
by Jahson Babel 19 Jan '22

19 Jan '22

Hello folks, I've seen a thread on vGPUs on this mailing list lately and I was wondering if multiple vGPUs are supported on one VM on OpenStack. From the OpenStack's documentation this seems pretty clear that it's not. ( https://docs.openstack.org/nova/latest/admin/virtual-gpu.html) But on Nvidia's side multiple vGPUs should be able to be possible on specific Linux KVM version. (https://docs.nvidia.com/grid/latest/grid-vgpu-release-notes-red-hat-el-kvm/…) Only true for RHEL systems maybe. So which one of those pieces of information should I follow ? Presumably the OpenStack's side is the correct one but I would like to be sure. And does anyone has been able to attach multiples vgpus on one VM ? Another side question that I have in mind despite the fact that I can't see how it could possibly work. Is it possible to over-commit the vGPUs resources ? Via the placement API ? Thanks in advance. Kindly, Jahson Babel

1 0

[neutron] CI meeting agenda
by Slawek Kaplonski 18 Jan '22

18 Jan '22

Hi, Please remember that today at 3pm UTC we will have Neutron CI meeting. It will be on both IRC and video: [1] as meetpad.opendev.org seems that is still disabled. Agenda for the meeting is at [2]. [1] https://meet.jit.si/neutron-ci-meetings [2] https://etherpad.opendev.org/p/neutron-ci-meetings -- Slawek Kaplonski Principal Software Engineer Red Hat

2 3

Problem with ressource provider
by Marc-Antoine Godde (Student at CentraleSupelec) 18 Jan '22

18 Jan '22

Hello, In our cluster, we have 4 computes running and we have an issue with the number 4. We can't create VMs on it, we can't migrate VMs to or from that node. VMs are still perfectly working though. After a first diagnosis, it appears that there's a problem with the ressource provider. Node is declared in the db with: - name: os-compute-4, uuid: d12ea77b-d678-40ce-a813-d8094cabbbd8 Here are the ressource provider: - name: os-compute-4, uuid: a9dc2a56-5b2d-49b1-ac47-6d996d2d029a - name: os-compute-4.openstack.local, uuid: d12ea776-d678-40ce-a813-d8094cabbbd8 In our opinion, os-compute-4.openstack.local shouldn't be there at all. We want to destroy both of the ressource provider and recreate one. I must also precise that os-compute-4 ressource provider has 0 allocation and os-compute-4.openstack.local only 3 (there’s at least 50 VMs running on it…). Moreover, for these 3 allocations, the server uuid doesn't correspond to any existing VMs. Overall, none of the VMs has a ressource allocation on os-compute-4. We found the command nova-manage placement heal_allocations on the Internet but we can't find it in any container, maybe deprecated ? The cluster is running Ussuri installed with Openstack-ansible. If you have any suggestion, any help would be appreciated. Thanks. :) Best, Marc-Antoine Godde

2 4

[horizon] Missing button "create user" in dashboard
by Eugen Block 18 Jan '22

18 Jan '22

Hi *, I have a fresh Victoria installation where the "create user" button is missing in the dashboard. Creating users via CLI works fine, also when I go to https://controller/identity/users/create I see the dialog to create a new user. I see the same in an Ussuri installation. The clouds are deployed manually (we have our own Salt mechanism) on baremetal, the OS is openSUSE Leap 15.2. What I have tried so far is to apply the keystonev3_policy.json from [1], but without success. There are no other custom policies applied, most configs are on default. There are no obvious errors in the dashboard logs, and before I change too much I wanted to ask for your advice. Can anyone help me out? Please let me know if you need more information. Thanks in advance, Eugen [1] https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1775224

1 1

[nova] Instance Even Scheduling
by Ammad Syed 18 Jan '22

18 Jan '22

Hi, I have 5 compute nodes. When I deploy instances, the most of the instances automatically placed in node 1 or node 2. The other compute nodes remain empty or with one or two instances on it. enabled_filters = ComputeFilter,ComputeCapabilitiesFilter,ImagePropertiesFilter,ServerGroupAntiAffinityFilter,ServerGroupAffinityFilter,AggregateInstanceExtraSpecsFilter I have enabled the above filters. How to ensure that instances should be scheduled on compute nodes evenly on all compute hosts based on RAM only ? Like scheduler should schedule the instance on compute host which has a large amount of RAM available then other hosts. - Ammad

3 9

OpenInfra Live - January 20 at 1500 UTC
by Allison Price 18 Jan '22

18 Jan '22

Hi everyone, This week’s OpenInfra Live episode is brought to you by the global OpenInfra Community. As we approach the launch of the CFP (call for papers) for the upcoming OpenInfra Summit in Berlin (June 7-9), join members of the 2022 Programming Committee as they share their top tips and tricks for writing a winning submission and answer your questions on what they look for in talks. Erin Disney, Senior Event Marketing Manager at the OpenInfra Foundation will host members of the Berlin Summit Programming committee, including: Armstrong Foundjem (AI, Machine Learning & HPC) Amy Marrich (Getting Started) Shuquan Huang (5G, NFV, and Edge) Arkady Kanevsky (Hardware Enablement) Arne Wiebalck (Private and Hybrid Cloud) Episode: Berlin Summit 2022 CFP 101 Date and time: Thursday, January 20 at 9am CT (1500 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=9s1VPCyuJXI <https://www.youtube.com/watch?v=9s1VPCyuJXI> LinkedIn: https://www.linkedin.com/video/event/urn:li:ugcPost:6887809515576815616/ <https://www.linkedin.com/video/event/urn:li:ugcPost:6887809515576815616/> Facebook: https://www.facebook.com/104139126308032/posts/4735936496461582/ <https://www.facebook.com/104139126308032/posts/4735936496461582/> WeChat: the recording will be posted on OpenStack WeChat after the live stream Have an idea for a future episode? Share it now at ideas.openinfra.live <https://openinfrafoundation.formstack.com/forms/openinfralive>. Thanks, Allison

1 0

[TripleO] Gate/Check blocker - tripleo-ci-centos-9-content-provider
by Chandan Kumar 18 Jan '22

18 Jan '22

Hello All, tripleo-ci-centos-9-content-provider is failing in Check and gate pipeline with following error ``` Last metadata expiration check: 0:01:21 ago on Tue 18 Jan 2022 03:13:29 AM UTC. centos-stream-release-9.0-6.el9.noarch.rpm 7.9 MB/s | 26 kB 00:00 warning: centos-stream-release-9.0-6.el9.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 8483c65d: NOKEY Verifying... ######################################## Preparing... ######################################## package centos-stream-release-9.0-8.el9.noarch (which is newer than centos-stream-release-9.0-6.el9.noarch) is already installed ``` A bug is already logged against the failure: https://bugs.launchpad.net/tripleo/+bug/1958202 and wip fix is here: https://review.opendev.org/c/openstack/tripleo-common/+/825038 Please hold your recheck on the tripleo patches where the CS9 content provider runs. Will update this thread once we have fixes merged. Thanks, Chandan Kumar

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