- openstack-discuss - lists.openstack.org

Glance review party - 2021-12-10T14:00:00Z
by Cyril Roelandt 07 Dec '21

07 Dec '21

Hello, On Friday (2021-12-10), at 14:00 UTC, we will have a "review party" for Glance. The party should last 2 to 3 hours, and the goal will be to clean the backlogs of glance_store and glanceclient, and try to work on the glance backlog as well if there is enough time. If some of your patches are currently in "merge conflict", please rebase them and make sure the tests pass, which will allow us to review them. If you think some of your *Glance* patches are a top priority for the project, please answer this email with a link to them, and we will try to make time to review them on Friday. We will be using https://bluejeans.com/u/croeland to coordinate. Happy Hacking! Cyril Roelandt

1 0

[neutron] Instances can't get IP from the DHCP server in OpenStack
by 韩光宇 07 Dec '21

07 Dec '21

Hi, I'm trying to create instance in OpenStack Victoria. But, I am facing a issues about dhcp of neutron. I have OpenStack Victoria running in one baremetl server with uniontech os(a downstream of centos 8). I have a Flat network created in the range of 10.12.21.190-10.12.21.195. I selected to have a DHCP. The instance ran, and neutron-dhcp-agent.service had allocated a IP to it.  # openstack server list +--------------------------------------+-------+--------+-----------------------+----------------+--------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+-------+--------+-----------------------+----------------+--------+ | 4ccae37e-fbfe-4acb-a109-e1bc9175c2e0 | inst1 | ACTIVE | provider=10.12.21.192 | centos8-server | h2 | +--------------------------------------+-------+--------+-----------------------+----------------+--------+ But the instance can't get a response from DHCP.  No any error in log. And if I setup the ip manually in the instance I can get access to the gateway, dhcp port and external network. I can catpure the DHCP request in any network device in the server, include dhcp port(10.12.21.190). But no response.  Dnsmasq process was running and had  # openstack port list +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+ | ID | Name | MAC Address | Fixed IP Addresses | Status | +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+ | 5ab32ca8-2d1d-47cf-9a62-7c01d21abaf0 | | fa:16:3e:1d:48:45 | ip_address='10.12.21.192', subnet_id='3daf5a55-e76a-4093-8533-78d9464b1beb' | ACTIVE | | 63fb2306-7759-4933-8d93-590e3a56f315 | | fa:16:3e:c5:59:9a | ip_address='10.12.21.190', subnet_id='3daf5a55-e76a-4093-8533-78d9464b1beb' | ACTIVE | +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------+--------+ # ip netns qdhcp-ec2c4d9d-888b-4312-b0af-ab2127b76e0e (id: 0) # sudo ip netns exec qdhcp-ec2c4d9d-888b-4312-b0af-ab2127b76e0e sudo tcpdump -n -S -i tap63fb2306-77|grep DHCP ## notes: fa:16:3e:1d:48:45 is the mac of nic of inst1 dropped privs to tcpdump tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on tap63fb2306-77, link-type EN10MB (Ethernet), capture size 262144 bytes 16:47:18.194028 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:1d:48:45, length 276 16:47:21.146736 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:1d:48:45, length 276 16:47:25.226387 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:1d:48:45, length 276 more detail informations: # ps -ef|grep dnsmasq dnsmasq 7441 1 0 12月03 ? 00:00:00 dnsmasq --no-hosts --no-resolv --pid-file=/var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/pid --dhcp-hostsfile=/var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/host --addn-hosts=/var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/addn_hosts --dhcp-optsfile=/var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/opts --dhcp-leasefile=/var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/leases --dhcp-match=set:ipxe,175 --dhcp-userclass=set:ipxe6,iPXE --local-service --bind-dynamic --dhcp-range=set:subnet-3daf5a55-e76a-4093-8533-78d9464b1beb,10.12.21.0,static,255.255.255.0,86400s --dhcp-option-force=option:mtu,1500 --dhcp-lease-max=256 --conf-file= --domain=openstacklocal dnsmasq 317868 1 0 14:33 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper root 317869 317868 0 14:33 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper root 340315 317310 0 18:43 pts/2 00:00:00 grep --color=auto dnsmasq [root@a16 ~]# cat /var/lib/neutron/dhcp/ec2c4d9d-888b-4312-b0af-ab2127b76e0e/host fa:16:3e:c5:59:9a,host-10-12-21-190.openstacklocal,10.12.21.190 fa:16:3e:1d:48:45,host-10-12-21-192.openstacklocal,10.12.21.192 # ovs-vsctl show adbd4b0c-cb78-4b8f-b8a6-197c5948312c Manager "ptcp:6640:127.0.0.1" is_connected: true Bridge br0 Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port enp5s0 Interface enp5s0 Port phy-br0 Interface phy-br0 type: patch options: {peer=int-br0} Port br0 Interface br0 type: internal Bridge br-tun Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port br-tun Interface br-tun type: internal Port patch-int Interface patch-int type: patch options: {peer=patch-tun} Bridge br-int Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure datapath_type: system Port int-br0 Interface int-br0 type: patch options: {peer=phy-br0} Port br-int Interface br-int type: internal Port tap63fb2306-77 tag: 1 Interface tap63fb2306-77 type: internal Port patch-tun Interface patch-tun type: patch options: {peer=patch-int} Port qvo5ab32ca8-2d tag: 1 Interface qvo5ab32ca8-2d ovs_version: "2.13.0". # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master ovs-system state UP group default qlen 1000 link/ether 1c:69:7a:92:be:30 brd ff:ff:ff:ff:ff:ff 3: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether ea:f5:ce:24:93:12 brd ff:ff:ff:ff:ff:ff 4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 1c:69:7a:92:be:30 brd ff:ff:ff:ff:ff:ff inet 10.12.21.142/24 scope global br0 valid_lft forever preferred_lft forever inet6 fe80::1e69:7aff:fe92:be30/64 scope link valid_lft forever preferred_lft forever 5: br-int: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether ba:5d:16:cf:89:40 brd ff:ff:ff:ff:ff:ff inet6 fe80::b85d:16ff:fecf:8940/64 scope link valid_lft forever preferred_lft forever 9: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 86:bb:24:69:7e:43 brd ff:ff:ff:ff:ff:ff 11: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:4d:96:e4 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 12: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:4d:96:e4 brd ff:ff:ff:ff:ff:ff 13: qbr5ab32ca8-2d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 76:0e:be:40:a6:ee brd ff:ff:ff:ff:ff:ff 14: qvo5ab32ca8-2d@qvb5ab32ca8-2d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master ovs-system state UP group default qlen 1000 link/ether 12:90:d5:07:2a:a2 brd ff:ff:ff:ff:ff:ff inet6 fe80::1090:d5ff:fe07:2aa2/64 scope link valid_lft forever preferred_lft forever 15: qvb5ab32ca8-2d@qvo5ab32ca8-2d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master qbr5ab32ca8-2d state UP group default qlen 1000 link/ether 76:0e:be:40:a6:ee brd ff:ff:ff:ff:ff:ff inet6 fe80::740e:beff:fe40:a6ee/64 scope link valid_lft forever preferred_lft forever 16: tap5ab32ca8-2d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master qbr5ab32ca8-2d state UNKNOWN group default qlen 1000 link/ether fe:16:3e:1d:48:45 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe1d:4845/64 scope link valid_lft forever preferred_lft forever # cat /etc/neutron/plugins/ml2/openvswitch_agent.ini [ovs] local_ip = 10.12.21.142 datapath_type = system bridge_mappings = provider:br0 [vxlan] enable_vxlan = true local_ip = 10.12.21.142 l2_population = true prevent_arp_spoofing = True [securitygroup] enable_security_group = True firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver # cat /etc/neutron/dhcp_agent.ini [DEFAULT] interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq enable_isolated_metadata = true     I would very very appreciate any kind of guidance or help. Thanks, Han Guangyu

2 4

[neutron][CI] How to reduce number of rechecks - brainstorming
by Slawek Kaplonski 07 Dec '21

07 Dec '21

Hi, Recently I spent some time to check how many rechecks we need in Neutron to get patch merged and I compared it to some other OpenStack projects (see [1] for details). TL;DR - results aren't good for us and I think we really need to do something with that. Of course "easiest" thing to say is that we should fix issues which we are hitting in the CI to make jobs more stable. But it's not that easy. We are struggling with those jobs for very long time. We have CI related meeting every week and we are fixing what we can there. Unfortunately there is still bunch of issues which we can't fix so far because they are intermittent and hard to reproduce locally or in some cases the issues aren't realy related to the Neutron or there are new bugs which we need to investigate and fix :) So this is never ending battle for us. The problem is that we have to test various backends, drivers, etc. so as a result we have many jobs running on each patch - excluding UT, pep8 and docs jobs we have around 19 jobs in check and 14 jobs in gate queue. In the past we made a lot of improvements, like e.g. we improved irrelevant files lists for jobs to run less jobs on some of the patches, together with QA team we did "integrated-networking" template to run only Neutron and Nova related scenario tests in the Neutron queues, we removed and consolidated some of the jobs (there is still one patch in progress for that but it should just remove around 2 jobs from the check queue). All of that are good improvements but still not enough to make our CI really stable :/ Because of all of that, I would like to ask community about any other ideas how we can improve that. If You have any ideas, please send it in this email thread or reach out to me directly on irc. We want to discuss about them in the next video CI meeting which will be on November 30th. If You would have any idea and would like to join that discussion, You are more than welcome in that meeting of course :) [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/ 025759.html -- Slawek Kaplonski Principal Software Engineer Red Hat

11 19

[ops]RabbitMQ High Availability
by DHilsbos＠performair.com 06 Dec '21

06 Dec '21

All; In the time I've been part of this mailing list, the subject of RabbitMQ high availability has come up several times, and each time specific recommendations for both Rabbit and Open Stack are provided. I remember it being an A or B kind of recommendation (i.e. configure Rabbit like A1, and Open Stack like A2, OR configure Rabbit like B1, and Open Stack like B2). Unfortunately, I can't find the previous threads on this topic. Does anyone have this information, that they would care to share with me? Thank you, Dominic L. Hilsbos, MBA Vice President - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

3 3

[kolla-ansible] Default masakari configuration should evacuate instances across nodes in wallaby?
by Rodrigo Lima 06 Dec '21

06 Dec '21

I'm working on upgrading an openstack farm from victoria to wallaby. After successful upgrade, I would like to enable hacluster and masakari to test HA between failing compute nodes. Everything seems to be running (pacemaker with the remote nodes OK, corosync without errors, masakari-monitors detects the 2 compute nodes online), but... when I simulate the failure of a node with shutdown, the failure and notification appears in the hostmonitor log, but the instances that were on the failed node don't evacuate, and I couldn't find documentation that explains how to do this specific configuration, if necessary. Does anyone have any ideas?

3 5

[dev][panko] deprecation doubts
by Soares Sarto, Ricardo 06 Dec '21

06 Dec '21

Hi Everyone Now that Panko has been deprecated, where are the events stored? What is the evolution strategy for OpenStack Telemetry? What is a current list of data generated by core openstack services (nova, neutron, keystone, glance, cinder, heat, etc.) to ceilometer ? (e.g. this link is from ocata … where is the current one ? https://docs.openstack.org/ocata/admin-guide/telemetry-data-collection.html ) Thank you!

1 0

OpenInfra Live - December 9, 2021 at 9am CT
by Ashlee Ferguson 06 Dec '21

06 Dec '21

Hi everyone, This week’s OpenInfra Live episode is brought to you by the OpenStack community. This new episode of the “Large Scale OpenStack” show will discuss operators' tricks and tools. In a live and direct discussion, our guests will reveal tricks and homegrown tools that they use in the trenches to keep their OpenStack clusters ticking like clockwork. Episode: Large Scale OpenStack: Operators’ tricks and tools Date and time: December 9, 2021 at 9am CT (1500 UTC) You can watch us live on: YouTube: https://www.youtube.com/watch?v=F_9KKAQE4fc LinkedIn: https://www.linkedin.com/feed/update/urn:li:ugcPost:6873686260419055616/ Facebook: https://www.facebook.com/104139126308032/posts/4596356560419577/ WeChat: recording will be posted on OpenStack WeChat after the live stream Speakers: Shatadru Bandyopadhyay (Workday) Thierry Carrez (OpenInfra Foundation) Thomas Goirand (Infomaniak) Axel Jacquet (Infomaniak) Gene Kuo (LINE) Belmiro Moreira (CERN) Arnaud Morin (OVHCloud) Adrien Pensart (OVHCloud) Have an idea for a future episode? Share it now at ideas.openinfra.live. Thanks! Ashlee Ashlee Ferguson Carlson Community & Events Open Infrastructure Foundation

1 0

[cinder] midcycle R-17 followup meeting thursday
by Brian Rosmaita 06 Dec '21

06 Dec '21

The poll results are in and our midcycle followup meeting will be held: DATE: Thursday, 9 December 2021 TIME: 1400-1430 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. The midcycle etherpad is here: https://etherpad.opendev.org/p/cinder-yoga-midcycles (Followup info starts at line 34, unless some joker has added a bunch of stuff at the top of the etherpad.) The primary topic is Gorka's proposal to revamp the quota system. There are links to the proposed spec and some POC patches on the etherpad. It's worth taking a look in advance so that we can have a short and productive meeting! cheers, brian

1 0

Re: [ops] [kolla] RabbitMQ High Availability
by Bogdan Dobrelya 06 Dec '21

06 Dec '21

> 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. 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

1 0

[cinder][OpenstackAnsible] Xena Cycle-Trailing Release Deadline
by Előd Illés 06 Dec '21

06 Dec '21

Hello teams with trailing projects, Next week is the Xena cycle-trailing release deadline [1], and all projects following the cycle-trailing release model must release their Xena deliverables by 16 December, 2021. The following trailing projects haven't been released yet for Xena: Cinder team's deliverables: - cinderlib OSA team's deliverables: - openstack-ansible-roles - openstack-ansible Patches were generated 2 weeks ago [2], feel free to update those if they are not up to date anymore. This is just a friendly reminder to allow you to release these projects in time. Do not hesitate to ping us if you have any questions or concerns. [1] https://releases.openstack.org/yoga/schedule.html#y-cycle-trail [2] https://review.opendev.org/q/topic:trailing-xena Előd Illés irc: elodilles

1 0

[neutron] Bug deputy report for week of November 29
by Lajos Katona 06 Dec '21

06 Dec '21

Hi Neutron Team I was bug deputy in neutron last week. Summary ========== 3 bugs need more attention, one is related to db upgrade (upgrade from Rocky to Stein), one bug is an issue between Nova and Neutron and related to network-vif-plug event, and one seems to be related to IPv6 Metadata. If you have time please check them and help solve them and check the reviews I linked. Needs attention ================ * "neutron-db-manage upgrade" is interrupted with error about neutron.portuplinkstatuspropagation ( https://bugs.launchpad.net/neutron/+bug/1952675 ) * VirtualInterfaceCreateException due to "Timeout waiting for [('network-vif-plugged'..." (https://bugs.launchpad.net/neutron/+bug/1944779 ) * DHCP agent fails to fully configure DHCP namespaces because of duplicate address detected (https://bugs.launchpad.net/neutron/+bug/1953165 ) ** Seems to be an issue with IPv6 metadata. Bugs with assignees =================== * Neurton linuxbridge agent does not create VXLAN interface ( https://bugs.launchpad.net/neutron/+bug/1952611 ) ** Fix proposed by mnaser to oslo.privsep: https://review.opendev.org/c/openstack/oslo.privsep/+/819996 * Segment updates may cause unnecessary overload ( https://bugs.launchpad.net/neutron/+bug/1952730 ) ** fix from rubasov: https://review.opendev.org/c/openstack/neutron/+/819777 * Cannot setup IPv6 overlay network in xena ( https://bugs.launchpad.net/neutron/+bug/1952897 ) ** https://review.opendev.org/c/openstack/neutron/+/820376 * Allow modification of max retries in OVSNeutronAgent ( https://bugs.launchpad.net/neutron/+bug/1952898 ) ** https://review.opendev.org/c/openstack/neutron/+/819816 * Gratuitous ARPs are not sent during master transition ( https://bugs.launchpad.net/neutron/+bug/1952907 ): ** Possible fix from Liu: https://review.opendev.org/c/openstack/neutron/+/712474 * On IPv6 overlay networks linuxbridge vxlans are created always on loopback device (https://bugs.launchpad.net/neutron/+bug/1953139 ): ** https://review.opendev.org/c/openstack/neutron/+/820484 RFEs ====== * [RFE] Unify quota engine API ( https://bugs.launchpad.net/neutron/+bug/1953170 ) ** We discussed the need for this rfe on last Friday's drivers meeting: https://meetings.opendev.org/meetings/neutron_drivers/2021/neutron_drivers.… Regards Lajos Katona (lajoskatona)

1 0

[kolla] Plan to deprecate binary and unify on single distrubition
by Michał Nasiadka 06 Dec '21

06 Dec '21

Hello Koalas, On the PTG we have discussed two topics: 1) Deprecate and drop binary type of Kolla images 2) Use a common base (single Linux distribution) for Kolla images This is a call for feedback - for people that have not been attending the PTG. What this essentially mean for consumers: 1) In Yoga cycle we will deprecate binary type of Kolla images, and in Z cycle those will be dropped. 2) We are not going to support CentOS Stream 9 (cs9) as a base operating system, and the source type build will rely on CentOS Stream 8 in Z release. 3) Beginning from A release Kolla will build only Debian source images - but Kolla-Ansible will still support deployment of those images on CentOS/Ubuntu/Debian Host operating systems (and Rocky Linux to be added in Yoga to that mix). Justification: The Kolla project team is limited in numbers, therefore supporting current broad mix of operating systems (especially with CentOS Stream 9 ,,on the way’’) is a significant maintenance burden. By dropping binary type of images - users would be running more tested images (since Kolla/Kolla-Ansible CI runs source images jobs as voting). In Xena we’ve already changed the default image type Kolla-Ansible uses to source. We also feel that using a unified base OS for Kolla container images is a way to remove some of the maintenance burden (including CI cycles and Request for feedback: If any of those changes is a no go from your perspective - we’d like to hear your opinions. Best regards, Michal Nasiadka

9 17

[TripleO] IPV6 Support
by Lokendra Rathour 03 Dec '21

03 Dec '21

Hi, I am trying to install the undercloud using the ipv6 address on Centos 8 using Train release. It is seen that the deployment of undercloud is getting failed with error as mentioned below. Same deployment is working in the normal ipv4 case. So Questions: 1. is IPV6 supported in TripleO , if yes then please suggest how. Error: nied", " attempt(s): 2", "2021-11-25 07:25:31,535 WARNING: 65355 -- Retrying running container: zaqar", "2021-11-25 07:25:34,887 ERROR: 65355 -- ['/usr/bin/podman', 'run', '--user', '0', '--name', 'container-puppet-zaqar', '--env', 'PUPPET_TAGS=file,file_line,concat,augeas,cron,zaqar_config', '--env', 'NAME=zaqar', '--env', 'HOSTNAME=undercloud', '--env', 'NO_ARCHIVE=', '--env', 'STEP=6', '--env', 'NET_HOST=true', '--env', 'DEBUG=False', '--volume', '/etc/localtime:/etc/localtime:ro', '--volume', '/tmp/tmp06nvxzzz:/etc/config.pp:ro', '--volume', '/etc/puppet/:/tmp/puppet-etc/:ro', '--volume', '/etc/pki/ca-trust/extracted:/etc/pki/ca-trust/extracted:ro', '--volume', '/etc/pki/tls/certs/ca-bundle.crt:/etc/pki/tls/certs/ca-bundle.crt:ro', '--volume', '/etc/pki/tls/certs/ca-bundle.trust.crt:/etc/pki/tls/certs/ca-bundle.trust.crt:ro', '--volume', '/etc/pki/tls/cert.pem:/etc/pki/tls/cert.pem:ro', '--volume', '/var/lib/config-data:/var/lib/config-data/:rw', '--volume', '/var/lib/container-puppet/puppetlabs/facter.conf:/etc/puppetlabs/facter/facter.conf:ro', '--volume', '/var/lib/container-puppet/puppetlabs/:/opt/puppetlabs/:ro', '--volume', '/dev/log:/dev/log:rw', '--rm', '--log-driver', 'k8s-file', '--log-opt', 'path=/var/log/containers/stdouts/container-puppet-zaqar.log', '--security-opt', 'label=disable', '--volume', '/usr/share/openstack-puppet/modules/:/usr/share/openstack-puppet/modules/:ro', '--entrypoint', '/var/lib/container-puppet/container-puppet.sh', '--net', 'host', '--volume', '/etc/hosts:/etc/hosts:ro', '--volume', '/var/lib/container-puppet/container-puppet.sh:/var/lib/container-puppet/container-puppet.sh:ro', 'undercloud.ctlplane.localdomain:8787/tripleotraincentos8/centos-binary-zaqar-wsgi:current-tripleo'] run failed after Error: container_linux.go:370: starting container process caused: error adding seccomp filter rule for syscall bdflush: permission denied: OCI permission denied", " attempt(s): 3", "2021-11-25 07:25:34,888 WARNING: 65355 -- Retrying running container: zaqar", "2021-11-25 07:25:34,888 ERROR: 65355 -- Failed running container for zaqar", "2021-11-25 07:25:34,888 INFO: 65355 -- Finished processing puppet configs for zaqar", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring crond", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring glance_api", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring heat_api", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring heat", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring ironic_api", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring ironic", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring ironic_inspector", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring neutron", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring iscsid", "2021-11-25 07:25:34,889 ERROR: 65345 -- ERROR configuring keystone", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring memcached", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring mistral", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring mysql", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring nova", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring rabbitmq", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring placement", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring swift", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring swift_ringbuilder", "2021-11-25 07:25:34,890 ERROR: 65345 -- ERROR configuring zaqar" ], "stderr_lines": [], "_ansible_no_log": false, "attempts": 15 } ] ] Not cleaning working directory /home/stack/tripleo-heat-installer-templates Not cleaning ansible directory /home/stack/undercloud-ansible-mw4crw92 Install artifact is located at /home/stack/undercloud-install-20211125072536.tar.bzip2 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Deployment Failed! ERROR: Heat log files: /var/log/heat-launcher/undercloud_deploy-o_qf1b4w !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Deployment failed. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1345, in _standalone_deploy raise exceptions.DeploymentError('Deployment failed') tripleoclient.exceptions.DeploymentError: Deployment failed During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1363, in _standalone_deploy raise exceptions.DeploymentError(six.text_type(e)) tripleoclient.exceptions.DeploymentError: Deployment failed During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/cliff/app.py", line 401, in run_subcommand result = cmd.run(parsed_args) File "/usr/lib/python3.6/site-packages/cliff/command.py", line 185, in run return_code = self.take_action(parsed_args) or 0 File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1451, in take_action if self._standalone_deploy(parsed_args) != 0: File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1400, in _standalone_deploy raise exceptions.DeploymentError('Deployment failed.') tripleoclient.exceptions.DeploymentError: Deployment failed. clean_up Deploy: Deployment failed. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1345, in _standalone_deploy raise exceptions.DeploymentError('Deployment failed') tripleoclient.exceptions.DeploymentError: Deployment failed During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1363, in _standalone_deploy raise exceptions.DeploymentError(six.text_type(e)) tripleoclient.exceptions.DeploymentError: Deployment failed During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/osc_lib/shell.py", line 136, in run ret_val = super(OpenStackShell, self).run(argv) File "/usr/lib/python3.6/site-packages/cliff/app.py", line 281, in run result = self.run_subcommand(remainder) File "/usr/lib/python3.6/site-packages/osc_lib/shell.py", line 176, in run_subcommand ret_value = super(OpenStackShell, self).run_subcommand(argv) File "/usr/lib/python3.6/site-packages/cliff/app.py", line 401, in run_subcommand result = cmd.run(parsed_args) File "/usr/lib/python3.6/site-packages/cliff/command.py", line 185, in run return_code = self.take_action(parsed_args) or 0 File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1451, in take_action if self._standalone_deploy(parsed_args) != 0: File "/usr/lib/python3.6/site-packages/tripleoclient/v1/tripleo_deploy.py", line 1400, in _standalone_deploy raise exceptions.DeploymentError('Deployment failed.') tripleoclient.exceptions.DeploymentError: Deployment failed. END return value: 1 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! An error has occured while deploying the Undercloud. See the previous output for details about what went wrong. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Command '['sudo', '--preserve-env', 'openstack', 'tripleo', 'deploy', '--standalone', '--standalone-role', 'Undercloud', '--stack', 'undercloud', '--local-domain=localdomain', '--local-ip=abce:abce:abce::1/64', '--templates=/usr/share/openstack-tripleo-heat-templates/', '--networks-file=network_data_undercloud.yaml', '--heat-native', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/undercloud.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/use-dns-for-vips.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/podman.yaml', '-e', '/home/stack/containers-prepare-parameter.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/ironic.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/mistral.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/zaqar-swift-backend.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/disable-telemetry.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/tempest.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/ssl/no-tls-endpoints-public-ip.yaml', '--deployment-user', 'stack', '--output-dir=/home/stack', '-e', '/home/stack/tripleo-config-generated-env-files/undercloud_parameters.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/tripleo-validations.yaml', '--debug', '--log-file=install-undercloud.log', '-e', '/usr/share/openstack-tripleo-heat-templates/undercloud-stack-vstate-dropin.yaml']' returned non-zero exit status 1. Command '['sudo', '--preserve-env', 'openstack', 'tripleo', 'deploy', '--standalone', '--standalone-role', 'Undercloud', '--stack', 'undercloud', '--local-domain=localdomain', '--local-ip=abce:abce:abce::1/64', '--templates=/usr/share/openstack-tripleo-heat-templates/', '--networks-file=network_data_undercloud.yaml', '--heat-native', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/undercloud.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/use-dns-for-vips.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/podman.yaml', '-e', '/home/stack/containers-prepare-parameter.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/ironic.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/mistral.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/zaqar-swift-backend.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/disable-telemetry.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/services/tempest.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/ssl/no-tls-endpoints-public-ip.yaml', '--deployment-user', 'stack', '--output-dir=/home/stack', '-e', '/home/stack/tripleo-config-generated-env-files/undercloud_parameters.yaml', '-e', '/usr/share/openstack-tripleo-heat-templates/environments/tripleo-validations.yaml', '--debug', '--log-file=install-undercloud.log', '-e', '/usr/share/openstack-tripleo-heat-templates/undercloud-stack-vstate-dropin.yaml']' returned non-zero exit status 1. END return value: 1 [stack@undercloud ~]$

2 5

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

03 Dec '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @ - Recording: https://www.youtube.com/watch?v=PwGYse8j4UY - Topic Info logs: https://meetings.opendev.org/meetings/tc/2021/tc.2021-12-02-15.02.log.html * Next week's meeting is on IRC on 9th Dec, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 8th Dec. 2. What we completed this week: ========================= * Goal proposal for RBAC is merged and the next step is to select it[2] * Add ansible-collection-kolla repo to Kolla project[3] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[4]. Open Reviews ----------------- * 9 open reviews for ongoing activities[5]. TC position on release cadence ------------------------------------- You might have seen the ML thread on the release cadence[6]. We discussed it in this week's TC meeting so that we can provide the TC stand on this. There are mixed amounts of opinions on the different proposals like doing 1-year release, no coordinated release, more releases, mixed LTS release and keeping it same which is 6-month release etc. One of the key things we discussed is how to improve the upgrade process which is one of the key points to revise the current release model. Dan made a good proposal on grenade testing the 'n-1' -> 'n' (current) and 'n-2' -> 'n' (new) so that we make sure 'n' release is upgrade-able from 'n-1' as well as 'n-2' release. For that, we need to think about the deprecation phase to be n+2 release then n+1. Along with that, we can add/improve our upgrade documentation. These are a few ideas we discussed but due to time constraints, we have not concluded yet. We will set up a separate call to continue the discussion sometime in Jan start(after the Christmas holidays) Yoga testing runtime ------------------------- We have an agreement now on Yoga testing runtime and keeping python3.6 support in Yoga, you can see the details in this ML[7] Fixing Zuul config error -------------------------- If your project is listed in zuul config error, please start planning to fix those[8] RBAC discussion: continuing from PTG ---------------------------------------------- The goal proposal is not merged and the next step is to select this goal which is in progress[8] with a good amount of positive votes and no objection yet. Community-wide goal updates ------------------------------------ * Proposed goals: ** RBAC goal is pretty much in good shape now, feel free to review it[9] * Under review: ** FIPS compatibility and compliance [10]. Adjutant need maintainers and PTLs ------------------------------------------- We are waiting to hear from Braden, Albert on permission to work on this project[11]. New project 'Skyline' proposal ------------------------------------ * TC is still waiting for skyline team to respond to open queries[12]. TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[13]. Project updates ------------------- * Add NVidia vGPU plugin charm to OpenStack charms[14] * Retire js-openstack-lib [15] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[16]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [17] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/815158 [3] https://review.opendev.org/c/openstack/governance/+/819331 [4] https://etherpad.opendev.org/p/tc-yoga-tracker [5] https://review.opendev.org/q/projects:openstack/governance+status:open [6] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025684… [7] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026164… [8] https://etherpad.opendev.org/p/zuul-config-error-openstack [9] https://review.opendev.org/c/openstack/governance/+/818817 [10] https://review.opendev.org/c/openstack/governance/+/816587 [11] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [12] https://review.opendev.org/c/openstack/governance/+/814037 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [14] https://review.opendev.org/c/openstack/governance/+/819856 [15] https://review.opendev.org/c/openstack/governance/+/807163 [16] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [17] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[release] Release countdown for week R-16, Dec 06-10
by Előd Illés 03 Dec '21

03 Dec '21

Development Focus ---------------------------- The Yoga-2 milestone will happen in next month, on 06 January, 2022. Yoga-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org <https://releases.openstack.org/yoga/schedule.html>/yoga <https://releases.openstack.org/yoga/schedule.html>/schedule.html <https://releases.openstack.org/yoga/schedule.html>for details. General Information ---------------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/ <https://opendev.org/openstack/releases/src/branch/master/deliverables/yoga>yoga <https://opendev.org/openstack/releases/src/branch/master/deliverables/yoga> You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/ <https://releases.openstack.org/yoga/schedule.html#y-mf>yoga <https://releases.openstack.org/yoga/schedule.html#y-mf>/schedule.html# <https://releases.openstack.org/yoga/schedule.html#y-mf>y <https://releases.openstack.org/yoga/schedule.html#y-mf>-mf <https://releases.openstack.org/yoga/schedule.html#y-mf> Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates ----------------------------------------- Yoga-2 Milestone:06 January, 2022 Előd Illés irc: elodilles

1 0

[ironic][meeting] Postpone meeting time until end of March 2022
by Riccardo Pittau 03 Dec '21

03 Dec '21

Hello ironicers! Due to some overlapping time with other meetings that cause me to attend to 2 (or sometimes 3.....) meetings at the same time, I'd like to propose to move the time for the weekly ironic upstream meeting 1 hour later, so from the current 15:00-16:00 UTC to 16:00-17:00 UTC, until the next Daylight saving time change that should happen at the end of March 2022. Thank you! Ciao, Riccardo

4 5

[neutron] Drivers meeting agenda - 03.12.2021
by Lajos Katona 03 Dec '21

03 Dec '21

Hi Neutron Drivers, The agenda for tomorrow's drivers meeting is at [1]. I would like to discuss one bug which I feel is more an RFE: * https://bugs.launchpad.net/neutron/+bug/1952867 : [ml2][ovs] allow multiple physical networks map to one physical ovs bridge As physnet-bridge mapping is deep in Neutron I feel that a discussion is necessary to have a common understanding of the possible benefits and pitfalls of such shange. I wrote to Liu to ask him to join, but I'm not sure if he can participate. We have one more "On Demand" topic from Rodolfo: * https://review.opendev.org/c/openstack/python-openstackclient/+/819627/1: To deprecate "force" behaviour in OSC "quota" commands. This is currently the default behaviour in Neutron; what is proposed in this patch is to move Neutron to, by default, check the quota limits and use "--force" parameter to commit the quota limits without any check. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda See you at the meeting tomorrow. Lajos Katona (lajoskatona)

1 1

[kolla[ Issue running masakari-hostmonitor
by Chris DiLorenzo 02 Dec '21

02 Dec '21

Hello, I am running Kolla-12.0.0 with Openstack Victoria. I have mostly successfully deployed masakari. The instance monitoring works, I can set up segments in Horizon and via CLI. But I can't get masakari-hostmonitor to start: 2021-12-02 16:50:44.999 7 INFO oslo.privsep.daemon [-] Running privsep helper: ['sudo', 'privsep-helper', '--config-file', '/etc/masakari-monitors/masakari -monitors.conf', '--privsep_context', 'masakarimonitors.privsep.monitors_priv', '--privsep_sock_path', '/tmp/tmpf_65hc7m/privsep.sock'] 2021-12-02 16:50:44.892 261 INFO oslo.privsep.daemon [-] privsep daemon starting 2021-12-02 16:50:44.898 261 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0 2021-12-02 16:50:44.902 261 ERROR oslo.privsep.daemon [-] [Errno 1] Operation not permitted Traceback (most recent call last): File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 593, in helper_main Daemon(channel, context).run() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 403, in run self._drop_privs() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 439, in _drop_privs capabilities.drop_all_caps_except(self.caps, self.caps, []) File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/capabilities.py", line 156, in drop_all_caps_except raise OSError(errno, os.strerror(errno)) PermissionError: [Errno 1] Operation not permitted 2021-12-02 16:50:45.001 7 DEBUG oslo_privsep.comm [-] EOF on privsep read channel _reader_main /var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep /comm.py:149 2021-12-02 16:50:45.475 7 WARNING oslo.privsep.daemon [-] privsep log: [Errno 1] Operation not permitted 2021-12-02 16:50:45.565 7 INFO oslo.privsep.daemon [-] Spawned new privsep daemon via rootwrap 2021-12-02 16:50:45.565 7 DEBUG oslo.privsep.daemon [-] Accepted privsep connection to /tmp/tmpf_65hc7m/privsep.sock __init__ /var/lib/kolla/venv/lib/pytho n3.8/site-packages/oslo_privsep/daemon.py:371 2021-12-02 16:50:45.467 267 INFO oslo.privsep.daemon [-] privsep daemon starting 2021-12-02 16:50:45.471 267 INFO oslo.privsep.daemon [-] privsep process running with uid/gid: 0/0 2021-12-02 16:50:45.474 267 ERROR oslo.privsep.daemon [-] [Errno 1] Operation not permitted Traceback (most recent call last): File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 593, in helper_main Daemon(channel, context).run() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 403, in run self._drop_privs() File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/daemon.py", line 439, in _drop_privs capabilities.drop_all_caps_except(self.caps, self.caps, []) File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_privsep/capabilities.py", line 156, in drop_all_caps_except raise OSError(errno, os.strerror(errno)) PermissionError: [Errno 1] Operation not permitted sudoers in the container appears to be set up correctly. Thanks Chris

2 3

python_requires >= 3.8 during Yoga
by Stephen Finucane 02 Dec '21

02 Dec '21

gmann has been helpfully proposing patches to change the versions of Python we're testing against in Yoga. I've suggested that we might want to bump 'python_requires' in 'setup.cfg' to indicate that we no longer support any version of Python before 3.8 [1]. As gmann has noted, doing so would mean nova would no longer be installable on Python 3.6 or 3.7 and there has been a small bit of back and forth on the pros and cons of this. I'm wondering what other people's thoughts on this are. Is this something we should be doing? Should we do it for libraries too or just services? Do we ever want to do this? Thoughts, please! Stephen [1] https://review.opendev.org/c/openstack/nova/+/819194/comment/72ecf24f_2bd29…

17 61

[cyborg] Cancel IRC meeting
by Brin Zhang(张百林) 02 Dec '21

02 Dec '21

Hi all, Due to the conflict between the team members and the IRC meeting time, the IRC meeting of this week will be cancelled. If you have any questions, please feel free to ping us through ML or #openstack-cyborg channel. Thanks. brinzhang Inspur Electronic Information Industry Co.,Ltd.

1 0

[cinder] R-17 midcycle followup meeting poll
by Brian Rosmaita 02 Dec '21

02 Dec '21

We had some very useful discussions at yesterday's midcycle but ran out of time before we could discuss Gorka's new quotas proposals. It turns out that due to 8 December being a public holiday in many locations, the next Cinder meeting won't work for a video followup, so we'll hold a special half-hour video meeting on this topic next week. The meeting will be 1400-1430 UTC on one of Tuesday, Thursday, or Friday. If you have a preference, please express it in this poll: https://doodle.com/poll/mnddwtp99uu6hsuq The poll closes at 1300 UTC on Monday 6 December, and I'll announce the selected time shortly thereafter. cheers, brian

1 0

Windows imaging process
by Gaël THEROND 02 Dec '21

02 Dec '21

Hi everyone, On one of our Openstack platforms, we maintain windows based workloads. We currently have the following build process: 1°/- We download windows ISO image. 2°/- Use hyper-v to create a gold image that bring virtio drivers. 3°/- We upload this image on glance and publish it for our users. 4°/- Our users use packer to create their own windows custom image from our gold image. This workflow works pretty fine, it’s simple enough and as Microsoft isn’t releasing a new major Windows every two months it’s pretty ok not having all the steps automated until now. However, I’m wondering if there is a way to automate my first two steps using Openstack? So far, from my early tests, I didn’t managed to get all of appropriate gears to work together, did I missed something? I need to create a VM that at least can use the Windows ISO plus a virtio ISO as a second cdrom device and an additional user-data payload that will instruct the Windows installer to go automatically through the installation steps plus loads missing drivers from the virtio iso. This is perfectly working on a native kvm as you can add multiple cdrom device but I didn’t find a way to replicate that on Openstack. Starting from an unaltered Microsoft originated ISO image is a mandatory requirement for this project (Because of security constraints that I can’t have any impact on). Help from anyone that already had to deal with such situation would be very appreciated ! Thanks!

2 3

[kuryr] Propose to EOL stable branches (Stein, Rocky and Queens) for all the kuryr scope
by Maysa De Macedo Souza 02 Dec '21

02 Dec '21

Hello, We have plenty of stable branches in Kuryr repositories still open with the oldest being stable/queens. We haven't seen many backports[0] proposed to Stein, Rocky and Queens, so I would like to propose retiring these branches. Let me know if anybody is interested in keeping any of those branches. [0] https://review.opendev.org/q/(project:%255Eopenstack/kuryr.*)AND((branch:st… Thank you, Maysa Macedo.

2 3

[all][tc] Technical Committee next weekly meeting on Dec 2nd at 1500 UTC
by Ghanshyam Mann 01 Dec '21

01 Dec '21

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

1 1

[ceilometer][octavia][Victoria] No metrics from octavia loadbalancer
by Iain Stott 01 Dec '21

01 Dec '21

Has anyone had any progress on this? We are currently in the same situation, we can see if loadblancers exists, but unable to see a way to configure the polling agent to poll endpoints like v2/lbaas/loadbalancers/[ID]/stats Cheers, Iain > OK. I have some progress. I created meters.d and pollster.d (in pollsters.d I’ve created octavia.yaml with sample type gauge and unit load balancer) and now I can see some measures, but only if load balancer exists or not. > Is there any way to force dynamic pollster to ask for url v2/lbaas/loadbalancers/[ID]/stats? > Best regards > Adam Iain Stott OpenStack Engineer The Hut Group<http://www.thehutgroup.com/> Tel: Email: Iain.Stott(a)thehutgroup.com<mailto:Iain.Stott@thehutgroup.com> For the purposes of this email, the "company" means The Hut Group Limited, a company registered in England and Wales (company number 6539496) whose registered office is at Fifth Floor, Voyager House, Chicago Avenue, Manchester Airport, M90 3DQ and/or any of its respective subsidiaries. Confidentiality Notice This e-mail is confidential and intended for the use of the named recipient only. If you are not the intended recipient please notify us by telephone immediately on +44(0)1606 811888 or return it to us by e-mail. Please then delete it from your system and note that any use, dissemination, forwarding, printing or copying is strictly prohibited. Any views or opinions are solely those of the author and do not necessarily represent those of the company. Encryptions and Viruses Please note that this e-mail and any attachments have not been encrypted. They may therefore be liable to be compromised. Please also note that it is your responsibility to scan this e-mail and any attachments for viruses. We do not, to the extent permitted by law, accept any liability (whether in contract, negligence or otherwise) for any virus infection and/or external compromise of security and/or confidentiality in relation to transmissions sent by e-mail. Monitoring Activity and use of the company's systems is monitored to secure its effective use and operation and for other lawful business purposes. Communications using these systems will also be monitored and may be recorded to secure effective use and operation and for other lawful business purposes. hgvyjuv

2 1

[RDO][Meeting] December Meeting Hiatus (12/22 and 12/29)
by Amy Marrich 01 Dec '21

01 Dec '21

In today's RDO meeting we decided to cancel the meetings which would have been held on 12/22 and 12/29. We will still be holding meetings the other weeks in December in the #RDO channel on OFTC and hope to see you there. Thanks, Amy (spotz)

1 0

[cinder] : SAN migration
by Gauurav Sabharwal1 01 Dec '21

01 Dec '21

Hi Experts , I need some expert advise of one of the scenario, I have multiple isolated OpenStack cluster running with train & rocky edition. Each OpenStack cluster environment have it's own isolated infrastructure of SAN ( CISCO fabric ) & Storage ( HP, EMC & IBM). Now company planning to refresh their SAN infrastructure. By procuring new Brocade SAN switches. But there are some migration relevant challenges we have. As we understand under one cinder instance only one typer of FC zone manager is supported . Currently customer configured & managing CISCO . Is it possible to configure two different vendor FC Zone manager under one cinder instance. Migration of SAN zoning is supposedly going to be happen offline way from OpenStack point of view. We will be migrating all ports of each existing cisco fabric to Brocade with zone configuration using brocade CLI. Our main concern is that after migration How CINDER DB update new zone info & path via Brocade SAN. Regards Gauurav Sabharwal IBM India Pvt. Ltd. IBM towers Ground floor, Block -A , Plot number 26, Sector 62, Noida Gautam budhnagar UP-201307. Email:gauurav.sabharwal@in.ibm.com Mobile No.: +91-9910159277

3 3

[cinder] reminder: yoga R-17 midcycle today at 1400 utc
by Brian Rosmaita 01 Dec '21

01 Dec '21

he Cinder Yoga R-17 virtual midcycle will be held: DATE: Today, Wednesday 1 December 2021 TIME: 1400-1600 UTC LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. The midcycle etherpad is here: https://etherpad.opendev.org/p/cinder-yoga-midcycles cheers, brian

1 0

[neutron][networking][ipv6][dns][ddi] Upcoming OpenInfra Edge Computing Group sessions
by Ildiko Vancsa 30 Nov '21

30 Nov '21

Hi, I’m reaching out to you to draw your attention to the amazing lineup of discussion topics for the OpenInfra Edge Computing Group weekly calls up until the end of this year with industry experts to present and participate in the discussions! I would like to invite and encourage you to join the working group sessions to discuss edge related challenges and solutions in the below areas and more! Some of the sessions to highlight will be continuing the discussions we started at the recent PTG: * November 29th - Networking and DNS discussion with Cricket Liu and Andrew Wertkin * December 6th - Networking and IPv6 discussion with Ed Horley Beyond the above topics we will have presentations from groups and projects such as Smart Edge and the Industry IoT Consortium (Formerly Industrial Internet Consortium). For the full schedule please see the edge WG’s wiki: https://wiki.openstack.org/wiki/Edge_Computing_Group#Upcoming_Topics Our calls happen every Monday at 6am Pacific Time / 1400 UTC on Zoom. You can find all the meeting details here: https://wiki.openstack.org/wiki/Edge_Computing_Group#Meetings Please let me know if you have any questions about the working group or any of the upcoming sessions. Thanks and Best Regards, Ildikó

1 3

[Neutron][OVN] nova-compute timeout while waiting for VIF activation confirmed by Neutron
by Tony Liu 30 Nov '21

30 Nov '21

Hi, I see such problem from time to time. It's not consistently reproduceable. ====================== 2021-11-23 22:16:28.532 7 INFO nova.compute.manager [req-50817b01-e7ae-4991-94fe-e4c5672c481b - - - - -] [instance: 7021bf37-348d-4dfa-b0c5-6a251fceb6cd] During sync_power_state the instance has a pending task (spawning). Skip. 2021-11-23 22:21:28.342 7 WARNING nova.virt.libvirt.driver [req-814c98a4-3fd9-4607-9abb-5fbe5cef8650 3a4c320d64664d9cb6784b7ea52d618a 21384fe21ebb4339b1a5f2a8f9000ea3 - default default] [instance: 7021bf37-348d-4dfa-b0c5-6a251fceb6cd] Timeout waiting for [('network-vif-plugged', '735d97a3-db7c-42ed-b3be-1596d4cc7f4b')] for instance with vm_state building and task_state spawning.: eventlet.timeout.Timeout: 300 seconds ====================== The VIF/port is activated by OVN ovn-controller to ovn-sb. It seems that, either Neutron didn't capture the update or didn't send message back to nova-compute. Is there any known fix for this problem? Thanks! Tony

5 9

[neutron][nova-compute] Received unexpected event network-vif-plugged-<uuid>
by Tony Liu 30 Nov '21

30 Nov '21

Hi, With Ussuri, when launch VM, I see this from nova-compute. ======== Received unexpected event network-vif-plugged-32b7af8a-ef81-4785-bd79-3a5619823638 ======== That caused VM to be destroyed, rescheduled and relaunched. And that recreation worked fine. >From user POV, it just takes a bit longer to launch the VM. What's the event nova-compute expects from Neutron for vif-plug? Any hints where I can look into it? More logs here. ======== 2021-11-29 18:28:10.064 7 INFO os_vif [req-2a89f605-6972-41dc-83f1-1ef6a444e486 b8de8d37a30147fd98681c22fc515874 b5938e7ebb0645e396b19e99bb7f9868 - default default] Successfully plugged vif VIFOpenVSwitch(active=False,address=fa:16:3e:f1:94:a0,bridge_name='br-int',has_traffic_filtering=True,id=32b7af8a-ef81-4785-bd79-3a5619823638,network=Network(27ea27c6-3d1e-4d37-ad4a-de2ae1578f1e),plugin='ovs',port_profile=VIFPortProfileOpenVSwitch,preserve_on_delete=False,vif_name='tap32b7af8a-ef') 2021-11-29 18:28:10.515 7 INFO nova.compute.manager [req-01cbb5ac-d453-4484-9384-1a2173b532a9 - - - - -] [instance: a8eb2a2a-8c83-46b2-bfd4-fd3a7d00f2ce] VM Started (Lifecycle Event) 2021-11-29 18:28:10.544 7 INFO nova.compute.manager [req-01cbb5ac-d453-4484-9384 -1a2173b532a9 - - - - -] [instance: a8eb2a2a-8c83-46b2-bfd4-fd3a7d00f2ce] VM Paused (Lifecycle Event) 2021-11-29 18:28:10.604 7 INFO nova.compute.manager [req-01cbb5ac-d453-4484-9384 -1a2173b532a9 - - - - -] [instance: a8eb2a2a-8c83-46b2-bfd4-fd3a7d00f2ce] During sync_power_state the instance has a pending task (spawning). Skip. 2021-11-29 18:28:25.441 7 INFO nova.compute.manager [req-01cbb5ac-d453-4484-9384 -1a2173b532a9 - - - - -] [instance: a8eb2a2a-8c83-46b2-bfd4-fd3a7d00f2ce] VM Res umed (Lifecycle Event) 2021-11-29 18:28:25.445 7 INFO nova.virt.libvirt.driver [-] [instance: a8eb2a2a- 8c83-46b2-bfd4-fd3a7d00f2ce] Instance spawned successfully. 2021-11-29 18:28:25.445 7 INFO nova.compute.manager [req-2a89f605-6972-41dc-83f1-1ef6a444e486 b8de8d37a30147fd98681c22fc515874 b5938e7ebb0645e396b19e99bb7f9868 - default default] [instance: a8eb2a2a-8c83-46b2-bfd4-fd3a7d00f2ce] Took 18.75 seconds to spawn the instance on the hypervisor. 2021-11-29 18:28:25.502 7 INFO nova.compute.manager [req-01cbb5ac-d453-4484-9384-1a2173b532a9 - - - - -] [instance: a8eb2a2a-8c83-46b2-bfd4-fd3a7d00f2ce] During sync_power_state the instance has a pending task (spawning). Skip. 2021-11-29 18:28:25.514 7 INFO nova.compute.manager [req-2a89f605-6972-41dc-83f1-1ef6a444e486 b8de8d37a30147fd98681c22fc515874 b5938e7ebb0645e396b19e99bb7f9868 - default default] [instance: a8eb2a2a-8c83-46b2-bfd4-fd3a7d00f2ce] Took 19.46 seconds to build instance. 2021-11-29 18:28:27.466 7 WARNING nova.compute.manager [req-82314965-fe71-4993-bbf6-f0aa9e708529 f0c1375066214e24ab7942d72d829097 3ec2940fc10d4e57bcf929d1fe678c79 - default default] [instance: a8eb2a2a-8c83-46b2-bfd4-fd3a7d00f2ce] Received unexpected event network-vif-plugged-32b7af8a-ef81-4785-bd79-3a5619823638 for instance with vm_state active and task_state None. 2021-11-29 18:28:55.829 7 INFO nova.compute.manager [req-e36e4a81-4755-4d7f-9ee4-d43d00629765 b8de8d37a30147fd98681c22fc515874 b5938e7ebb0645e396b19e99bb7f9868 - default default] [instance: a8eb2a2a-8c83-46b2-bfd4-fd3a7d00f2ce] Terminating instance ======== Thanks! Tony

2 1

[neutron] CI meeting 30.11.2021 - cancelled
by Slawek Kaplonski 29 Nov '21

29 Nov '21

Hi, Due to some personal reasons I will not be able to drive today's Neutron CI meeting. Let's cancel it this week. Remember, next week we will have CI meeting on Jitsi and we will discuss all ideas about how to improve stability of our CI. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[Neutron][OVN] AttributeError: 'NoneType' object has no attribute 'get_lrouter'
by Tony Liu 29 Nov '21

29 Nov '21

Hi, It happens from time to time, not consistently, with the latest kolla/centos-binary-neutron-server:ussuri container image. >From the bottome of traceback, it seems self._ovn is None. Any clues how this can happen? I don't see other suspicious logging in Neutron and OVN. ===================== File "/usr/lib/python3.6/site-packages/neutron/services/ovn_l3/plugin.py", line 477, in get_router_availability_zones ERROR neutron.api.v2.resource lr = self._ovn.get_lrouter(router['id']) ERROR neutron.api.v2.resource AttributeError: 'NoneType' object has no attribute 'get_lrouter' ===================== Here is the full traceback. ===================== neutron.api.v2.resource [req-bf2230aa-0491-4caa-b5f7-169d37009672 b8de8d37a30147fd98681c22fc515874 b5938e7ebb0645e396b19e99bb7f9868 - default default] index failed: No details.: AttributeError: 'NoneType' object has no attribute 'get_lrouter' neutron.api.v2.resource Traceback (most recent call last): neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron/api/v2/resource.py", line 98, in resource neutron.api.v2.resource result = method(request=request, **args) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/api.py", line 139, in wrapped neutron.api.v2.resource setattr(e, '_RETRY_EXCEEDED', True) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ neutron.api.v2.resource self.force_reraise() neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise neutron.api.v2.resource raise value neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/api.py", line 135, in wrapped neutron.api.v2.resource return f(*args, **kwargs) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_db/api.py", line 154, in wrapper neutron.api.v2.resource ectxt.value = e.inner_exc neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ neutron.api.v2.resource self.force_reraise() neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise neutron.api.v2.resource raise value neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_db/api.py", line 142, in wrapper neutron.api.v2.resource return f(*args, **kwargs) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/api.py", line 183, in wrapped neutron.api.v2.resource LOG.debug("Retry wrapper got retriable exception: %s", e) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ neutron.api.v2.resource self.force_reraise() neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise neutron.api.v2.resource raise value neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/api.py", line 179, in wrapped neutron.api.v2.resource return f(*dup_args, **dup_kwargs) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron/api/v2/base.py", line 369, in index neutron.api.v2.resource return self._items(request, True, parent_id) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron/api/v2/base.py", line 304, in _items neutron.api.v2.resource obj_list = obj_getter(request.context, **kwargs) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/api.py", line 233, in wrapped neutron.api.v2.resource return method(*args, **kwargs) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/api.py", line 139, in wrapped neutron.api.v2.resource setattr(e, '_RETRY_EXCEEDED', True) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ neutron.api.v2.resource self.force_reraise() neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise neutron.api.v2.resource raise value neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/api.py", line 135, in wrapped neutron.api.v2.resource return f(*args, **kwargs) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_db/api.py", line 154, in wrapper neutron.api.v2.resource ectxt.value = e.inner_exc neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ neutron.api.v2.resource self.force_reraise() neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise neutron.api.v2.resource raise value neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_db/api.py", line 142, in wrapper neutron.api.v2.resource return f(*args, **kwargs) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/api.py", line 183, in wrapped neutron.api.v2.resource LOG.debug("Retry wrapper got retriable exception: %s", e) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 220, in __exit__ neutron.api.v2.resource self.force_reraise() neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 196, in force_reraise neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/six.py", line 703, in reraise neutron.api.v2.resource raise value neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/api.py", line 179, in wrapped neutron.api.v2.resource return f(*dup_args, **dup_kwargs) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron/db/l3_db.py", line 547, in get_routers neutron.api.v2.resource page_reverse=page_reverse) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/model_query.py", line 317, in get_collection neutron.api.v2.resource for c in query neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/model_query.py", line 317, in <listcomp> neutron.api.v2.resource for c in query neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron/db/l3_db.py", line 221, in _make_router_dict neutron.api.v2.resource resource_extend.apply_funcs(l3_apidef.ROUTERS, res, router) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron_lib/db/resource_extend.py", line 84, in apply_funcs neutron.api.v2.resource resolved_func(response, db_object) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron/db/availability_zone/router.py", line 40, in _add_az_to_response neutron.api.v2.resource l3_plugin.get_router_availability_zones(router_db)) neutron.api.v2.resource File "/usr/lib/python3.6/site-packages/neutron/services/ovn_l3/plugin.py", line 477, in get_router_availability_zones neutron.api.v2.resource lr = self._ovn.get_lrouter(router['id']) neutron.api.v2.resource AttributeError: 'NoneType' object has no attribute 'get_lrouter' neutron.api.v2.resource neutron.wsgi [req-bf2230aa-0491-4caa-b5f7-169d37009672 b8de8d37a30147fd98681c22fc515874 b5938e7ebb0645e396b19e99bb7f9868 - default default] 10.91.1.7,10.250.20.26 "GET /v2.0/routers HTTP/1.1" status: 500 len: 344 time: 0.2660162 ===================== Thanks! Tony

1 0

RE: Nova Local Disk Storage (Seena Fallah)
by Steven Relf 29 Nov '21

29 Nov '21

Hi Seena, Do you mean passing an entire disk to an instance, or moving where nova stores its ephemeral disks? (e.g. /var/lib/nova/instances?) Rgds Steve. The future has already arrived. It's just not evenly distributed yet - William Gibson Hi, Is there any support for creating instances on a whole separate disk, not an LVM?

1 0

[glance][image-import] local disk space required by image import and conversion
by Tony Liu 29 Nov '21

29 Nov '21

Hi, The target is for user to import .qcow2 image from download site and automatically stored as raw image. Read through [1], this seems doable. I am not sure the workflow. Does it download the whole qcow2 and convert it to raw locally, or download, convert and upload in a streaming way, which only require small space for caching? The question is that, how much local disk space is required for such import and conversion? [1] https://docs.openstack.org/glance/latest/admin/interoperable-image-import.h… Thanks! Tony

2 2

[tripleo] puppet_config: immutable relationship between config_volume and config_image?
by Brent Eagles 29 Nov '21

29 Nov '21

Hi all, I've been working on https://review.opendev.org/c/openstack/tripleo-heat-templates/+/816895 and the current pep8 check error on the designate-api-container-puppet.yaml template appears to disallow using different container config images on the same config volume. I see where this makes sense but because the way the puppet_config sections seem to be structured I wonder if it was intentional. The templates happen to work in this patch's case because the api specific config image in this template only includes some additional binaries for apache+wsgi necessary for the puppet. However, I can see where this might cause some really unfortunate issues if the config images for a given config_volume were to have different versions of puppet. While I will alter the templates so the designate config volume use the same config image, it does beg the question if having the puppet_config config_volume definitions duplicated across the templates is a good pattern. Would it be a better choice to adopt a pattern where the immutable parts of the config_volumes (e.g. config_volume name, config_image) can only be defined once per config volume? Perhaps in a separate file and have the mutable parts in their respective template definitions? Cheer, Brent -- Brent Eagles Principal Software Engineer Red Hat Inc.

2 2

[ironic] End of year meeting schedule
by Julia Kreger 29 Nov '21

29 Nov '21

Greetings everyone, Today, during the Ironic team meeting, we reached consensus[0] that we would not hold meetings during the last half of December and for the first week of January. Much as we've done the past few years to give contributors time they can feel safe taking off without missing any meetings, coupled with end of year PTO usage and holidays. We will resume our regular meetings on January 10th, 2022. Dates of cancelled meetings: * December 20th, 2021 * December 27th, 2021 * January 3rd, 2022 Hopefully everyone will get plenty of rest, and be ready to review plenty of code when they get back! Thanks, -Julia [0]: https://meetings.opendev.org/meetings/ironic/2021/ironic.2021-11-29-15.00.l…

1 0

[neutron][nova] [kolla] vif plugged timeout
by Michal Arbet 29 Nov '21

29 Nov '21

Hi, Has anyone seen issue which I am currently facing ? When launching heat stack ( but it's same if I launch several of instances ) vif plugged in timeouts an I don't know why, sometimes it is OK ..sometimes is failing. Sometimes neutron reports vif plugged in < 10 sec ( test env ) sometimes it's 100 and more seconds, it seems there is some race condition but I can't find out where the problem is. But on the end every instance is spawned ok (retry mechanism worked). Another finding is that it has to do something with security group, if noop driver is used ..everything is working good. Firewall security setup is openvswitch . Test env is wallaby. I will attach some logs when I will be near PC .. Thank you, Michal Arbet (Kevko)

8 12

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

29 Nov '21

Hi, I am using Openstack Wallaby release with OVN on Ubuntu 20.04. My environment consists of 2 compute nodes and 1 controller node. ovs-vswitchd (Open vSwitch) 2.15.0 Ubuntu Kernel Version: 5.4.0-88-generic compute node1 172.16.30.1 compute node2 172.16.30.3 controller/Network node/Primary ovs-db IP 172.16.30.46 backup ovs-db 172.16.30.47 I added another node for backup ovs-db server (172.16.30.47 ) and installed openvswitch-ovn and networking-ovn packages on it for backup ovs-db server and using Pacemaker to manage the ovn-northd(Open vSwitch) service between primary and backup ovs-db server active/passive HA mode. Pacemaker cluster is successful and after creating a pacemaker cluster, I am using the following commands to create one active and one backup server for OVN databases. $ pcs resource create ovndb_servers ocf:ovn:ovndb-servers \ master_ip=172.16.30.46 \ ovn_ctl=<path of the ovn-ctl script> \ op monitor interval="10s" \ op monitor role=Master interval="15s" But i am getting below error: Error: Agent 'ocf:ovn:ovndb-servers' is not installed or does not provide valid metadata: Metadata query for ocf:ovn:ovndb-servers failed: Input/output error, use --force to override I would really appreciate any input in this regard. Best regards, Faisal Sheikh

1 0

Regarding Drop down of frequently used stacks in OpenStack Wallaby Version 23.1.2
by Adivya Singh 29 Nov '21

29 Nov '21

Dear Team, I want a Drop down of frequently used stack in my orchestration --> Launch Stack parametre in openstack version given above, Is there any Solution for this, How should i go ahead with this Regards Adivya Singh

2 2

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

29 Nov '21

Hi, I am using Openstack Wallaby release with OVN on Ubuntu 20.04. My environment consists of 2 compute nodes and 1 controller node. ovs-vswitchd (Open vSwitch) 2.15.0 Ubuntu Kernel Version: 5.4.0-88-generic compute node1 172.16.30.1 compute node2 172.16.30.3 controller/Network node/Primary ovs-db IP 172.16.30.46 backup ovs-db 172.16.30.47 I added another node for backup ovs-db server (172.16.30.47 ) and installed openvswitch-ovn and networking-ovn packages on it for backup ovs-db server and using Pacemaker to manage the ovn-northd(Open vSwitch) service between primary and backup ovs-db server active/passive HA mode. Pacemaker cluster is successful and after creating a pacemaker cluster, I am using the following commands to create one active and one backup server for OVN databases. $ pcs resource create ovndb_servers ocf:ovn:ovndb-servers \ master_ip=172.16.30.46 \ ovn_ctl=<path of the ovn-ctl script> \ op monitor interval="10s" \ op monitor role=Master interval="15s" But i am getting below error: Error: Agent 'ocf:ovn:ovndb-servers' is not installed or does not provide valid metadata: Metadata query for ocf:ovn:ovndb-servers failed: Input/output error, use --force to override I would really appreciate any input in this regard. Best regards, Faisal Sheikh

1 0

[neutron]Some floating IPs inaccessible after restart of L3 agent
by Kamil Madáč 29 Nov '21

29 Nov '21

Hello Everyone, We have openstack Victoria deployed since the beginning of the year with kolla/ansible in docker containers. Everything was running OK, but few weeks ago we noticed issues with networking. Our installation uses Openvswitch networking with DVR non HA routers. Everything is running smoothly until we restart L3 agent. After that, some floating ips of VMs running on the node where L3 agent is running becomes inaccessible. Workaround is to reassign floating IP to affected VM. Every restart affects same floating IPs and VMs. No errors/excpetions found in logs. I was able to find out that after restart there are missing routes for those particular floating IPs in fip- namespace, which causes that proxy arp responses are not working. After floating IP address is reassigned, routes are added by L3 agent and floating IP is working again. Looks like some sort of race condition in L3 agent, but I was not able to identify any possible existing bug. L3 agent is in version 17.0.1.dev44. Is anyone aware of any existing bug which could explain such behavior, or does anyone have idea how to solve the issue? Kamil Madáč Slovensko IT a.s.

2 3

[Image Encryption] No meeting today
by Josephine Seifert 29 Nov '21

29 Nov '21

Hi, due to a conflicting meeting today I will not be able to hold the popup team meeting. Next meeting will be next week. greetings Josphine (Luzi)

1 0

[neutron] Bug deputy, 22Nov - 28Nov
by Rodolfo Alonso Hernandez 29 Nov '21

29 Nov '21

Hello Neutrinos: This is the bug report from last week. Critical: https://bugs.launchpad.net/neutron/+bug/1952004: “ovn: Functional test may fail if northd hasn't initialized DBs yet”. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/819032 https://bugs.launchpad.net/neutron/+bug/1952023: “Neutron functional tests don't properly clean up ovn-northd”. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/819049 <https://bugs.launchpad.net/neutron/+bug/1952066> https://bugs.launchpad.net/neutron/+bug/1952066: “Scenario test test_mac_learning_vms_on_same_network fails intermittently in the ovn job”. Assigned. https://bugs.launchpad.net/neutron/+bug/1952357: “Functional tests job in the ovn-octavia-provider is broken“. Assigned. Patch: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/819377 <https://bugs.launchpad.net/neutron/+bug/1952393> https://bugs.launchpad.net/neutron/+bug/1952393: “[OVN] neutron-tempest-plugin-scenario-ovn broken with "ovn-northd did not start"“. Assigned. Patch: https://review.opendev.org/c/openstack/devstack/+/819402 <https://bugs.launchpad.net/neutron/+bug/1952508> https://bugs.launchpad.net/neutron/+bug/1952508: “[OVN] "TestAgentMonitor.test_agent_change_controller" failing randomly“. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/819502 High: https://bugs.launchpad.net/neutron/+bug/1952567: “[ml2][ovs] ports tag are missing and flood on those”. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/819567 <https://bugs.launchpad.net/neutron/+bug/1952550> https://bugs.launchpad.net/neutron/+bug/1952550: “[OVN] neutron_ovn_metadata_agent retrying on UUID errors infinitely”. *Unassigned* . Medium: https://bugs.launchpad.net/neutron/+bug/1951816: “[OVN] setting a IPv6 address in dns_servers is broken”. *Unassigned*. https://bugs.launchpad.net/neutron/+bug/1951872: “OVN: Missing reverse DNS for instances”. *Unassigned*. https://bugs.launchpad.net/neutron/+bug/1952055: “native firewall driver - conntrack marks too much traffic as invalid“. *Unassigned*. Low: https://bugs.launchpad.net/neutron/+bug/1951569: “[L3] L3 agent extension should always inherit from "L3AgentExtension"”. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/818540 <https://bugs.launchpad.net/neutron/+bug/1952409> https://bugs.launchpad.net/neutron/+bug/1952409: “SQLAlchemy "ConnectionEvents.before_execute" signature has changed in 1.4“. Assigned. Patch: https://review.opendev.org/c/openstack/neutron/+/819420 Undecided/Opinion/Invalid: https://bugs.launchpad.net/neutron/+bug/1951720: "Virtual interface creation failed". More information is needed to debug this issue. https://bugs.launchpad.net/neutron/+bug/1952249: "[OVN] Created VM name overrides predefined port dns-name". The extension works as expected. Regards.

1 0

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

26 Nov '21

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * Most of the meeting discussions are summarized below (Completed or in-progress activities section). Meeting full logs are available @ https://meetings.opendev.org/meetings/tc/2021/tc.2021-11-25-15.00.log.html * Next week's meeting is video call on 2nd Dec, Thursday 15:00 UTC, feel free the topic on the agenda[1] by 1st Dec. 2. What we completed this week: ========================= * Add ProxySQL repository for OpenStack-Ansible[2] * Mark 'Technical Writing' SIG 'complete' as it is merged into TC [3] * Rename ‘Extended Maintenance’ SIG to the ‘Stable Maintenance’ [4] * Retire training-labs repo [5] 3. Activities In progress: ================== TC Tracker for Yoga cycle ------------------------------ * This etherpad includes the Yoga cycle targets/working items for TC[6]. Open Reviews ----------------- * 8 open reviews for ongoing activities[7]. Yoga testing runtime ------------------------- We updated the Yoga testing runtime to move from CentOS stream 8 to CentOS stream 9 and so drop the py3.6[8]. But while updating projects to drop py3.6, and discussion on whether we should change 'python_requires'>= 3.8 in setup.cfg, another (but good) discussion started on ML about whether we should continue testing py3.6 and support CentOS stream 8 and 9 both in yoga which is what RDO community plan is[8]. After discussing on ML and then with Alfredo Moralejo on TC IRC channel, we have a potential way forward on this which I have summarized on ML thread[9]. I will keep that open to get feedback or any objection to the proposed plan and accordingly we will conclude it early next week. I hope I have summarized the discussion here if not please read the ML thread for this. Fixing Zuul config error -------------------------- If your project is listed in zuul config error, please start planing to fix those[10] RBAC discussion: continuing from PTG ---------------------------------------------- After last week meeting discussion, we are almost ready with this goal, if you would like to review the current direction as well as the schedule, please review it[11]. Next plan is to merge the proposed goal and then select it ASAP as m-1 is already passed for Yoga cycle. Community-wide goal updates ------------------------------------ * Two goals are proposed currently and under review. ** RBAC goal is pretty much in good shape now, feel free to review it[11] ** 'FIPS compatibility and compliance' [12]. Adjutant need maintainers and PTLs ------------------------------------------- We are waiting to hear from Braden, Albert on permission to work in this project[13]. New project 'Skyline' proposal ------------------------------------ * TC is still waiting for skyline team to respond on open queries[14]. TC tags analysis ------------------- * TC agreed to remove the framework and it is communicated in ML[15]. Project updates ------------------- * Add ansible-collection-kolla repo to Kolla project[16] * Retire js-openstack-lib [17] 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[18]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15 UTC [19] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [2] https://review.opendev.org/c/openstack/governance/+/817245 [3] https://review.opendev.org/c/openstack/governance-sigs/+/815868 [4] https://review.opendev.org/c/openstack/governance-sigs/+/817499 [5] https://review.opendev.org/c/openstack/governance/+/817511 [6] https://etherpad.opendev.org/p/tc-yoga-tracker [7] https://review.opendev.org/q/projects:openstack/governance+status:open [8] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/026001… [9] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/026024… [10] https://etherpad.opendev.org/p/zuul-config-error-openstack [11] https://review.opendev.org/c/openstack/governance/+/815158 [12] https://review.opendev.org/c/openstack/governance/+/816587 [13] http://lists.openstack.org/pipermail/openstack-discuss/2021-November/025786… [14] https://review.opendev.org/c/openstack/governance/+/814037 [15] http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025571.… [16] https://review.opendev.org/c/openstack/governance/+/819331 [17] https://review.opendev.org/c/openstack/governance/+/807163 [18] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [19] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

Project-scoped app creds - Best practice
by Ryan Bannon 26 Nov '21

26 Nov '21

Hello all, Relatively new to OpenStack. To my understanding, application credentials are bound to users. Is there a way to bind them to Projects (I assume not) or, perhaps, Groups? My naive thought on a possible solution is that if a group has access to a Project, a "generic" user account that everybody has access to could be used for the application credentials. (The use case here is to not bind an app cred to an individual who might leave the organization, thus making the app cred secret lost.) Thanks, Ryan

2 5

Nova Local Disk Storage
by Seena Fallah 26 Nov '21

26 Nov '21

Hi, Is there any support for creating instances on a whole separate disk, not an LVM?

1 0

[Openstack-victoria] [IRONIC] error in network interface | baremetal node validate
by Swogat Pradhan 25 Nov '21

25 Nov '21

Hi, I am currently trying to setup openstack ironic using driver IPMI. I followed the official docs of openstack for setting everything up. When i run openstack baremetal node validate $NODE_UUID, i am getting the following error: * Unexpected exception, traceback saved into log by ironic conductor service that is running on controller: 'ServiceTokenAuthWrapper' object has no attribute '_discovery_cache' * in the network interface in command output. When i check the ironic conductor logs i see the following messages: <attached <https://mail.google.com/mail/u/0?ui=2&ik=7bb3543b01&attid=0.1&permmsgid=msg…> > Can anyone suggest a solution or a way forward. With regards Swogat Pradhan

2 4

[aodh][tacker] Support for pyparsing v 3.0.6 is required in python-aodhclient
by ueha.ayumu＠fujitsu.com 25 Nov '21

25 Nov '21

Hi aodh team, Hi I'm Ueha from tacker team. Tacker CI fails with the following error since a few days ago: ---from h-eng log--- Traceback (most recent call last): ... File "/usr/local/lib/python3.8/dist-packages/aodhclient/utils.py", line 43, in <module> expr = pp.operatorPrecedence(condition, [ AttributeError: module 'pyparsing' has no attribute 'operatorPrecedence' -------------------- As I have researched, the version of pyparsing has been updated to v3.0.6 in global requirements [1]. And operatorPrecedence was already deprecated in pyparsing v3.0.6. A patch to fix this appears to have already been posted to python-aodhclient [2]. Could you consider merging the fixes to avoid errors in the CI? For your information, it have been merged similar fixes in cinder [3] and manila [4]. [1] https://review.opendev.org/c/openstack/requirements/+/818614 [2] https://review.opendev.org/c/openstack/python-aodhclient/+/819054 [3] https://review.opendev.org/c/openstack/cinder/+/818834 [4] https://review.opendev.org/c/openstack/manila/+/818829 Regards, Ueha

1 0

[puppet] Propose retiring old stable branches(Stein, Rocky and Queens)
by Takashi Kajinami 25 Nov '21

25 Nov '21

Hello, In puppet repos we have plenty of stable branches still open, and the oldest is now stable/queens. However recently we haven't seen many backports proposed to stein, rocky and queens [1], so I'll propose retiring these three old branches now. Please let me know if anybody is interested in keeping any of these three. Note that currently CI jobs are broken in these three branches and it is likely we need to investigate the required additional pinning of dependent packages. If somebody is still interested in maintaining these old branches then these jobs should be fixed. [1] https://review.opendev.org/q/(project:%255Eopenstack/puppet-.*)AND(NOT+proj… Thank you, Takashi Kajinami

2 2