February 2021 - openstack-discuss

[all][stackalytics] stackalytics.io
by Andrii Ostapenko 17 Feb '21

17 Feb '21

Hi all! Since https://stackalytics.com is not operational for quite some time already, I exposed another instance on https://stackalytics.io It shares the same configuration and is kept updated. You're welcome to use it at least until stackalytics.com is up and running (just please be gentle). Sincerely, Andrii Ostapenko

3 5

[Octavia] driver for 3rd party loadbalancer
by Artem Goncharov 17 Feb '21

17 Feb '21

Hi all, In our cloud we have a non Octavia LoadBalancer provided by vendor with no possibility to get it replaced with real Octavia. I see there is possibility to provide drivers for Octavia to operate other types of load balancers (https://docs.openstack.org/octavia/latest/contributor/guides/providers.html <https://docs.openstack.org/octavia/latest/contributor/guides/providers.html>), but there are still some issues/questions: - is it possible to make Octavia only expose it’s API and make the driver transpose calls into the internal LB - there is no need for any data persistency on the Octavia side, since there are other interfaces to operate LB what will cause inconsistences otherwise - can the driver have access to the API user data (user sends X-Auth-Token, it gets validated by keystonemiddleware, but I need to pass extra info to the underlaying internal LB API). Here I do not need anything special, it is more or less get access to the used token to pass it further. Ideally auth can be offloaded completely to the underlaying LB This all sounds like writing simple API convertor, but we really want service behaviour is 100% compatible to Octavia to avoid further issues (and perhaps convincing Octavia can replace other solution). Is this achievable? If yes I would really appreciate technical hints how this can be implemented. I feel like Octavia is already covering such use case (or at least intend to do so), but I am lost in docs. Thanks in advance, Artem

2 2

[All] Open Infrastructure Meeting on Branding, Trademark, Logo, etc.
by Kanevsky, Arkady 17 Feb '21

17 Feb '21

Dear Open Infra fellow members, It is time for us to start figuring out for Open Infrastructure what logo, branding, trademarks, and other related things are. I have created a doodle for several possible times next week for inaugural meeting. https://doodle.com/poll/3n4ke3ihryqn8bv5?utm_source=poll&utm_medium=link Please, take a poll and I will schedule meeting for us. Thanks, Arkady Kanevsky, Ph.D. SP Chief Technologist & DE Dell Technologies office of CTO Dell Inc. One Dell Way, MS PS2-91 Round Rock, TX 78682, USA Phone: 512 7204955

1 1

[TripleO] Closing out stale bugs
by Marios Andreou 17 Feb '21

17 Feb '21

Hello TripleO, FYI I started a process of closing out stale bugs. For now I'm specifically looking at bugs targeted for wallaby-3 [1]. I just did a first pass and have removed 'wallaby-3' as target for anything with status 'Incomplete' and older than 365 days - in total 81 bugs (details there [2]). I will then also move onto 'New' 'Triaged' and 'In Progress' (older than 365 days). If you see a comment like [3] on your bug and you disagree please re-set the status and milestone but also add a comment about why you disagree ('still a thing', 'ongoing _there_' etc). thanks for your understanding! regards, marios [1] https://launchpad.net/tripleo/+milestone/wallaby-3 [2] https://gist.github.com/marios/b3155fe3b1318cc26bfa4bc15c764a26#gistcomment… [3] https://bugs.launchpad.net/tripleo/+bug/1768596/comments/3

1 0

[cloudkitty] Proposing Mariusz Karpiarz as a CloudKitty core reviewer
by Rafael Weingärtner 17 Feb '21

17 Feb '21

Hello guys, I would like to propose Mariusz Karpiarz (mkarpiarz) to be a new member of the CloudKitty core team. Mariusz has been working consistently in CloudKitty for quite some time already. He is actively reviewing and proposing patches. Moreover, he is always present in the bi-weekly meeting to discuss and trace CloudKitty's future. I think that he will be a great addition to our (not too big) core team. I will open this nomination open for a week to get feedback about it. Please give your +1/-1 in the next coming days. -- Rafael Weingärtner

2 1

[stein][neutron][bridge config][kolla]ovs-vsctl shows issue with bridge config
by roshan anvekar 17 Feb '21

17 Feb '21

Hello, I have tried multiple options of setting up the bridge interface for vlan provider network setup in stein. None is allowing the gm to get IP. Getting the same DHCP issue all the time. I tried with: 1. Setting provider network interface as as sub interface on a bond. Connecting bridge with it. 2. Setting bridge directly over bond. 3. Manual setup of bridge interface. 4. Allowing Openstack to setup bridge on the bond. None of this is working. All are giving the same DHCP issue. Also I m using a sub-interface on the same bond for TLS interface. Not sure if that's causing a issue. Error message in openvswitch container while running ovs-vsctl show command: *error: "could not add network device br-ex to ofproto (File exists)"* Any pointers for this issue?? Regards, Roshan

2 3

[puppet][ci][infra] Missing jobs in check/gate queue
by Takashi Kajinami 17 Feb '21

17 Feb '21

Hello, Today I noticed that some of our CI jobs are not properly invoked. For example in the following patch we don't see results of unit tests and integration tests. https://review.opendev.org/c/openstack/puppet-ceilometer/+/775730 These jobs were executed when we merged another patch last night. https://review.opendev.org/c/openstack/puppet-ceilometer/+/765100 I was looking into the zuul job definition in puppet repo but could not find any suspicious change in our repos. Is there any change made in the infra side which can result in this behavior ? I'd appreciate some help from infra team with this issue. Because we don't have enough test coverage now, please hold on merging any patches until this problem is solved. Thank you, Takashi

2 3

[victoria][octavia] Operating status OFFLINE
by Malik Obaid 16 Feb '21

16 Feb '21

Hi, I have configured Octavia using Openstack Victoria release on Ubuntu 20.04. Everything is working as expected like loadbalancing, healthmonitoring etc. The issue I am facing is that the operating_status of Loadbalancer, listener, pool and its members always stay OFFLINE. I am new to Openstack and would really appreciate your help in this regard. ------------------------------------------------------------------------- *loadbalancer status:* { "loadbalancer": { "id": "b33d7de7-4bf6-4815-a151-5ca7a7a3a40e", "name": "testlb", "operating_status": "OFFLINE", "provisioning_status": "ACTIVE", "listeners": [ { "id": "03972160-dd11-4eac-855b-870ee9ee909b", "name": "testlistener", "operating_status": "OFFLINE", "provisioning_status": "ACTIVE", "pools": [ { "id": "5ad57d34-a9e7-4aa1-982d-e528b38c84ed", "name": "testpool", "provisioning_status": "ACTIVE", "operating_status": "OFFLINE", "health_monitor": { "id": "3524ea0f-ce2b-4957-9967-27d71033f964", "name": "testhm", "type": "HTTP", "provisioning_status": "ACTIVE", "operating_status": "ONLINE" }, "members": [ { "id": "25b94432-6464-4245-a5db-6ecedb286721", "name": "", "operating_status": "OFFLINE", "provisioning_status": "ACTIVE", "address": "192.168.100.44", "protocol_port": 80 }, { "id": "9157600c-280e-4eb9-a9aa-6b683da76420", "name": "", "operating_status": "OFFLINE", "provisioning_status": "ACTIVE", "address": "192.168.100.90", "protocol_port": 80 } ] } ] } ] } } ---------------------------------------------------------------------------------------- *octavia.conf* #create new [DEFAULT] # RabbitMQ connection info transport_url = rabbit://openstack:password@172.16.30.46 [api_settings] # IP address this host listens bind_host = 172.16.30.46 bind_port = 9876 auth_strategy = keystone api_base_uri = http://172.16.30.46:9876 # MariaDB connection info [database] connection = mysql+pymysql://octavia:password@172.16.30.45/octavia [health_manager] bind_ip = 0.0.0.0 bind_port = 5555 # Keystone auth info [keystone_authtoken] www_authenticate_uri = http://172.16.30.46:5000 auth_url = http://172.16.30.46:5000 memcached_servers = 172.16.30.46:11211 auth_type = password project_domain_name = default user_domain_name = default project_name = service username = octavia password = servicepassword # specify certificates created on [2] [certificates] ca_private_key = /etc/octavia/certs/private/server_ca.key.pem ca_certificate = /etc/octavia/certs/server_ca.cert.pem server_certs_key_passphrase = insecure-key-do-not-use-this-key ca_private_key_passphrase = not-secure-passphrase # specify certificates created on [2] [haproxy_amphora] server_ca = /etc/octavia/certs/server_ca-chain.cert.pem client_cert = /etc/octavia/certs/private/client.cert-and-key.pem # specify certificates created on [2] [controller_worker] client_ca = /etc/octavia/certs/client_ca.cert.pem amp_image_tag = Amphora # specify [flavor] ID for Amphora instance amp_flavor_id = 200 # specify security group ID Amphora instance amp_secgroup_list = 4fcb5a29-06b3-4a5d-8804-23c4670c200e # specify network ID to boot Amphora instance (example below specifies public network [public]) amp_boot_network_list = 7d6af354-206f-4c30-a0d6-dcf0f7f35f08 network_driver = allowed_address_pairs_driver compute_driver = compute_nova_driver amphora_driver = amphora_haproxy_rest_driver [oslo_messaging] topic = octavia_prov # Keystone auth info [service_auth] auth_url = http://172.16.30.46:5000 memcached_servers = 172.16.30.46:11211 auth_type = password project_domain_name = default user_domain_name = default project_name = service username = octavia password = servicepassword ----------------------------------------------------------------------- Regards, Malik Obaid

2 1

[magnum] status fail if images are marked with community
by Ionut Biru 16 Feb '21

16 Feb '21

Hi guys, I wanted to "decommission" the old stable fedora-coreos-32 from my catalog and I marked the image with community instead of public. That's how the nova team suggested that old images should be decommissioned . A cluster deployed with that image had a node shutdown and magnum healer tried to resolve the issue and now the status of the cluster is in error with: faults | {'default-master': "Resource UPDATE failed: resources[0]: resources.kube_masters.Property error: resources.kube_node_volume.properties.image: Error validating value 'fedora-coreos-32-x86_64': No images matching {'name': u'fedora-coreos-32-x86_64'}.", 'default-worker': "Resource UPDATE failed: resources[0]: resources.kube_masters.Property error: resources.kube_node_volume.properties.image: Error validating value 'fedora-coreos-32-x86_64': No images matching {'name': u'fedora-coreos-32-x86_64'}."} | In the mean time I have marked the image as public and started the node but the healer cannot fix it and it's the status is still in error. Magnum api has an exception in the logs: magnum.common.exception.NotSupported: Updating a cluster when status is "UPDATE_FAILED" is not supported openstack coe cluster show: https://paste.xinu.at/JxYaw/ What's the right path to fix this issue? -- Ionut Biru - https://fleio.com

2 1

[scientific-sig] IRC meeting today 2100 UTC - SIG videos and Superclouds
by Stig Telfer 16 Feb '21

16 Feb '21

Hi All - We have a Scientific SIG meeting today at 2100 UTC (about 90 minutes time). Everyone is welcome. Today's agenda is taking shape here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_February_16th_20… We'd like to talk about mixing virtualisation and bare metal (the "Supercloud") and the nice video from the Baremetal SIG (https://youtu.be/uyN481mqdOs) and whether the Scientific SIG could do the same. If you'd like to propose a topic, please feel free to do so and come along. Cheers, Stig

1 0

[keystone] No team meeting Feb 16
by Nikolla, Kristi 16 Feb '21

16 Feb '21

Hi team, Sorry for the short notice. A last minute scheduling conflict came up and I won't be able to host the weekly meeting today. Best, Kristi

1 0

[ops][cinder][kolla-ansible] cinder-backup fails if source disk not in nova az
by Adam Zheng 16 Feb '21

16 Feb '21

3 4

[victoria][magnum] Kubernetes 1.19 and 1.20 Support
by Ammad Syed 16 Feb '21

16 Feb '21

Hi, Is openstack (victoria) magnum supports kubernetes 1.19 and 1.20 ? -- Regards, Syed Ammad Ali

2 1

Self service networks + IPV6 with provider range
by Maxence Sartiaux 16 Feb '21

16 Feb '21

Hello, I am installing an openstack infrastructure but i have an issue with the selfservice networks and the ipv6 On my provider network i have the fddd:3138:5d15:18::/64 subnet which is my local server range. I've managed to make the ipv6 works in a SLAAC-SLAAC configuration with a second /64 subnet (fddd:3138:5d15:180::/64) and a static route in my switches (by defining the provider subnet + gateway and selfservice subnet) But my question is : Is it possible to use the "none - slaac" mode (or other) in my selfservice network with the "provider range" fddd:3138:5d15:18::/64 and let my external router advertise the RA for the openstack instances ? Or is it only possible on a "provider" network without a neutron router ? Just like that i don't have to create a second subnet for each vlan we have. I hope it's understandable. Thanks.

2 1

[tripleo] moving tripleo-ipsec to independent release model
by Marios Andreou 16 Feb '21

16 Feb '21

hello TripleO, per $subject I want to propose that tripleo-ipsec moves to the independent release model, as done recently for os-collect-config and friends at [1]. The tripleo-ipsec repo hasn't had much/any commits in the last year [2]. In fact, we hadn't even created a ussuri branch for this repo and no-one noticed (!). Because of the lack of stable/ussuri some of the release jobs failed, as discussed at [3] and which ttx tried to fix (thank you!) with [4]. Unfortunately this hasn't resolved the issue and jobs are still failing, as discussed just now in openstack-release [4]. If we agree to move tripleo-ipsec to independent then it will also resolve this build job issue. If we move tripleo-ipsec to independent it means we can still release it if required, but we will no longer create stable/branches for the repo. please voice any objections here or go and comment on the proposal at [6] thanks for reading! regards, marios [1] https://review.opendev.org/c/openstack/releases/+/772570 [2] https://opendev.org/openstack/tripleo-ipsec/commits/branch/master [3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/020112.… [4] https://review.opendev.org/c/openstack/releases/+/772995 [5] http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-re… [6] https://review.opendev.org/c/openstack/releases/+/775395

4 7

[tripleo] TripleO CI Summary: Unified Sprint 39
by Bhagyashri Shewale 15 Feb '21

15 Feb '21

Greetings, The TripleO CI team has just completed **Unified Sprint 39** (Jan 14 thru Feb 03 2021). The following is a summary of completed work during this sprint cycle: - Deployed the new (next gen) promoter code <https://hackmd.io/team/rh-openstack-ci?nav=search&q=promoter> - Deploy the promoter server using new code for rocky and train centos-7 promotion - Applied new promoter configuration engine changes to consolidate all promoters into the same code. - Started dependency pipeline <https://hackmd.io/team/rh-openstack-ci?nav=search&q=dependency+pipeline> work: - RHEL and CentOS OpenVswitch pipeline - Upstream and downstream container-tools pipeline - Downstream RHELU.next - Add centos8 stream jobs and pipeline - https://hackmd.io/Y6IGnQGXTqCl8TAX0YAeoA?view - Create the design document for tripleo-repos <https://opendev.org/openstack/tripleo-repos> - https://hackmd.io/v2jCX9RwSeuP8EEFDHRa8g?view - https://review.opendev.org/c/openstack/tripleo-specs/+/772442 - [tempest skip list] Add addtest command to tempest-skiplist - Tempest scenario manager Many of the scenario manager methods used to be private apis. Since these methods Are supposed to be used in tempest plugins they aren’t expected to be private. Following commits are with respect to this idea except - https://review.opendev.org/c/openstack/tempest/+/774085 - https://review.opendev.org/c/openstack/tempest/+/766472 - https://review.opendev.org/c/openstack/tempest/+/773783 - https://review.opendev.org/c/openstack/tempest/+/773019 Implementation of create_subnet() api varies with manila-tempest plugin For the stable implementation of create_subnet() following parameters have been added: 1. Condition to check empty str_cidr 2. More attributes in case of ipv6 3. Usage of default_subnet_pool - - https://review.opendev.org/c/openstack/tempest/+/766472 - Ruck/Rover recorded notes [1]. The planned work for the next sprint and leftover previous sprint work as following: - Migrate upstream master from CentOS-8 to CentOS-8-Stream - improving resource usage/ reduce upstream infra footprint, context <http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020235…> - Deploy the promoter server for master and other releases - elastic-recheck containerization - https://hackmd.io/dmxF-brbS-yg7tkFB_kxXQ - Openstack health for tripleo - https://hackmd.io/HQ5hyGAOSuG44Le2x6YzUw - Tripleo-repos spec and implementation - https://hackmd.io/v2jCX9RwSeuP8EEFDHRa8g?view - https://review.opendev.org/c/openstack/tripleo-specs/+/772442 - Leftover dependency pipeline work: - ansible 2.10/11 upstream pipeline - https://hackmd.io/riLaLFcTTpybbyY51xcm9A?both - monitoring dependency pipeline under cockpit The Ruck and Rover for this sprint are Arx Cruz(arxcruz) and Sandeep Yadav (ysandeep). Please direct questions or queries to them regarding CI status or issues in #tripleo, ideally to whomever has the ‘|ruck’ suffix on their nick. Ruck/rover notes to be tracked in hackmd [2]. Thanks, Bhagyashri Shewale [1] https://hackmd.io/_XvcCzQlQ1-A9ygYMlmvKA [2] https://hackmd.io/Ta6fdwi2Sme4map8WEiaQA

1 0

[tc] weekly update
by Mohammed Naser 15 Feb '21

15 Feb '21

Hi everyone, Here’s an update on what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # Patches ## Open Reviews - Cool-down cycle goal https://review.opendev.org/c/openstack/governance/+/770616 - Retire tempest-horizon https://review.opendev.org/c/openstack/governance/+/774379 - monasca-log-api & monasca-ceilometer does not make releases https://review.opendev.org/c/openstack/governance/+/771785 - Add assert:supports-api-interoperability tag to neutron https://review.opendev.org/c/openstack/governance/+/773090 - Add assert:supports-api-interoperability to cinder https://review.opendev.org/c/openstack/governance/+/773684 # Other Reminders - Our next [TC] weekly meeting is scheduled for February 18th at 1500 UTC. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, February 17th, at 2100 UTC. Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[neutron] CI meeting - Tuesday 16.02.2021
by Slawek Kaplonski 15 Feb '21

15 Feb '21

Hi, I will not be available to chair CI meeting tomorrow. So let's cancel it this week. See You online and on the meeting next week :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[neutron] Team meeting - Tuesday 16.02.2021 cancelled
by Slawek Kaplonski 15 Feb '21

15 Feb '21

Hi, I will not be available to chair team meeting tomorrow. So lets cancel it this week. See You online and on the meeting next week :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

Nova-compute 20.4.0-ubuntu1~cloud0 fails to start
by Eyle Brinkhuis 15 Feb '21

15 Feb '21

Hi, Deploying a new testbed, we experience an issue with nova-compute (using canonical charmed openstack Train). We use networking-vpp, that uses python-etcd. After installation of openstack, and configuration of the networking-vpp setup, we cannot start nova-compute anymore: Feb 15 09:35:19 sr635-1 nova-compute[131674]: Traceback (most recent call last): Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/bin/nova-compute", line 6, in <module> Feb 15 09:35:19 sr635-1 nova-compute[131674]: from nova.cmd.compute import main Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/nova/cmd/__init__.py", line 16, in <module> Feb 15 09:35:19 sr635-1 nova-compute[131674]: import nova.monkey_patch # noqa Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/nova/monkey_patch.py", line 98, in <module> Feb 15 09:35:19 sr635-1 nova-compute[131674]: _monkey_patch() Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/nova/monkey_patch.py", line 67, in _monkey_patch Feb 15 09:35:19 sr635-1 nova-compute[131674]: import oslo_service # noqa Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/oslo_service/__init__.py", line 16, in <module> Feb 15 09:35:19 sr635-1 nova-compute[131674]: from oslo_log import log as logging Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/oslo_log/log.py", line 41, in <module> Feb 15 09:35:19 sr635-1 nova-compute[131674]: from oslo_config import cfg Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/oslo_config/cfg.py", line 53, in <module> Feb 15 09:35:19 sr635-1 nova-compute[131674]: from oslo_config import types Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/oslo_config/types.py", line 28, in <module> Feb 15 09:35:19 sr635-1 nova-compute[131674]: from debtcollector import removals Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/debtcollector/__init__.py", line 20, in <module> Feb 15 09:35:19 sr635-1 nova-compute[131674]: 'debtcollector').version_string() Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pbr/version.py", line 467, in version_string Feb 15 09:35:19 sr635-1 nova-compute[131674]: return self.semantic_version().brief_string() Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pbr/version.py", line 462, in semantic_version Feb 15 09:35:19 sr635-1 nova-compute[131674]: self._semantic = self._get_version_from_pkg_resources() Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pbr/version.py", line 439, in _get_version_from_pkg_resources Feb 15 09:35:19 sr635-1 nova-compute[131674]: import pkg_resources Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3250, in <module> Feb 15 09:35:19 sr635-1 nova-compute[131674]: @_call_aside Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3234, in _call_aside Feb 15 09:35:19 sr635-1 nova-compute[131674]: f(*args, **kwargs) Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3263, in _initialize_master_working_set Feb 15 09:35:19 sr635-1 nova-compute[131674]: working_set = WorkingSet._build_master() Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 574, in _build_master Feb 15 09:35:19 sr635-1 nova-compute[131674]: ws = cls() Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 567, in __init__ Feb 15 09:35:19 sr635-1 nova-compute[131674]: self.add_entry(entry) Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 623, in add_entry Feb 15 09:35:19 sr635-1 nova-compute[131674]: for dist in find_distributions(entry, True): Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2065, in find_on_path Feb 15 09:35:19 sr635-1 nova-compute[131674]: for dist in factory(fullpath): Feb 15 09:35:19 sr635-1 nova-compute[131674]: File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2127, in distributions_from_metadata Feb 15 09:35:19 sr635-1 nova-compute[131674]: if len(os.listdir(path)) == 0: Feb 15 09:35:19 sr635-1 nova-compute[131674]: PermissionError: [Errno 13] Permission denied: '/usr/local/lib/python3.6/dist-packages/python_etcd-0.4.5.dist-info' Feb 15 09:35:19 sr635-1 systemd[1]: nova-compute.service: Main process exited, code=exited, status=1/FAILURE Meanwhile, in a different deployment, which runs nova-compute 20.3.0-ubuntu1~cloud0, we do not experience this issue. Permissions of all the packages in /usr/local/lib/python3.6/dist-packages/ are all identical. When we remove all packages once again (python-etcd etc), nova-compute is able to start without any issue. Anyone experiencing the same, or has a workaround? Eyle

2 2

Proposing Flavio Fernandes (flaviof) for ovsdbapp core
by Terry Wilson 15 Feb '21

15 Feb '21

Flavio has been helping out with ovsdbapp a great deal and I would like to nominate him for ovsdbapp-core. He's written some great code and reviews and will be an asset to the team. Historically, I've just added people who were contributing directly, but seeing as ovsdbapp has moved past 1.0 I thought I'd go ahead and follow official procedures this time. ;) Existing team members, please respond with +1/-1. Thanks! Terry

5 6

[neutron] Bug Deputy Report Feb 8 - 15
by Jakub Libosvar 15 Feb '21

15 Feb '21

Hi everyone, I was bug deputy for the last week. It's been mostly business as usual but I'd like to highlight this bug that needs an assignee: https://bugs.launchpad.net/neutron/+bug/1915341 The problem seems to be with LinuxBridge agent after it's restarted, which is not tested on the gate AFAIK. I don't have an LB environment thus I couldn't confirm but would be great if somebody who maintains and is interested in LB can confirm. Here is the full weekly report: Critical * Neutron run with uwsgi is broken with oslo_policy 3.6.2 - https://bugs.launchpad.net/neutron/+bug/1915494 - Assigned to: Slawek Kaplonski * neutron-linuxbridge-agent not starting due to nf_tables rules - https://bugs.launchpad.net/neutron/+bug/1915341 - Needs an assignee High * test_create_router_set_gateway_with_fixed_ip fails in dvr-ha job - https://bugs.launchpad.net/neutron/+bug/1915271 - In progress: https://review.opendev.org/c/openstack/neutron/+/774785 - Assigned to: Oleg Bondarev * Metadata over IPv6 don't works with L3ha routers - https://bugs.launchpad.net/neutron/+bug/1915495 - Assigned to: Slawek Kaplonski Medium * Split logfiles for neutron-functional-with-uwsgi job are empty - https://bugs.launchpad.net/neutron/+bug/1915272 - In progress: https://review.opendev.org/c/openstack/neutron/+/774865 - Assigned to: Bernard Cafarelli * Resource name and collection name for address groups are incorrectly defined in neutron-lib - https://bugs.launchpad.net/neutron/+bug/1915310 - Fix committed: https://review.opendev.org/c/openstack/neutron-lib/+/774924 - Assigned to: Miguel Lavalle * DeviceManager's fill_dhcp_udp_checksums assumes IPv6 available - https://bugs.launchpad.net/neutron/+bug/1915480 - Needs an assignee Low * Openvswitch firewall - removing and adding security group breaks connectivity - https://bugs.launchpad.net/neutron/+bug/1915530 - Assigned to: Slawek Kaplonski RFEs * [RFE] There should be a way to set ethertype for the vlan_transparent networks - https://bugs.launchpad.net/neutron/+bug/1915151 Kuba

1 1

[tc][heat][tacker] Discusssion about heat-translater and tosca-parser maintenance
by TAKAHASHI TOSHIAKI(高橋　敏明) 14 Feb '21

14 Feb '21

Hi, I'm a tacker team member. I'd like to discuss how to maintain heat-translator[1] and tosca-parser[2] repositories. These 2 repositories have not been updated so actively, but tacker often requires code updates for these repositories. Recently, patch merge progress of tacker and these repo do not sometimes match, which affects the development of tacker. For example, our some functional tests on zuul fail because these master codes are not updated. Therefore, tacker members would like to take part more in these 2 developments. Tacker members have already started code reviews, patch posts, etc. If possible, we want some Tacker members to join the core team in the near future. How about this? [1] https://opendev.org/openstack/heat-translator [2] https://opendev.org/openstack/tosca-parser Regards, Toshiaki

5 9

[ironic] A new project for useful deploy steps?
by Dmitry Tantsur 14 Feb '21

14 Feb '21

Hi all, We have finally implemented in-band deploy steps (w00t!), and people started coming up with ideas. I have two currently: 1) configure arbitrary kernel command line arguments via grub 2) write NetworkManager configuration (for those not using cloud-init) I'm not sure how I feel about putting these in IPA proper, seems like we may go down a rabbit hole here. But what about a new project (ironic-python-agent-extras?) with a hardware manager providing a collection of potentially useful deploy steps? Or should we nonetheless just put them in IPA with priority=0? Opinions welcome. Dmitry -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

4 6

[Interop, Users] listing interop results
by Kanevsky, Arkady 12 Feb '21

12 Feb '21

Dell Customer Communication - Confidential Team, We are reviewing our openstack interop program. We have 3 base "certifications" for interop that cloud vendors can submit and foundation list on marketplace https://www.openstack.org/marketplace/ : 1. Openstack Powered Storage 2. OpenStack Powered Compute 3. OpenStack Powered Platform (combines both compute and storage) These can be viewed as the core. And there are 3 add-on programs for specific projects of openstack: 1. DNS (Designate) 2. Orchestration (Heat) 3. Shared-File-System (Manila) We have 4 categories of clouds that use interop programs and list their offering with interoperability results and logo: 1. Remotely managed private clouds - https://www.openstack.org/marketplace/remotely-managed-private-clouds/ * The latest interop guidelines listed there is 2019.11 and most are from 2017-2018 * All used OpenStack Powered Platform * Vexxhost listed without listing what guidelines they used. (Jimmy can you pull what they had submitted and update their entry) 2. Distros and Appliances - https://www.openstack.org/marketplace/distros/ : * These seems to be updated most often. Several used the latest 2020.06 guidelines * There are usage of all 3 core logos. * No add-on logos listed 3. Hosted Private Clouds - https://www.openstack.org/marketplace/hosted-private-clouds/ : * There is one entry that uses 2020.06 guidelines but most are 2016-2018. * Most for Powered Platform and one for Powered Compute 4. Public Cloud - https://www.openstack.org/marketplace/public-clouds/ : * There is one entry that uses 2020.06 guidelines but most are 2016-2018. * Mixture of Powered Platform and Powered Compute I will skip the question on the value of Marketplace program as it will be discussed separately in newly formed temporary WG under foundation to review/define Open Infrastructure Branding and Trademark policy. We need to address the issue on how to list add-ons for current openstack marketplace program. The simplest way is to add to "TESTED" OpenStack Powered Platform/Compute/Storage also add-ons that vendors passed. In the detailed section we already listing what APIs and services supported and which version. So do not see any changes needed there. Comments and suggestions please? Thanks, Arkady Kanevsky, Ph.D. SP Chief Technologist & DE Dell EMC office of CTO Dell Inc. One Dell Way, MS PS2-91 Round Rock, TX 78682, USA Phone: 512 7204955

4 6