July 2021 - openstack-discuss - lists.openstack.org

[PTLs][release] Xena Cycle Highlights
by helena＠openstack.org 12 Aug '21

12 Aug '21

Hello Everyone!It's that time of the year once again! It's time to start thinking about calling out 'cycle-highlights' in your deliverables! As PTLs, you probably get many pings towards the end of every release cycle by various parties (marketing, management, journalists, etc) asking for highlights of what is new and what significant changes are coming in the new release. By putting them all in the same place it makes them easy to reference because they get compiled into a pretty website like this from the last few releases: Ussuri[1], Victoria[2]. We don't need a fully fledged marketing message, just a few highlights (3-4 ideally), from each project team. Looking through your release notes might be a good place to start. The deadline for cycle highlights is the end of the R-5 week [3] on September 3.How To Reminder: -------------------------Simply add them to the deliverables/$RELEASE/$PROJECT.yaml in the openstack/releases repo like this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin.The formatting options for this tag are the same as what you are probably used to with Reno release notes.Also, you can check on the formatting of the output by either running locally: tox -e docsAnd then checking the resulting doc/build/html/$RELEASE/highlights.html file or the output of the build-openstack-sphinx-docs job under html/$RELEASE/highlights.html. Feel free to add Kendall Nelson (diablo_rojo) as a reviewer on your patches. Can't wait to see you all have accomplished this release! Thanks :) -Helena Spease (hspease) [1] [ https://releases.openstack.org/ussuri/highlights.html ]( https://releases.openstack.org/ussuri/highlights.html ) [2] https://releases.openstack.org/victoria/highlights.html [3] https://releases.openstack.org/xena/schedule.html

1 1

[interop][cinder] review of next.json (part 2)
by Brian Rosmaita 09 Aug '21

09 Aug '21

Hello Interop WG, The Cinder team completed its discussion of what capabilities should be added as advisory in next.json at yesterday's weekly cinder meeting [0]. The tldr; is that we don't have anything to propose for inclusion in next.json at the present time. The team does have some general questions that would help us determine the suitability of some proposed capabilities. We'd like to invite someone from the Interop WG to the cinder xena R-9 virtual midcycle (Wednesday 4 August 2021, 1400-1600 UTC) so we can discuss this "live". So if someone could put 1400 UTC 4 August on their schedule for a 20 minute discussion, that would be very helpful. cheers, brian [0] http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-05-12-14.00…

3 8

Re: [neutron-vpnaas][kolla-ansible][victoria] Growing memory consumption with only one VPN connection
by at 09 Aug '21

09 Aug '21

Hi, 1. There is only one, bidirectional vpn connection between project networks in two regions 2. there is no (or almost no) traffic on this vpn link 3. second region is on one host (kolla all-in-one) and situation looks the same- with vpn service enabled there is excessive Memory use (growing also about 5-6MB/ minute and forcing the system to use swapfile) there is no big cpu usage (ofcourse also due to no traffic inside VPN) It's the same case even if there's no vpn connection configured. Best regards Adam Tomas Wysłane z iPhone'a > Wiadomość napisana przez Vinh Nguyen Duc <vinhducnguyen1708(a)gmail.com> w dniu 29.06.2021, o godz. 11:04: > > > Hi Adam, > Do you think the VPN connection is use CPU and memory to encrypt the VPN traffic? > > On Mon, Jun 28, 2021 at 14:30 Adam Tomas <bkslash(a)poczta.onet.pl <mailto:bkslash@poczta.onet.pl>> wrote: > Hi, > I have problem with neutron vpnaas - after enabling vpnaas plugin everything was ok at first. I was able to create VPN connection and communication is correct. But after a week of running vpnaas (only one VPN connection created/working!) I’ve noticed, that neutron-vpnaas takes more and more memory. I have 5 processes on each controller (there should be always five? Or it is changing dynamically?): > > 42435 1545384 0.6 8.6 5802516 5712412 ? S Jun15 110:50 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545389 0.6 8.5 5735832 5645856 ? S Jun15 112:16 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545378 0.5 8.5 5734192 5643620 ? S Jun15 108:09 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545372 0.5 8.5 5731128 5641436 ? S Jun15 109:07 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > 42435 1545369 0.6 8.4 5637084 5547392 ? S Jun15 114:21 /var/lib/kolla/venv/bin/python3.8 /var/lib/kolla/venv/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf > > now neutron_server takes over 27G of RAM on each controller: > > neutron_server running 10.2 27.2G > > After stopping all neutron containers and starting it again neutron takes a lot less memory: > > neutron_server running 0.5 583M > > but memory usage keeps growing (about 5-6 M every minute). > What’s wrong? When I disable vpnaas globally there’s no problem with excessive memory usage, so it’s vpnaas for sure… > > Best regards > Adam Tomas

3 2

[neutron][ops] VLAN Provider Network
by DHilsbos＠performair.com 07 Aug '21

07 Aug '21

All; We're using OpenStack Victoria, with OVS networking (no OVN). I'm having some problems with a VLAN provider network that I added to my OpenStack. I have other VLAN provider networks, that I based this one off of. Instances are getting the tap interfaces, but these interfaces are not getting IP addresses, and when a static IP is given, they can't ping either the DHCP address or the gateway address. I have checked the switch configuration, to verify the VLAN is bound appropriately. I rebooted the whole cluster to ensure the configuration change applied. Here's a snip our plugin.ini [ml2_type_vlan] network_vlan_ranges = provider_core:55:55,provider_core:64:64,... 64 works, 55, doesn't. I'm not seeing anything concerning in /var/log/openvswitch/ovs-vswitchd.log I'm sure it's something dumb, but I'm not seeing it. Any suggestions for what else to look at? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

2 2

[wallaby][neutron][ovn] Multiple VLAN ranges and FLAT network
by Malik Obaid 06 Aug '21

06 Aug '21

Hi, I am using Openstack Wallaby release on Ubuntu 20.04. I am configuring openstack neutron for production and just want to know is there a way to specify different vlan ranges with multiple physical networks. I would really appreciate any input in this regard. Thank you. Regards, Malik Obaid

2 1

gerrit no longer lading from iphone
by Sorin Sbarnea 05 Aug '21

05 Aug '21

I am wondering if something was changed on our gerrit deployment recently as it seems to no longer load on ios safari. I know,… not the most common use case… still adding the usual recheck can prove useful after checking zuul comment. /zbr -- -- /zbr

5 7

Migrating VM's
by Derek O keeffe 04 Aug '21

04 Aug '21

Hi all, I have a question. If we have an old openstack deployment (Queens) that have VM's (with & without volumes attached) and we want to migrate those to a new deploy (Victoria) can this be achieved by the owners of the VM's through horizon in some way? We can take snapshots of the vm's that don't have volumes attached, copy them to the new controller and re instantiate them but we haven't found a solution for the volumes yet. This give us more work though as it all needs to be done over cli so the user is taken out of the loop and it falls on us 3 admins to move over 300 VM's. Any advice or info would be greatly appreciated. Thanks in advance. Derek

3 7

[nova][neutron][deployment-projects] Re secbug #1734320
by Radosław Piliszek 04 Aug '21

04 Aug '21

Hello Folks! I am writing this because a recent patch proposed to DevStack [1] mentioned "when using ml2/ovs vif isolation should always be used to prevent cross tenant traffic during a live migration" which is related to secbug #1734320 "Eavesdropping private traffic" [2]. However, I've found that none of the publicly-available deployment projects seem to be using ``isolate_vif``. [3] [4] Should this be corrected? PS: I used the deployment-projects tag as a collective tag to avoid mentioning all the projects (as it is too long to write :-) ). I hope that relevant people see this if need be or someone passes the information to them. For now, I am curious whether this should actually be enforced by default with ML2/OVS. [1] https://review.opendev.org/c/openstack/devstack/+/796826 [2] https://bugs.launchpad.net/neutron/+bug/1734320 [3] https://codesearch.opendev.org/?q=%5Cbisolate_vif%5Cb&i=nope&files=&exclude… [4] https://github.com/search?p=1&q=isolate_vif&type=Code -yoctozepto

3 2

stackalytics.com/api/1.0/activity
by Csatari, Gergely (Nokia - FI/Espoo) 03 Aug '21

03 Aug '21

Hi, We plan to use the API of stackalytics.com and we realized that the data it provides ([1<https://www.stackalytics.com/api/1.0/activity?page_size=100>]) is never more recent than March 2021. Does anyone know what is the reason for this? Thanks, Gergely 1: https://www.stackalytics.com/api/1.0/activity?page_size=100

5 5

[swift] EC data left in old location after rebalance
by Reid Guyett 03 Aug '21

03 Aug '21

Hello, We started using EC policies in a new cluster a few months ago and added more capacity. During the rebalance (started June 30), it seems that all the data was copied to the new locations but it didn't clean up the old locations. This was identified through our handoff monitoring. OS: Ubuntu 18.04 Swift: 2.17.1 Example: List of devices for partition ~$ swift-get-nodes /etc/swift/object-4.ring.gz -p 14242 ... removed ... Server:Port Device x.x.x.31:6031 d31 Server:Port Device x.x.x.66:6030 d30 Server:Port Device x.x.x.25:6029 d29 Server:Port Device x.x.x.33:6027 d27 Server:Port Device x.x.x.36:6020 d20 Server:Port Device x.x.x.29:6018 d18 Server:Port Device x.x.x.21:6033 d33 Server:Port Device x.x.x.27:6025 d25 Server:Port Device x.x.x.35:6022 d22 Server:Port Device x.x.x.39:6031 d31 Server:Port Device x.x.x.28:6032 d32 Server:Port Device x.x.x.23:6021 d21 Server:Port Device x.x.x.26:6022 d22 Server:Port Device x.x.x.34:6023 d23 Server:Port Device x.x.x.37:6019 d19 Server:Port Device x.x.x.30:6017 d17 Server:Port Device x.x.x.22:6027 d27 Server:Port Device x.x.x.24:6031 d31 Server:Port Device x.x.x.32:6032 d32 Partitions look to have the correct data on them: ~$ ssh root(a)x.x.x.31 "ls -lah ${DEVICE:-/srv/node*}/d31/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.66 "ls -lah ${DEVICE:-/srv/node*}/d30/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.25 "ls -lah ${DEVICE:-/srv/node*}/d29/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.33 "ls -lah ${DEVICE:-/srv/node*}/d27/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.36 "ls -lah ${DEVICE:-/srv/node*}/d20/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.29 "ls -lah ${DEVICE:-/srv/node*}/d18/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.21 "ls -lah ${DEVICE:-/srv/node*}/d33/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.27 "ls -lah ${DEVICE:-/srv/node*}/d25/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.35 "ls -lah ${DEVICE:-/srv/node*}/d22/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.39 "ls -lah ${DEVICE:-/srv/node*}/d31/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.28 "ls -lah ${DEVICE:-/srv/node*}/d32/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.23 "ls -lah ${DEVICE:-/srv/node*}/d21/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.26 "ls -lah ${DEVICE:-/srv/node*}/d22/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.34 "ls -lah ${DEVICE:-/srv/node*}/d23/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.37 "ls -lah ${DEVICE:-/srv/node*}/d19/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.30 "ls -lah ${DEVICE:-/srv/node*}/d17/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.22 "ls -lah ${DEVICE:-/srv/node*}/d27/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.24 "ls -lah ${DEVICE:-/srv/node*}/d31/objects-4/14242 | wc -l" 664 ~$ ssh root(a)x.x.x.32 "ls -lah ${DEVICE:-/srv/node*}/d32/objects-4/14242 | wc -l" 664 >From one of the nodes that does not belong to the list above. This partition should not exist on this node after the rebalance. x.x.x.20:~# ls /srv/node/d28/objects-4/14242 | wc -l 627 The reconstructor is throwing a lot of these unexpected response errors in the logs. Manually running it from the node that should not have the partition, I can reproduce the error. x.x.y.0/24 is the replication network. x.x.x.20:~# swift-object-reconstructor /etc/swift/object-server.conf -d d28 -p 14242 -o -v object-reconstructor: x.x.y.42:6200/d30/14242 Unexpected response: ":ERROR: 500 'ERROR: With :UPDATES: 36 failures to 0 successes'" There looked to have been some partition locations cleaned up around July 11. Our expectation is that the old partition locations should be cleaned gradually since June 30 but we're not seeing that. I Was hoping for some ideas on what may be the problem (if any) and how we can make sure that the old partitions are cleaned up. Thanks, Reid

2 4

[ironic] Xena Mid-cycle
by Iury Gregory 03 Aug '21

03 Aug '21

Hello Ironicers! In our upstream meeting we decided we should do a virtual mid-cycle! If you are interested please fill out the doodle[1] and add topics in the etherpad[2]. Keep in mind we have contributors in many time zones, if you think we should add more time windows, please let me know. Maybe we can have multiple sessions each day so we can accommodate APAC TZ. I will close the doodle before our upstream meeting next week. [1] https://doodle.com/poll/mhh959u4s4rturxi [2] https://etherpad.opendev.org/p/ironic-xena-midcycle -- *Att[]'sIury Gregory Melo Ferreira * *MSc in Computer Science at UFCG* *Part of the ironic-core and puppet-manager-core team in OpenStack* *Software Engineer at Red Hat Czech* *Social*: https://www.linkedin.com/in/iurygregory *E-mail: iurygregory(a)gmail.com <iurygregory(a)gmail.com>*

1 1

[nova][gate] nova-tox-functional-* jobs failing on master branch
by melanie witt 02 Aug '21

02 Aug '21

Hey all, The nova-tox-functional-* jobs on the openstack/nova master branch are currently failing 100% of the time: https://zuul.openstack.org/builds?job_name=nova-tox-functional-py38&branch=… This is due to another issue with time overrides (a lack thereof) in the test_archive_task_logs functional tests. The same bug has happened in the past and the fix is now known to have been unsuccessful: https://bugs.launchpad.net/nova/+bug/1934519 Another fix has been proposed here: https://review.opendev.org/c/openstack/nova/+/803106 Please hold your rechecks until the fix merges and apologies for the trouble. -melwitt

2 2

[TripleO] centos7 gate blocker (stable/train) please hold rechecks
by Marios Andreou 02 Aug '21

02 Aug '21

Hello tripleo o/ new gate blocker for centos7 hitting stable/train tripleo repos https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ci-centos-7-co… bug is at https://bugs.launchpad.net/tripleo/+bug/1938079 - hitting stable/train (we only run c7 jobs there). investigation/resolution ongoing please hold rechecks for centos7 jobs. thank you

2 3

[cinder-backup][ceph] replicate volume between sites
by Tony Liu 01 Aug '21

01 Aug '21

Hi, I have two sites with OpenStack Victoria deployed by Kolla and Ceph Octopus deployed by cephadm. As what I know, either Swift (implemented by RADOSGW) or RBD is supported to be the backend of cinder-backup. My intention is to use one of those option to replicate Cinder volume from one site to another, based on RADOSGW multi-site support or RBD mirroring. I wonder if anyone has done this and could share some opinions, like pros, cons, which way is better for which case? One specific thing I am not clear is that, how to import RBD volume into Cinder when it gets to another site. There used to be a way, but it's replicated. Any comments is appreciated. Thanks! Tony

1 1

[neutron] dnsmasq refusing to provide ipv6 address over dhcpv6 after a server rebuild
by Thomas Goirand 01 Aug '21

01 Aug '21

Hi, I've filled this bug in Debian concerning our official image: https://bugs.debian.org/991613 tl;dr: When doing "openstack server rebuild", dnsmasq refuses to provide an ipv6 when the instance does a dhcpv6 request, because after a rebuild, the instance generates a different DUID. So I wonder if there's a way to fix this by configuring dnsmasq in some ways, maybe by telling it to not use the DUID at all. So far, I haven't found a way yet. Does anyone have a good answer to this problem? Ideally, I'd like to find a way to fix on both side (ie: OpenStack *AND* the official Debian image), so I can make sure to never encounter the issue ever again. Cheers, Thomas Goirand (zigo)

1 0

Routed provider networks
by Gk Gk 31 Jul '21

31 Jul '21

Hi, I learnt that routed provider networks from the below links: https://docs.openstack.org/neutron/latest/admin/config-routed-networks.html https://www.youtube.com/watch?v=HwQFmzXdqZM This concept, according to them solves two issues: 1. Large broadcast L2 domains with failure domains 2. If there are multiple L2 provider networks, users are confused, unable to choose a particular network. My question is, how does routed provider networks solve the second problem mentioned above ? If one user wants to use external network for internet, how can he choose from this one single routed provider network ? Or, if another user wants another provider network, how can he choose that particular network ? Also the same can also be achieved by creating nova aggregates or availability zones and mapping computes with particular provider network connections and ask users to use that particular nova AZ, without creating routed provider networks at all ? Can someone clarify this for me ? Thanks Kumar

2 2

[all][tc] What's happening in Technical Committee: summary 30th July, 21: Reading: 5 min
by Ghanshyam Mann 31 Jul '21

31 Jul '21

Hello Everyone, Here is last week's summary of the Technical Committee activities. 1. What we completed this week: ========================= * Retired tripleo-common-tempest-plugin[1] 2. TC Meetings: ============ * TC held this week meeting on Thursday; you can find the full meeting logs in the below link: - https://meetings.opendev.org/meetings/tc/2021/tc.2021-07-29-15.00.log.html * We will have next week's meeting on Aug 5th, Thursday 15:00 UTC[2]. 3. Activities In progress: ================== TC Tracker for Xena cycle ------------------------------ TC is using the etherpad[3] for Xena cycle working item. We will be checking and updating the status biweekly in the same etherpad. Open Reviews ----------------- * Three open reviews for ongoing activities[4]. Migration from Freenode to OFTC ----------------------------------------- * Only few repo patches are left to merge. requesting core team of those repos to merge them. ** https://review.opendev.org/q/topic:%2522oftc%2522+status:open * openstack blog site is updated for freenode->oftc, Thanks Jimmy for taking care of it. * All the required work for this migration is tracked in this etherpad[5] Test support for TLS default: ---------------------------------- * Rico has started a separate email thread over testing with tls-proxy enabled[6], we encourage projects to participate in that testing and help to enable the tls-proxy in gate testing. Project updates: ------------------- * Retiring js-openstack-lib [7] * Adding tap-as-a-service back to neutron stadium[8] Yoga release community-wide goal ----------------------------------------- * Please add the possible candidates in this etherpad [9]. * Current status: One goal "Secure RBAC" is proposed. Other Changes ------------------ * Defining Yoga release testing runtime[10] PTG planning ---------------- * TC booked three slots: ** 1. Monday 15-17 UTC for TC + Community Leaders ** 2. Thursday 13-17 UTC ** 3. Friday 13-17UTC * We are collecting the PTG topics in etherpad[11], feel free to add any topic you want to discuss. 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[12]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [13] 3. Office hours: The Technical Committee offers a weekly office hour every Tuesday at 0100 UTC [14] 4. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://review.opendev.org/c/openstack/governance/+/800432 [2] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [3] https://etherpad.opendev.org/p/tc-xena-tracker [4] https://review.opendev.org/q/project:openstack/governance+status:open [5] https://etherpad.opendev.org/p/openstack-irc-migration-to-oftc [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-June/023000.html [7] https://review.opendev.org/c/openstack/governance/+/798540 [8] https://review.opendev.org/c/openstack/governance/+/802833 [9] https://etherpad.opendev.org/p/y-series-goals [10] https://review.opendev.org/c/openstack/governance/+/799927 [11] https://etherpad.opendev.org/p/tc-yoga-ptg [12] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [13] http://eavesdrop.openstack.org/#Technical_Committee_Meeting [14] http://eavesdrop.openstack.org/#Technical_Committee_Office_hours -gmann

1 0

Redhat RHEV Virtualisation and logical data volumes
by KK CHN 31 Jul '21

31 Jul '21

Is it practically or theoretically possible to export image/Disk as single image /Disk from RHEV/Virtualization Manager where VMs have logical volumes attached to it ? Any other data/information do I need to provide for the above question let know. Problem scenario is this: We have hosted VMs on RHEV virtualization environment. Each VM has associated Logical Volumes attached to the VM. We are planning to migrate our VMs to OpenStack (Ussuri, qemu KVM and Glance) Right now Our System Integrator who maintains these VMs on their RHEV virtualization environment exporting each VM as Three separate images. One for OS image, other for boot and third one for data volume disk image ( they use logical volumes for data storage, might be added disks when data storage was insufficient at any point of time. ) But I want to get each VM with data volumes as a single disk image . IS THIS THEORETICALLY or PRACTICALLY POSSIBLE using RHEV Virtualization tools ? if so how ? ( OR any other methods do this ?) OR am I asking a STUPID QUESTION ? If so WHY ? Kindly enlighten me !!! I am at the end of the rope with this issue. Thanks in advance, Kris

1 0

[sahara][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Sahara Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've seen that Sahara's stable branches started to fail as well so collected the recent failures with examples. Please take a look at them and try to fix them. The errors seem to be related to cinder's v2 removal ("No module named 'cinderclient.v2'"): sahara: stein - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/77f0f18b297240fa92eb5b22c8200598 sahara: train - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/23c860b5af74449bbed561d5853963ea sahara: ussuri - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/6e8ec09a4cc54eadaeaa9fe88eb249d9 sahara: victoria - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/db254fea259e482ab3ff3b404feeed28 sahara: wallaby - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/1e50a52edefe4f8191f0f0d529db7a63 [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

2 2

[cinder][qa][devstack][ci] need help running centos-8/opensuse-15 on stable/victoria
by Brian Rosmaita 31 Jul '21

31 Jul '21

Does anyone have any zuul jobs running in stable/victoria that use either of these nodesets: - devstack-single-node-centos-8 - devstack-single-node-opensuse-15 I can't get devstack to complete building on either (missing package, though different for each distro). I figure that someone in openstack must have this working, given that Python 3.6 and Centos-8 and OpenSUSE-15 are listed in the Tested Runtimes for Victoria [0]. Here's the failing patch if anyone would be kind enough to point out what I'm mis-configuring: https://review.opendev.org/c/openstack/python-cinderclient/+/800635/ thanks! brian [0] https://governance.openstack.org/tc/reference/runtimes/victoria.html

6 7

[nova][wallaby] Nova policy rule project_member_api not effective
by Taltavull Jean-Francois 31 Jul '21

31 Jul '21

Hi All, Despite the fact that oslopolicy-policy-generator --namespace nova shows the rules "project_member_api": "role:member and project_id:%(project_id)s" and "os_compute_api:servers:create": "rule:project_member_api", it is still possible to create a server even if you only have the role "member" on the project. Is this behavior normal or not ? Must we consider that we are in a phase of transition about nova default policies ? Thanks, Jean-Francois

2 3

[trove][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Trove Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * bandit should be constrained: trove: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/c8da125f4a7f4dafaa5f3b337a0d14c2 trove: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/9973f556913e439a912455712ecbd54a trove: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/6ed08e9f7d25414e8ee04db14a753649 trove: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/0a3b1f6668a740c69f888c7272e24d58 trove: rocky - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/208c02dfcbc9487bbaca1eccc53e8a67 trove: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/f13cc87c4f104727ab4f4696ad7ed160 trove: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/9aff516680074e11b52ea07fac389fa0 trove: train - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/db3b97cec2604318a7bd129fa8cd3bc2 * version conflict revealed with the new pip resolver: trove: stein - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/30f8f8a99fea4a93bab55b694c9e79e9 trove: train - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/00b400d2485a45fc997ebd35d48a506d trove: train - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/5e6a8f14ea93456ba70f5e1e3ee689a9 trove: train - openstack-tox-py37 -- https://zuul.opendev.org/t/openstack/build/e3c9201c92874e3fa25357171741cad2 [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[neutron][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Neutron Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * horizon's pike + queens were deprecated: networking-bgpvpn: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/553d4923eeca421c9ac56d193781b487 networking-bgpvpn: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/0fe12998347c4fa19ce3e04450bd914d networking-bgpvpn: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/d804b266bfdc408dbd1dd517b5901914 networking-bgpvpn: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/9151ba1cb74e4f569d863b7a90a8b702 * some dependency issues + unit tests are broken: neutron-vpnaas: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/64d92abffe7d48b1bcc3d3f42f8a1a24 neutron-vpnaas: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/743f561a2bb34875b86917cfe8861a53 neutron-vpnaas: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/e700494509934ba995f8c4b0e69f4627 neutron-vpnaas: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/4339034bc4014a0292310fd013d46caa neutron-vpnaas: victoria - openstack-tox-docs -- https://zuul.opendev.org/t/openstack/build/83d8251153b64de488bae3972968256f neutron-vpnaas: victoria - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/02e214a1483a4778986697ba6c85cbf9 neutron-vpnaas: victoria - openstack-tox-py38 -- https://zuul.opendev.org/t/openstack/build/a746a0bc5a1c4caeb6b813a7dd83878c [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[murano][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Murano Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root causes): * bandit should be constrained: murano: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/6ee6c9548d6b47e79361151964992ddf murano: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/fbfe0f67b90f4b3189a13e02a5b7f274 murano: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/c254a7f764f547e4a5bf8467cbcbe24b murano: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/b9646137d45c49ab8f10c2031135d21e murano: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/63f53b3df8a940f6b86c450617882cfc murano: stein - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/be63abe6be9a4d1f90c8d74fd9c4a407 * broken unittest: murano: victoria - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/b403e1a7431a484e90b23738a56669c7 murano: victoria - openstack-tox-py38 -- https://zuul.opendev.org/t/openstack/build/7f886d7e21864f4d941ad0a03d61ec4d murano: wallaby - openstack-tox-py36 -- https://zuul.opendev.org/t/openstack/build/dc61998732ff4d13a6e8c9d1f82ccd8d murano: wallaby - openstack-tox-py38 -- https://zuul.opendev.org/t/openstack/build/cc2fa00e650d4cd1973fd76dc1649624 * and also master is broken. [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0

[designate][stable] periodic-stable errors
by Előd Illés 31 Jul '21

31 Jul '21

Hi Designate Team, In the last couple of months the periodic-stable job errors (and thus the mails on openstack-stable-maint mailing list [1], where mails are sent from every failing jobs) increased significantly. I've talked with the infra team as the mail traffic is quite visible for them as well. I've collected the recent failures with examples that are failing constantly. Please take a look at them and try to fix them wherever it is possible. Since the old branches seem quite abandoned in some cases, they might need maintainers to step up to keep those gates healthy, or in case there are no maintainers, then it might worth to think of transitioning those broken old branches to End of Life. :/ And the list (with possible root cause): * bandit should be constrained: designate: pike - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/810cf80432dc4b90a7367b5f2107147e designate: pike - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/11d042ab2e82478db75d877f3c62cd62 designate: queens - build-openstack-sphinx-docs -- https://zuul.opendev.org/t/openstack/build/4cd73558ffb3402e8f25f602d85aec94 designate: queens - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/6c0b8dd6cee24b7eab9153bfc0e1dd61 designate: rocky - openstack-tox-py27 -- https://zuul.opendev.org/t/openstack/build/8d4d56e05ec94870823d3e057ee8ea4a [1] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-July/threa… Thanks, Előd

1 0