- openstack-discuss - lists.openstack.org

[all][interop] Reforming the refstack maintainers team
by Ghanshyam Mann 12 Feb '21

12 Feb '21

Hello Everyone, As Goutham mentioned in a separate ML thread[2] that there is no active maintainer for refstack repo which we discussed in today's interop meeting[1]. We had a few volunteers who can help to maintain the refstack and other interop repo which is good news. I would like to call for more volunteers (new or existing ones), if you are interested to help please do reply to this email. The role is to maintain the source code of the below repos. I will propose the ACL changes in infra sometime next Friday (18th dec) or so. For easy maintenance, we thought of merging the below repo core group into a single group called 'refstack-core' - openstack/python-tempestconf - openstack/refstack - openstack/refstack-client - x/ansible-role-refstack-client (moving to osf/ via https://review.opendev.org/765787) Current Volunteers: - martin (mkopec(a)redhat.com) - gouthamr (gouthampravi(a)gmail.com) - gmann (gmann(a)ghanshyammann.com) - Vida (vhariria(a)redhat.com) - interop-core (we will add this group also which has interop WG chairs so that it will be easy to maintain in the future changes) NOTE: there is no change in the 'interop' repo group which has interop guidelines and doc etc. [1] https://etherpad.opendev.org/p/interop [2] http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019263… -gmann

8 12

[release] Release countdown for week R-8 Feb 15 - Feb 19
by Herve Beraud 12 Feb '21

12 Feb '21

Hello everyone, General Information ------------------- The following cycle-with-intermediary deliverables have not done any intermediary release yet during this cycle. The cycle-with-rc release model is more suited for deliverables that plan to be released only once per cycle. To start the discussion, we have proposed changes[1] that update the release model for the following deliverables: Swift ( https://review.opendev.org/c/openstack/releases/+/774682 ) [1] https://review.opendev.org/q/topic:%22switch-to-rc%22 PTLs and release liaisons for each of those deliverables can either +1 the release model change, or -1 the change if they expect a release soon. We also published a proposed release schedule for the upcoming Xena cycle: https://review.opendev.org/c/openstack/releases/+/772357 Unless new comments are posted on that review that make us reconsider, we will approve this Xena release schedule by February 18. Upcoming Deadlines & Dates -------------------------- Cross-project events: - Non-client library freeze: 04 March, 2021 (R-6 week) - Client library freeze: 11 March, 2021 (R-5 week) - Wallaby-3 milestone: 11 March, 2021 (R-5 week) Project-specific events: - Cinder Driver Features Declaration: 18 February, 2021 (R-8) - Oslo Feature Freeze: 25 February, 2021 (R-7) Thanks for your attention, -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[neutron] Drivers meeting agenda - Friday 12.02.2021
by Slawek Kaplonski 12 Feb '21

12 Feb '21

Hi, For the tomorrow's drivers meeting we have 1 RFE to discuss: * https://bugs.launchpad.net/neutron/+bug/1915151 - [RFE] There should be a way to set ethertype for the vlan_transparent networks Please take a look at it and ask/prepare questions for it to be discussed during the meeting :) If anyone has anything else which would like to discuss, please add it to the "On demand" section at [1]. [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

[oslo] February 15th meeting is canceled
by Herve Beraud 12 Feb '21

12 Feb '21

Hello Osloers, I will be on PTO next Monday so I won't be around to run the meeting. If someone else from the Oslo team wants to run it, please feel free. See you on Tuesday -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[stein][kolla][haproxy] Waiting for virtual ip to appear
by roshan anvekar 12 Feb '21

12 Feb '21

Hi Folks, I am deploying a multinode Openstack cluster using kolla-ansible. *Network composition:* *Bond0: *network_interface/kolla_internal_vip_address *Bond1.101: *kolla_external_vip_address/interface Bond1 also had br-ex ovs bridge configured on it directly. *Bond2: *storage interface With this config I am trying to deploy through kolla. The deployment repeatedly fails at HAproxy: waiting for internal IP to appear or mariadb trying to be active via haproxy. Not sure what's the cause of this. I have given unique keepalive_id too. Generated proper passwords as required by stein. Haproxy is not generating any logs too yet. Any help would be appreciated. Regards, Roshan

2 2

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

11 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 = 172.16.30.46 bind_port = 5555 controller_ip_port_list = 127.0.0.1:5555, 172.16.30.46:5555 #healthcheck_enabled = True [healthcheck] backends = octavia_db_check #debug = true # 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

1 0

Openstack cannot access to the Internet
by Jaime 11 Feb '21

11 Feb '21

# Openstack instances cannot access Internet [linuxbridge] I am having serious issues in the deployment of the Openstack scenario related to the Linux Bridge. This is the scenario: - Controller machine: - Management Interface `enp2s0`: 138.100.10.25. - Compute machine: - Management Interface `enp2s0`: 138.100.10.26. - Provider Interface `enp0s20f0u4`: 138.100.10.27. Openstack Train scenario has been successfully deployed in Centos 8, choosing networking option 2 (self-service network). To verify the functionality, an image has been uploaded, created an Openstack flavor and security group, and launched a couple of cirrOS instances for connection testing. We have created a provider network following [this tutorial](https://docs.openstack.org/newton/install-guide-rdo/launch-instan… and a selfservice network following [this one](https://docs.openstack.org/newton/install-guide-rdo/launch-instance-ne…. The network scenario is the next one: As can be seen in the network topology, an external network 138.100.10.0/21 (provider) and an internal network 192.168.1.1 (selfservice) have been created, connected through a router by the interfaces 138.100.10.198 and 192.168.1.1, both active. Our problem is that our Linux bridge is not working as expected: the Openstack cirrOS instances has no internet access. This is the controller `ip a` and `brctl show` command output: This is the compute `ip a` and `brctl show` command output: (The output of `ovs-vsctl show` command is empty in both machines). **Are the Linux Bridges correctly created?** These are the Linux bridge configuration files: * Controller `/etc/neutron/plugins/ml2/linuxbridge_agent.ini`: ``` [linux_bridge] physical_interface_mappings = provider:enp2s0 # enp2s0 is the interface associated to 138.100.10.25 [vxlan] enable_vxlan = true local_ip = 138.100.10.25 # controller has only 1 IP l2_population = true ``` * Compute `/etc/neutron/plugins/ml2/linuxbridge_agent.ini`: ``` [linux_bridge] physical_interface_mappings = provider:enp0s20f0u4 # interface associated to 138.100.10.26 [vxlan] enable_vxlan = true local_ip = 138.100.10.27 l2_population = true ``` An **observation** to keep in mind is that compute management interface (`138.100.10.26`) is inaccessible from anywhere, which I think is not correct since this prevents us, for example, from accessing the instance console through the URL. I have made some conection tests and these are the results: - There is **connection** between Cirros A and Cirros B (in both directions). - There is **connection** between Cirros A/B and self-service gateway (192.168.1.1) (in both directions). - There is **connection** between Cirros A/B and provider gateway (138.100.10.198) (in both directions). - There is **connection** between Cirros A/B and controller management interface (138.100.10.25) (in both directions). - There is **no connection** between Cirros A/B and compute management interface (138.100.10.26). This interface is not accessible. - There is **connection** between Cirros A/B and compute provider interface (138.100.10.27) (in both directions). I do not know if there is a problem on Linux bridge configuration files, or maybe I need another network interface on controller machine.

3 3

[tripleo][ci] post failures, storage related
by Wesley Hayutin 11 Feb '21

11 Feb '21

FYI.. There is currently an issue w/ the log storage upstream across all openstack jobs it seems. Working w/ infra atm. See #openstack-infra for details Related tracking bug: https://bugs.launchpad.net/tripleo/+bug/1915415 Thanks all! We'll keep you posted.

3 3

[cinder] festival of XS reviews 19 Feb 2021
by Brian Rosmaita 11 Feb '21

11 Feb '21

Hello Cinder community members, At the R-9 mid-cycle yesterday, Eric pointed out that we have a bunch of XS reviews piling up that we should be able to knock out fairly quickly, and either Alan or Jay suggested that we steal the "review jam" idea from the ironic team. So we will hold a Cinder Festival of XS Reviews on Friday next week. what: Cinder Festival of XS Reviews when: Friday 19 February 2021 from 1400-1600 UTC where: https://bluejeans.com/3228528973 See you there! brian

1 0

[tripleo] next irc meeting Tuesday Feb 16 @ 1400 UTC in #tripleo
by Marios Andreou 11 Feb '21

11 Feb '21

Reminder that the next TripleO irc meeting is: ** Tuesday 16 February at 1400 UTC in #tripleo ** ** https://wiki.openstack.org/wiki/Meetings/TripleO ** ** https://etherpad.opendev.org/p/tripleo-meeting-items ** Please add anything you want to hilight at https://etherpad.opendev.org/p/tripleo-meeting-items This can include recently completed things, ongoing review requests, blocking issues, or anything else tripleo you'd like to share. Our last meeting was on Feb 02 - you can find the logs there http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-02-02-14.… Hope you can make it on Tuesday, thanks, marios

1 0

[tripleo][ci] socializing upstream job removal ( master upgrade, scenario010 )
by Wesley Hayutin 11 Feb '21

11 Feb '21

Greetings, Expect to see several of these emails as we propose additional items to reduce the upstream resource footprint of TripleO. The intent of the email is to broadcast our general intent regarding specific ci jobs with some details regarding the how and when things will happen. Expect jobs to be removed in a staged pragmatic manner. Historical Context [1] Please feel free to respond to this thread with your opinions. Summary: First stage of TripleO's job reduction will be to remove most TripleO upgrade jobs on master and remove all scenario010 octavia jobs from upstream. *Upgrade jobs in master:* All the upgrade jobs in master are non-voting based on policy and to give the upgrade developers time to compensate for new developments and features. The feedback provided by CI can still occur in our periodic jobs in RDO's software factory zuul. Upgrade jobs will remain running in periodic but removed from upstream. Specifically: ( master ) tripleo-ci-centos-8-standalone-upgrade tripleo-ci-centos-8-undercloud-upgrade tripleo-ci-centos-8-scenario000-multinode-oooq-container-upgrades I'll note there is interest in keeping the undercloud-upgrade, however we are able to remove all the upgrade jobs for a branch in the upstream we can also remove a content-provider job. I would encourage folks to consider undercloud-upgrade for periodic only. *Scenario010 - Octavia:* Scenario010 octavia has been non-voting and not passing at a high enough rate [2] to justify the use of upstream resources. I would propose we only run these jobs in the periodic component and integration lines in RDO softwarefactory. Specifically: ( all branches ) tripleo-ci-centos-8-scenario010-ovn-provider-standalone tripleo-ci-centos-8-scenario010-standalone Please review and comment. The CI team will start taking action on these two items in one week. Thank you! [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020235… [2] http://dashboard-ci.tripleo.org/d/iEDLIiOMz/non-voting-jobs?orgId=1&from=no…

6 6

Openstack instances cannot access to Internet [linuxbridge]
by Jaime 11 Feb '21

11 Feb '21

I am having serious issues in the deployment of the Openstack scenario related to the Linux Bridge. This is the scenario: - Controller machine: - Management Interface `enp2s0`: 138.100.10.25. - Compute machine: - Management Interface `enp2s0`: 138.100.10.26. - Provider Interface `enp0s20f0u4`: 138.100.10.27. Openstack Train scenario has been successfully deployed in Centos 8, choosing networking option 2 (self-service network). To verify the functionality, an image has been uploaded, created an Openstack flavor and security group, and launched a couple of cirrOS instances for connection testing. We have created a provider network following [this tutorial](https://docs.openstack.org/newton/install-guide-rdo/launch-instan… and a selfservice network following [this one](https://docs.openstack.org/newton/install-guide-rdo/launch-instance-ne…. The network scenario is the next one: As can be seen in the network topology, an external network 138.100.10.0/21 (provider) and an internal network 192.168.1.1 (selfservice) have been created, connected through a router by the interfaces 138.100.10.198 and 192.168.1.1, both active. Our problem is that our Linux bridge is not working as expected: the Openstack cirrOS instances has no internet access. This is the controller `ip a` and `brctl show` command output: ``` [upm@modena ~]$ 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: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master brq84f65ccb-c9 state UP group default qlen 1000 link/ether 24:4b:fe:7c:78:b8 brd ff:ff:ff:ff:ff:ff 3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:15:5b:02 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 4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:15:5b:02 brd ff:ff:ff:ff:ff:ff 17: tapa467f377-b1@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master brq84f65ccb-c9 state UP group default qlen 1000 link/ether d6:90:e8:fe:90:23 brd ff:ff:ff:ff:ff:ff link-netns qdhcp-84f65ccb-c945-437b-9013-9c71422bb10e 18: brq84f65ccb-c9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 24:4b:fe:7c:78:b8 brd ff:ff:ff:ff:ff:ff inet 138.100.10.25/21 brd 138.100.15.255 scope global brq84f65ccb-c9 valid_lft forever preferred_lft forever inet6 fe80::6c31:4cff:fe2d:7820/64 scope link valid_lft forever preferred_lft forever 19: tap7a390547-5b@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master brqd811bcfa-94 state UP group default qlen 1000 link/ether 26:6d:a4:fc:73:51 brd ff:ff:ff:ff:ff:ff link-netns qdhcp-d811bcfa-945a-4633-9266-60ccafa28d86 20: vxlan-1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master brqd811bcfa-94 state UNKNOWN group default qlen 1000 link/ether fa:cb:4e:e2:83:46 brd ff:ff:ff:ff:ff:ff 21: brqd811bcfa-94: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000 link/ether 12:a8:05:bf:98:98 brd ff:ff:ff:ff:ff:ff inet6 fe80::88c2:ecff:fe72:761f/64 scope link valid_lft forever preferred_lft forever 22: tap3eb4fbcf-41@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master brqd811bcfa-94 state UP group default qlen 1000 link/ether 12:a8:05:bf:98:98 brd ff:ff:ff:ff:ff:ff link-netns qrouter-278c944f-7e75-4a93-affe-b9ff93f4c6a5 23: tapfd2dca1f-f7@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master brq84f65ccb-c9 state UP group default qlen 1000 link/ether 86:cc:64:22:4d:db brd ff:ff:ff:ff:ff:ff link-netns qrouter-278c944f-7e75-4a93-affe-b9ff93f4c6a5 [upm@modena ~]$ brctl show bridge name bridge id STP enabled interfaces brq84f65ccb-c9 8000.244bfe7c78b8 no enp2s0 tapa467f377-b1 tapfd2dca1f-f7 brqd811bcfa-94 8000.12a805bf9898 no tap3eb4fbcf-41 tap7a390547-5b vxlan-1 virbr0 8000.525400155b02 yes virbr0-nic ``` This is the compute `ip a` and `brctl show` command output: ```shell [upm@testarossa ~]$ 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: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 24:4b:fe:7c:79:a0 brd ff:ff:ff:ff:ff:ff inet 138.100.10.26/21 brd 138.100.15.255 scope global noprefixroute enp2s0 valid_lft forever preferred_lft forever inet6 fe80::c461:f832:d690:c0a7/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: enp0s20f0u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master brq84f65ccb-c9 state UP group default qlen 1000 link/ether 00:e0:4c:53:44:58 brd ff:ff:ff:ff:ff:ff inet6 fe80::ecff:62cc:d9e1:2e53/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:66:84:5a 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 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:66:84:5a brd ff:ff:ff:ff:ff:ff 6: brqd811bcfa-94: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000 link/ether 8e:94:21:5b:dc:f4 brd ff:ff:ff:ff:ff:ff inet 138.100.10.27/21 brd 138.100.15.255 scope global noprefixroute brqd811bcfa-94 valid_lft forever preferred_lft forever 7: brq84f65ccb-c9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:e0:4c:53:44:58 brd ff:ff:ff:ff:ff:ff inet 138.100.10.27/21 brd 138.100.15.255 scope global brq84f65ccb-c9 valid_lft forever preferred_lft forever 9: tap9d1c0de6-96: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc fq_codel master brqd811bcfa-94 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:7d:14:63 brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe7d:1463/64 scope link valid_lft forever preferred_lft forever 10: tapaf15e2f0-24: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master brq84f65ccb-c9 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:91:6d:ef brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe91:6def/64 scope link valid_lft forever preferred_lft forever 11: vxlan-1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master brqd811bcfa-94 state UNKNOWN group default qlen 1000 link/ether 8e:94:21:5b:dc:f4 brd ff:ff:ff:ff:ff:ff 13: tapef3e95d6-7c: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc fq_codel master brqd811bcfa-94 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:91:d1:1d brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe91:d11d/64 scope link valid_lft forever preferred_lft forever 14: tap1a5d77c0-d4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master brq84f65ccb-c9 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:4f:da:0f brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe4f:da0f/64 scope link valid_lft forever preferred_lft forever 15: tap792bf660-2f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc fq_codel master brqd811bcfa-94 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:f1:df:5f brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fef1:df5f/64 scope link valid_lft forever preferred_lft forever 16: tapf42b8b2f-be: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master brq84f65ccb-c9 state UNKNOWN group default qlen 1000 link/ether fe:16:3e:9e:46:bb brd ff:ff:ff:ff:ff:ff inet6 fe80::fc16:3eff:fe9e:46bb/64 scope link valid_lft forever preferred_lft forever [upm@testarossa ~]$ brctl show bridge name bridge id STP enabled interfaces brq84f65ccb-c9 8000.00e04c534458 no enp0s20f0u4 tap1a5d77c0-d4 tapaf15e2f0-24 tapf42b8b2f-be brqd811bcfa-94 8000.8e94215bdcf4 no tap792bf660-2f tap9d1c0de6-96 tapef3e95d6-7c vxlan-1 virbr0 8000.52540066845a yes virbr0-nic ``` (The output of `ovs-vsctl show` command is empty in both machines). **Are the Linux Bridges correctly created?** These are the Linux bridge configuration files: * Controller `/etc/neutron/plugins/ml2/linuxbridge_agent.ini`: ``` [linux_bridge] physical_interface_mappings = provider:enp2s0 # enp2s0 is the interface associated to 138.100.10.25 [vxlan] enable_vxlan = true local_ip = 138.100.10.25 # controller has only 1 IP l2_population = true ``` * Compute `/etc/neutron/plugins/ml2/linuxbridge_agent.ini`: ``` [linux_bridge] physical_interface_mappings = provider:enp0s20f0u4 # interface associated to 138.100.10.26 [vxlan] enable_vxlan = true local_ip = 138.100.10.27 l2_population = true ``` An **observation** to keep in mind is that compute management interface (`138.100.10.26`) is inaccessible from anywhere, which I think is not correct since this prevents us, for example, from accessing the instance console through the URL. I have made some conection tests and these are the results: * Cirros_a `ip a` command output: ``` $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1 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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:91:d1:1d brd ff:ff:ff:ff:ff:ff inet 192.168.1.222/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fe91:d11d/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether fa:16:3e:4f:da:0f brd ff:ff:ff:ff:ff:ff ``` * Cirros_b `ip a` command output: ``` $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1 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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast qlen 1000 link/ether fa:16:3e:f1:df:5f brd ff:ff:ff:ff:ff:ff inet 192.168.1.30/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::f816:3eff:fef1:df5f/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether fa:16:3e:9e:46:bb brd ff:ff:ff:ff:ff:ff ``` - There is **connection** between Cirros A and Cirros B (in both directions). - There is **connection** between Cirros A/B and self-service gateway (192.168.1.1) (in both directions). - There is **connection** between Cirros A/B and provider gateway (138.100.10.198) (in both directions). - There is **connection** between Cirros A/B and controller management interface (138.100.10.25) (in both directions). - There is **no connection** between Cirros A/B and compute management interface (138.100.10.26). This interface is not accessible. - There is **connection** between Cirros A/B and compute provider interface (138.100.10.27) (in both directions). I do not know if there is a problem on linux bridge configuration files, or maybe I need another network interface on controller machine.

1 0

Openstack instances cannot access to Internet [linuxbridge]
by Jaime 11 Feb '21

11 Feb '21

I am having serious issues in the deployment of the Openstack scenario related to the Linux Bridge. This is the scenario: - Controller machine: - Management Interface `enp2s0`: 138.100.10.25. - Compute machine: - Management Interface `enp2s0`: 138.100.10.26. - Provider Interface `enp0s20f0u4`: 138.100.10.27. Openstack Train scenario has been successfully deployed in Centos 8, choosing networking option 2 (self-service network). To verify the functionality, an image has been uploaded, created an Openstack flavor and security group, and launched a couple of cirrOS instances for connection testing. We have created a provider network following [this tutorial](https://docs.openstack.org/newton/install-guide-rdo/launch-instan… and a selfservice network following [this one](https://docs.openstack.org/newton/install-guide-rdo/launch-instance-ne…. The network scenario is the next one: As can be seen in the network topology, an external network 138.100.10.0/21 (provider) and an internal network 192.168.1.1 (selfservice) have been created, connected through a router by the interfaces 138.100.10.198 and 192.168.1.1, both active. Our problem is that our Linux bridge is not working as expected: the Openstack cirrOS instances has no internet access. This is the controller `ip a` and `brctl show` command output: This is the compute `ip a` and `brctl show` command output: (The output of `ovs-vsctl show` command is empty in both machines). **Are the Linux Bridges correctly created?** These are the Linux bridge configuration files: * Controller `/etc/neutron/plugins/ml2/linuxbridge_agent.ini`: ``` [linux_bridge] physical_interface_mappings = provider:enp2s0 # enp2s0 is the interface associated to 138.100.10.25 [vxlan] enable_vxlan = true local_ip = 138.100.10.25 # controller has only 1 IP l2_population = true ``` * Compute `/etc/neutron/plugins/ml2/linuxbridge_agent.ini`: ``` [linux_bridge] physical_interface_mappings = provider:enp0s20f0u4 # interface associated to 138.100.10.26 [vxlan] enable_vxlan = true local_ip = 138.100.10.27 l2_population = true ``` An **observation** to keep in mind is that compute management interface (`138.100.10.26`) is inaccessible from anywhere, which I think is not correct since this prevents us, for example, from accessing the instance console through the URL. I have made some conection tests and these are the results: * Cirros_a `ip a` command output: * Cirros_b `ip a` command output: - There is **connection** between Cirros A and Cirros B (in both directions). - There is **connection** between Cirros A/B and self-service gateway (192.168.1.1) (in both directions). - There is **connection** between Cirros A/B and provider gateway (138.100.10.198) (in both directions). - There is **connection** between Cirros A/B and controller management interface (138.100.10.25) (in both directions). - There is **no connection** between Cirros A/B and compute management interface (138.100.10.26). This interface is not accessible. - There is **connection** between Cirros A/B and compute provider interface (138.100.10.27) (in both directions). I do not know if there is a problem on linux bridge configuration files, or maybe I need another network interface on controller machine.

1 0

[stein][neutron][vlan provider network] How to configure br-ex on virtual interface
by roshan anvekar 11 Feb '21

11 Feb '21

Hello, Below is my scenario. I am trying to use a single physical bonded interface ( example: bond1) both for external TLS access traffic and for provider network too ( These are 2 different vlan networks with separate vlan ids) . Bond0 is used as api_interface for management traffic. Bond2 is used for storage traffic. For this I created 2 virtual interfaces on this bond1 and used it accordingly while deploying through kolla-ansible. Before deployment the gateways for both vlan networks were accessible. Post deployment I see that qdhcp-id router is created on one of the controllers. Post creation of this DHCP agent, the gateway is inaccessible. Also the vms created are not getting IPs through DHCP agent so failing to be accessible. I had configured br-ex on virtual interface of provider vlan network and not on physical interface directly. Please let me know if I am going wrong in my network configurations. Regards, Roshan

3 4

[ironic] [release] [kolla] RFC: stop doing Extended Maintenance for Bifrost
by Dmitry Tantsur 11 Feb '21

11 Feb '21

Hi all, Since Bifrost is an installation project that supports several distributions, maintaining its stable branches is a never ending nightmare. We have *nearly* fixed Ussuri (thank you Riccardo!) and just started looking into Train (thank you Iury and Mark), I'm sure we cannot keep EM branches in a decent shape. Personally I feel that Bifrost is more geared towards consumers staying close to master, but my gut feeling may not necessarily match the reality. Based on the above, I'm proposing: 1) EOL all old branches from Ocata to Stein on Bifrost. 2) No longer create EM branches, EOL immediately after a branch leaves the regular maintenance. Opinions? Dmitry P.S. Adding kolla because of a potential impact. -- 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

3 4

[cinder] wallaby R-9 mid-cycle summary available
by Brian Rosmaita 10 Feb '21

10 Feb '21

In case you missed the exciting cinder R-9 virtual mid-cycle session (held yesterday or earlier today depending on where you are) I've posted a summary: https://wiki.openstack.org/wiki/CinderWallabyMidCycleSummary It will eventually include a link to the recording (in case you want to see what you missed or if you want to re-live the excitement). cheers, brian

1 0

bootstrap errors in OSA installation in CentOS 8.3
by Amey Abhyankar 10 Feb '21

10 Feb '21

Hello, I am trying to configure deployment host by referring following guide =https://docs.openstack.org/project-deploy-guide/openstack-ansible/victoria/deploymenthost.html # dnf install https://repos.fedorapeople.org/repos/openstack/openstack-victoria/rdo-relea… # dnf install git chrony openssh-server python3-devel sudo # dnf group install "Development Tools" # git clone -b 22.0.0.0rc1 https://opendev.org/openstack/openstack-ansible /opt/openstack-ansible # scripts/bootstrap-ansible.sh [ after executing this command, I am getting errors. Attaching sample error] ------------------------------------------------- hs will be added later\\n --pathspec-from-file <file>\\n read pathspec from file\\n --pathspec-file-nul with --pathspec-from-file, pathspec elements are separated with NUL character\\n'\"], [\"Role {'name': 'os_ironic', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-os_ironic', 'version': '67733c8f0cb13c467eb10f256a93d878c56d4743', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/os_ironic'} failed after 2 retries\\n\"], [\"Role {'name': 'os_cinder', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-os_cinder', 'version': '00a38c6584c09168faad135f10d265ad9c86efba', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/os_cinder'} failed after 2 retries\\n\"], [\"Role {'name': 'lxc_hosts', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-lxc_hosts', 'version': 'b3bff3289ac2e9510be81f562f6d35500ac47723', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/lxc_hosts'} failed after 2 retries\\n\"], [\"Role {'name': 'rsyslog_client', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-rsyslog_client', 'version': 'd616af7883bd6e7a208be3a4f56d129bc2aa92ca', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/rsyslog_client'} failed after 2 retries\\n\"], [\"Role {'name': 'openstack_openrc', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-openstack_openrc', 'version': '242772e99978fe9cd3c50b5b40d5637833f38beb', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/openstack_openrc'} failed after 2 retries\\n\"], [\"Role {'name': 'os_ceilometer', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-os_ceilometer', 'version': '6df1fb0fc5610c2f317b5085188b0a60346e7111', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/os_ceilometer'} failed after 2 retries\\n\"], [\"Failed to reset /etc/ansible/roles/os_keystone\\nCmd('git') failed due to: exit code(129)\\n cmdline: git reset --force --hard f1625b38a820dd51cffa66141053a836211695dc\\n stderr: 'error: unknown option `force'\\nusage: git reset [--mixed | --soft | --hard | --merge | --keep] [-q] [<commit>]\\n or: git reset [-q] [<tree-ish>] [--] <pathspec>...\\n or: git reset [-q] [--pathspec-from-file [--pathspec-file-nul]] [<tree-ish>]\\n or: git reset --patch [<tree-ish>] [--] [<pathspec>...]\\n\\n -q, --quiet be quiet, only report errors\\n --mixed reset HEAD and index\\n --soft reset only HEAD\\n --hard reset HEAD, index and working tree\\n --merge reset HEAD, index and working tree\\n --keep reset HEAD but keep local changes\\n --recurse-submodules[=<reset>]\\n control recursive updating of submodules\\n -p, --patch select hunks interactively\\n -N, --intent-to-add record only the fact that removed paths will be added later\\n --pathspec-from-file <file>\\n read pathspec from file\\n --pathspec-file-nul with --pathspec-from-file, pathspec elements are separated with NUL character\\n'\"], [\"Role {'name': 'openstack_hosts', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-openstack_hosts', 'version': '8ab8503a15ad5cfe504777647922be301ddac911', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/openstack_hosts'} failed after 2 retries\\n\"], [\"Role {'name': 'os_sahara', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-os_sahara', 'version': '0f9e76292461a5532f6d43927b71ab9fff692dd5', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/os_sahara'} failed after 2 retries\\n\"], [\"Role {'name': 'os_tempest', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-os_tempest', 'version': '49004fb05fa491275848a07020a36d4264ab6d49', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/os_tempest'} failed after 2 retries\\n\"], [\"Role {'name': 'ceph-ansible', 'scm': 'git', 'src': 'https://github.com/ceph/ceph-ansible', 'version': '7d088320df1c4a6ed458866c61616a21fddccfe8', 'trackbranch': 'stable-5.0', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/ceph-ansible'} failed after 2 retries\\n\"], [\"Role {'name': 'galera_server', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-galera_server', 'version': '0b853b1da7802f6fac8da309c88886186f6a15a6', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/galera_server'} failed after 2 retries\\n\"], [\"Role {'name': 'os_nova', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-os_nova', 'version': '43b1b62f22b47e3148adcc4cd2396a4e29522e9b', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/os_nova'} failed after 2 retries\\n\"], [\"Role {'name': 'os_keystone', 'scm': 'git', 'src': 'https://opendev.org/openstack/openstack-ansible-os_keystone', 'version': 'f1625b38a820dd51cffa66141053a836211695dc', 'trackbranch': 'stable/victoria', 'path': '/etc/ansible/roles', 'refspec': None, 'depth': 10, 'dest': '/etc/ansible/roles/os_keystone'} failed after 2 retries\\n\"]]\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1} PLAY RECAP ****************************************************************************************************************************************************************************************** localhost : ok=4 changed=0 unreachable=0 failed=1 skipped=8 rescued=0 ignored=0 ++ exit_fail 405 0 ++ set +x Last metadata expiration check: 2:12:54 ago on Wed 10 Feb 2021 01:34:28 PM IST. Package iproute-5.3.0-5.el8.x86_64 is already installed. Dependencies resolved. Nothing to do. Complete! Failed to get DNSSEC supported state: Unit dbus-org.freedesktop.resolve1.service not found. which: no lxc-ls in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) which: no lxc-checkconfig in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) which: no networkctl in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) [WARNING]: Skipping callback plugin '/dev/null', unable to load which: no btrfs in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin :/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) which: no btrfs in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin :/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) which: no zfs in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/ usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin) ++ info_block 'Error Info - 405' 0 ++ echo ---------------------------------------------------------------------- ---------------------------------------------------------------------- ++ print_info 'Error Info - 405' 0 ++ PROC_NAME='- [ Error Info - 405 0 ] -' ++ printf '\n%s%s\n' '- [ Error Info - 405 0 ] -' ------------------------------ -------------- - [ Error Info - 405 0 ] --------------------------------------------- ++ echo ---------------------------------------------------------------------- ---------------------------------------------------------------------- ++ exit_state 1 ++ set +x ---------------------------------------------------------------------- - [ Run Time = 163 seconds || 2 minutes ] ---------------------------- ---------------------------------------------------------------------- ---------------------------------------------------------------------- - [ Status: Failure ] ------------------------------------------------ ---------------------------------------------------------------------- Pls suggest how to fix these issues thanks. Regards, Amey.

2 4

[baremetal-sig][ironic] Tue Feb 9, 2021, 2pm UTC: Deploy Steps in Ironic
by Arne Wiebalck 10 Feb '21

10 Feb '21

Dear all, The Bare Metal SIG will meet tomorrow Tue Feb 9, 2021 at 2pm UTC on zoom. This time there will be a 10 minute "topic-of-the-day" presentation by Dmitry Tantsur (dtansur) on: 'An Introduction to Deploy Steps in Ironic' If you've never found the time to understand what deploy steps are and how they are useful, this is your chance to hear it from one of the experts! You can find all the details for this meeting on the SIG's etherpad: https://etherpad.opendev.org/p/bare-metal-sig Everyone is welcome, don't miss out! Cheers, Arne

2 1

[charms] OpenStack Charms 21.01 release is now available
by Peter Matulis 10 Feb '21

10 Feb '21

The 21.01 release of the OpenStack Charms is now available. This release brings several new features to the existing OpenStack Charms deployments for Queens, Rocky, Stein, Train, Ussuri, Victoria and many stable combinations of Ubuntu + OpenStack. Please see the Release Notes for full details: https://docs.openstack.org/charm-guide/latest/2101.html == Highlights == * Cinder-Ceph - Image mirroring The cinder-ceph charm now supports image replication to a second Ceph cluster. * Ironic charms Three new tech-preview charms are now available for the deployment of OpenStack Ironic. Ironic provisions bare metal machines, as opposed to virtual machines. * Glance multi-backend usage When multiple storage backends are used with Glance, the glance charm now supports the CLI Glance client option (--store) that enables an operator to specify, at image upload time, which backend will be used to store the image. * Documentation updates Ongoing improvements to the OpenStack Charms Deployment Guide, the OpenStack Charm Guide, and the charm READMEs. * Trusty series deprecation The ‘trusty’ series is no longer actively tested and is now EOL in terms of bug fixes for the OpenStack charms. == OpenStack Charms team == The OpenStack Charms team can be contacted on the #openstack-charms IRC channel on Freenode. == Thank you == Lots of thanks to the below 33 contributors who squashed 52 bugs, enabled new features, and improved the documentation! Alex Kavanagh Alvaro Uria Andrea Ieri Arif Ali Aurelien Lourot Billy Olsen Corey Bryant David Ames Dmitrii Shcherbakov Dongdong Tao Edward Hope-Morley Eric Desrochers Felipe Reyes Frode Nordahl Gabriel Samfira Garrett Thompson Giuseppe Petralia Hemanth Nakkina Ioanna Alifieraki Ionut Balutoiu Jarred Wilson Liam Young Linda Guo Marius Oprin Martin Fiala Martin Kalcok Peter Matulis Peter Sabaini Ponnuvel Palaniyappan Robert Gildein Rodrigo Barbieri Trent Lloyd Xav Paice -- OpenStack Charms Team

1 0

[release] Proposing Előd Illés (elod) for Release Management Core
by Herve Beraud 10 Feb '21

10 Feb '21

Hi, Előd has been working on Release management for quite some time now and in that time has shown tremendous growth in his understanding of our processes and on how deliverables work on Openstack. I think he would make a good addition to the core team. Existing team members, please respond with +1/-1. If there are no objections we'll add him to the ACL soon. :-) Thanks. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

5 5

[QA] Migrate from testr to stestr
by Martin Kopec 10 Feb '21

10 Feb '21

Hi everyone, testr unit test runner (testrepository package [1]) hasn't been updated for years, therefore during Shanghai PTG [2] we came up with an initiative to migrate from testr to stestr (testr's successor) [3] unit test runner. Here is an etherpad which tracks the effort [4]. However as there is still quite a number of the projects which haven't migrated, we would like to kindly ask you for your help. If you are a maintainer of a project which is mentioned in the etherpad [4] and it's not crossed out yet, please migrate to stestr. [1] https://pypi.org/project/testrepository/ [2] https://etherpad.opendev.org/p/shanghai-ptg-qa [3] https://pypi.org/project/stestr/ [4] https://etherpad.opendev.org/p/enkM4eeDHObSloTjPGAu Have a nice day, -- Martin Kopec Software Quality Engineer Red Hat EMEA <https://www.redhat.com> <https://red.ht/sig>

6 5

[nova] Rescue booting on wrong disk
by Arnaud Morin 10 Feb '21

10 Feb '21

Hey all, >From time to time we are facing an issue when puting instance in rescue with the same image as the one the instance was booted. E.G. I booted an instance using Debian 10, disk are: debian@testarnaud:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 486K 0 rom vda 254:0 0 10G 0 disk └─vda1 254:1 0 10G 0 part / debian@testarnaud:~$ cat /etc/fstab # /etc/fstab: static file system information. UUID=5605171d-d590-46d5-85e2-60096b533a18 / ext4 errors=remount-ro 0 1 I rescued the instance: $ openstack server rescue --image bc73a901-6366-4a69-8ddc-00479b4d647f testarnaud Then, back in the instance: debian@testarnaud:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 486K 0 rom vda 254:0 0 2G 0 disk └─vda1 254:1 0 2G 0 part vdb 254:16 0 10G 0 disk └─vdb1 254:17 0 10G 0 part / Instance booted on /dev/vdb1 instead of /dev/vda1 Is there anything we can configure on nova side to avoid this situation? Thanks -- Arnaud Morin

4 3

[cinder][ceph] improving storage latency
by Ionut Biru 10 Feb '21

10 Feb '21

Hi guys, Currently in one locations we have the underlay for ceph running over tcp ip with solarflare networking cards attached to 40G switches. We use OSA to deploy openstack and we follow their network layout e.g br-storage. 3 nodes with mixed storage type, ssd and hdd. We want to deploy a new ceph cluster in a new region but we want to improve our ceph installation overlay to have lower latency. What do you guys use in your infrastructure? -- Ionut Biru - https://fleio.com

1 0

[largescale-sig] OpenStack DB Archiver
by Arnaud Morin 10 Feb '21

10 Feb '21

Hello large-scalers! TLDR: we opensource a tool to help reducing size of databases. See https://github.com/ovh/osarchiver/ Few months ago, we released a tool, name osarchiver, which we are using on our production environment (at OVH) to help reduce the size of our tables in mariadb (or mysql) In fact, some tables are well know to grow very quickly. We use it, for example, to clean the OpenStack mistral database from old tasks, actions and executions which are older than a year. Another use case could be to archive some data in another table (e.g. with _archived as suffix) if they are 6 months old, and delete this data after 1 year. The source code of this tool is available here: https://github.com/ovh/osarchiver/ We were wondering if some other users would be interested in using the tool, and maybe move it under the opendev governance? Feel free to contact us and/or answer this thread. Cheers, -- Arnaud, Pierre-Samuel and OVH team

12 18

[cinder] wallaby new driver - kioxia kumoscale
by Brian Rosmaita 09 Feb '21

09 Feb '21

I'm proposing that we extend the wallaby new driver merge deadline for the kioxia kumoscale driver to Friday 12 February 2021 to give the reviewers who committed to reviewing the patches at the cinder meeting last week [0] time to complete their reviews of the driver [1] and os-brick [2] changes. The Kioxia 3rd party CI is running and responding to patches, and the dev team has been very responsive to reviews and posted revisions quickly. This extension past the standing Milestone-2 deadline for new drivers is due to limited review bandwidth this cycle which I am attributing to stress caused by the ongoing pandemic, so this should not be considered a precedent applicable to new drivers proposed for future releases. If you have comments or concerns about this proposal, please respond to this email so we can discuss at the virtual mid-cycle meeting tomorrow. And if you have committed to reviewing one of the patches and have not done it yet, please review as soon as possible! cheers, brian [0] http://eavesdrop.openstack.org/meetings/cinder/2021/cinder.2021-02-03-14.00… [1] https://review.opendev.org/c/openstack/cinder/+/768574 [2] https://review.opendev.org/c/openstack/os-brick/+/768575

1 0

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

09 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 - Retire tempest-horizon https://review.opendev.org/c/openstack/governance/+/774379 - Cool-down cycle goal https://review.opendev.org/c/openstack/governance/+/770616 - 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 ## Project Updates - Remove Karbor project team https://review.opendev.org/c/openstack/governance/+/767056 - Create ansible-role-pki repo https://review.opendev.org/c/openstack/governance/+/773383 - Add rbd-iscsi-client to cinder project https://review.opendev.org/c/openstack/governance/+/772597 ## General Changes - Define Xena release testing runtime https://review.opendev.org/c/openstack/governance/+/770860 - [manila] add assert:supports-api-interoperability https://review.opendev.org/c/openstack/governance/+/770859 - Define 2021 upstream investment opportunities https://review.opendev.org/c/openstack/governance/+/771707 # Other Reminders - Our next [TC] Weekly meeting is scheduled for February 11th 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 10th, 2100 UTC. Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[cinder] reminder: wallaby R-9 virtual mid-cycle tomorrow (wednesday)
by Brian Rosmaita 09 Feb '21

09 Feb '21

Reminder: no cinder meeting tomorrow, instead we're having a virtual mid-cycle meeting: DATE: Wednesday, 10 February 2021 TIME: 1400-1600 UTC (2 hours) LOCATION: https://bluejeans.com/3228528973 The meeting will be recorded. Topics are on the planning etherpad. (For people who have been procrastinating, there's probably room for one or two more topics.) https://etherpad.opendev.org/p/cinder-wallaby-mid-cycles cheers, brian

1 0

[stein][manila] share migration misconfiguration ?
by Ignazio Cassano 09 Feb '21

09 Feb '21

Hello All, I am trying to migrate a share between a netapp backend to another. Both backends are configured in my manila.conf. I am able to create share on both, but I am not able to migrate share between them. I am using DSSH=False. I did not understand how host and driver assisted migration work and what "data_node_access_ip" means. The share I want to migrate is on a network (10.102.186.0/24) that I can reach by my management controllers network (10.102.184.0/24). I Can mount share from my controllers and I can mount also the netapp SVM where the share is located. So in the data_node_access_ip I wrote the list of my controllers management ips. During the migrate phase I checked if my controller where manila is running mounts the share or the netapp SVM but It does not happen. Please, what is my mistake ? Thanks Ignazio

3 17

[nova][placement] adding nova-core to placement-core in gerrit
by Balazs Gibizer 09 Feb '21

09 Feb '21

Hi, Placement got back under nova governance but so far we haven't consolidated the core teams yet. Stephen pointed out to me that given the ongoing RBAC works it would be beneficial if more nova cores, with API and RBAC experience, could approve such patches. So I'm proposing to add nova-core group to the placement-core group in gerrit. This means Ghanshyam, John, Lee, and Melanie would get core rights in the placement related repositories. @placement-core, @nova-core members: Please let me know if you have any objection to such change until end of this week. cheers, gibi

6 9

[kolla] Stein base container build fails
by Eric K. Miller 08 Feb '21

08 Feb '21

Hi, I'm trying to update a few things in a Stein cluster and while building some kolla containers, I get the following error when building the base container: INFO:kolla.common.utils.openstack-base:Step 4/8 : RUN curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py && python get-pip.py && rm get-pip.py INFO:kolla.common.utils.openstack-base: ---> Running in f5c8bb3fe6f0 INFO:kolla.common.utils.openstack-base:curl (https://bootstrap.pypa.io/get-pip.py) response: 200, time: 0.423, size: 1929903 INFO:kolla.common.utils.openstack-base:Traceback (most recent call last): INFO:kolla.common.utils.openstack-base: File "get-pip.py", line 24244, in <module> INFO:kolla.common.utils.openstack-base: INFO:kolla.common.utils.openstack-base: main() INFO:kolla.common.utils.openstack-base: File "get-pip.py", line 199, in main INFO:kolla.common.utils.openstack-base: bootstrap(tmpdir=tmpdir) INFO:kolla.common.utils.openstack-base: File "get-pip.py", line 82, in bootstrap INFO:kolla.common.utils.openstack-base: from pip._internal.cli.main import main as pip_entry_point INFO:kolla.common.utils.openstack-base: File "/tmp/tmpDXRruf/pip.zip/pip/_internal/cli/main.py", line 60 INFO:kolla.common.utils.openstack-base: sys.stderr.write(f"ERROR: {exc}") INFO:kolla.common.utils.openstack-base: INFO:kolla.common.utils.openstack-base: ^ INFO:kolla.common.utils.openstack-base:SyntaxError: invalid syntax INFO:kolla.common.utils.openstack-base: INFO:kolla.common.utils.openstack-base:Removing intermediate container f5c8bb3fe6f0 ERROR:kolla.common.utils.openstack-base:Error'd with the following message ERROR:kolla.common.utils.openstack-base:The command '/bin/sh -c curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py && python get-pip.py && rm get-pip.py' returned a non-zero code: 1 Any ideas as to where the issue is? Is this a pip installer bug? Eric

2 1

[ironic] On redfish-virtual-media vs idrac-redfish-virtual-media
by Dmitry Tantsur 08 Feb '21

08 Feb '21

Hi all, Now that we've gained some experience with using Redfish virtual media I'd like to reopen the discussion about $subj. For the context, the idrac-redfish-virtual-media boot interface appeared because Dell machines need an additional action [1] to boot from virtual media. The initial position on hardware interfaces was that anything requiring OEM actions must go into a vendor hardware interface. I would like to propose relaxing this (likely unwritten) rule. You see, this distinction causes a lot of confusion. Ironic supports Redfish, ironic supports iDRAC, iDRAC supports Redfish, ironic supports virtual media, Redfish supports virtual media, iDRAC supports virtual media. BUT! You cannot use redfish-virtual-media with iDRAC. Just today I had to explain the cause of it to a few people. It required diving into how exactly Redfish works and how exactly ironic uses it, which is something we want to protect our users from. We already have a precedent [2] of adding vendor-specific handling to a generic driver. I have proposed a patch [3] to block using redfish-virtual-media for Dell hardware, but I grew to dislike this approach. It does not have precedents in the ironic code base and it won't scale well if we have to handle vendor differences for vendors that don't have ironic drivers. Based on all this I suggest relaxing the rule to the following: if a feature supported by a generic hardware interface requires additional actions or has a minor deviation from the standard, allow handling it in the generic hardware interface. Meaning, redfish-virtual-media starts handling the Dell case by checking the System manufacturer (via the recently added detect_vendor call) and loading the OEM code if it matches "Dell". After this idrac-redfish-virtual-media will stay empty (for future enhancements and to make the patch backportable). Thoughts? Dmitry [1] https://opendev.org/openstack/ironic/src/commit/6ea73bdfbb53486cf9905d21024… [2] https://review.opendev.org/c/openstack/ironic/+/757198/ [3] https://review.opendev.org/c/openstack/ironic/+/771619 -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

5 7

[TripleO] Fwd: Planned outage of review.rdoproject.org: 2021-02-11 from 14:00 to 18:00 UTC
by Nicolas Hicher 08 Feb '21

08 Feb '21

-------- Forwarded Message -------- From: Nicolas Hicher <nhicher(a)redhat.com> Subject: Planned outage of review.rdoproject.org: 2021-02-11 from 14:00 to 18:00 UTC To: dev(a)lists.rdoproject.org Message-ID: <891d4c95-0f55-3452-d0b5-54a54aab0941(a)redhat.com> Date: Mon, 8 Feb 2021 17:31:36 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Hello folks, Our cloud provider plans to do maintainance operation on 2021-02-11 from 14:00 to 18:00 UTC. Service interruption is expected, including: - Zuul CI not running jobs for gerrit, github or opendev. - RDO Trunk not building new packages. - DLRN API. - review.rdoproject.org and softwarefactory-project.io gerrit service. - www.rdoproject.org and lists.rdoproject.org. We expect that the interruption of services will be less than 4 hours. Regards, Nicolas , on behalf of the Software Factory Operation Team

1 0

RE: [kolla] Stein base container build fails
by Eric K. Miller 08 Feb '21

08 Feb '21

Looks like a Python3 error as described here: https://stackoverflow.com/questions/65896334/python-pip-broken-wiith-sys -stderr-writeferror-exc Looks like we need some way to choose to use the older version of pip using: curl https://bootstrap.pypa.io/2.7/get-pip.py -o get-pip.py instead of: curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py Eric

1 0

Rally - Unable to install rally - install_rally.sh is not available in repo
by Ankit Goel 08 Feb '21

08 Feb '21

Hello Experts, I was trying to install Openstack rally on centos 7 VM but the link provided in the Openstack doc to download the install_rally.sh is broken. Latest Rally Doc link - > https://docs.openstack.org/rally/latest/install_and_upgrade/install.html#au… Rally Install Script -> https://raw.githubusercontent.com/openstack/rally/master/install_rally.sh - > This is broken After searching on internet I could reach to the Openstack rally Repo - > https://opendev.org/openstack/rally but here I am not seeing the install_ rally.sh script and according to all the information available on internet it says we need install_ rally.sh. Thus can you please let me know what's the latest procedure to install Rally. Awaiting for your response. Thanks, Ankit Goel

4 12

[cinder] bug deputy report for week of 2021-02-01
by Sofia Enriquez 08 Feb '21

08 Feb '21

This is a bug report from 2021-01-27 to 2021-01-05. Most of this bugs were discussed at the Cinder meeting last Wednesday 2021-02-03 Critical: - High: - Medium: - https://bugs.launchpad.net/cinder/+bug/1914319: "DellEMC VNX driver: volume is not created on array but status is 'available' in openstack". Assigned to Yong Huan. - https://bugs.launchpad.net/cinder/+bug/1913578: "PowerFlex documentation contains invalid paths". Unassigned. - https://bugs.launchpad.net/python-cinderclient/+bug/1913474: "Cinderclient needs to support mv 3.63". Unassigned. Low: - https://bugs.launchpad.net/cinder/+bug/1913705: "OsProfiler does not work". Unassigned. Incomplete: - https://bugs.launchpad.net/cinder/+bug/1913363: "Multiple calls to lshost during attach operation". Assigned to Girish Chilukuri. Undecided/Unconfirmed: - https://bugs.launchpad.net/cinder/+bug/1914639: "[NetApp] Issue while trying to attach a volume using CHAP authentication". Unassigned. Not a bug: - https://bugs.launchpad.net/cinder/+bug/1914273: "After attachment-delete nova still sees volume as attached". Feel free to reply/reach me if I missed something. Regards Sofi -- L. Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

[KEYSTONE][FEDERATION] Groups mapping problem when using keycloak as IDP
by Taltavull Jean-Francois 08 Feb '21

08 Feb '21

Hello, In order to implement identity federation, I've deployed (with OSA) keystone (Ussuri) as Service Provider and Keycloak as IDP. As one can read at [1], "groups" can have multiple values and each value must be separated by a ";" But, in the OpenID token sent by keycloak, groups are represented with a JSON list and keystone fails to parse it well (only the first group of the list is mapped). Have any of you already faced this problem ? Thanks ! Jean-François [1] https://docs.openstack.org/keystone/ussuri/admin/federation/mapping_combina…

2 3

[stein][hypervisor] Post successful stein deployment Openstack hypervisor list is empty
by roshan anvekar 08 Feb '21

08 Feb '21

Hi all, Scenario: I have an installation of Openstack stein through kolla-ansible. The deployment went fine and all services look good. Although I am seeing that under Admin--> Compute --> Hypervisors panel in horizon, all the controller nodes are missing. It's a blank list. Also "Openstack hypervisor list" gives an empty list. I skimmed through the logs and found no error message other than in nova-scheduler that: *Got no allocation candidates from the Placement API. This could be due to insufficient resources or a temporary occurence as compute nodes start up.* Subsequently I checked placement container logs and found no error message or anamoly. Not sure what the issue is. Any help in the above case would be appreciated. Regards, Roshan

4 9

[victoria][trove] percona server deployment error
by Ammad Syed 08 Feb '21

08 Feb '21

Hi, I am trying to create a percona server datastore and datastore version. I have used the below commands. root@trove:/etc/trove# su -s /bin/bash trove -c "trove-manage datastore_update percona ''" Datastore 'percona' updated. root@ trove :/etc/trove# su -s /bin/sh -c "trove-manage datastore_version_update percona 5.7 percona cc2fbce7-4711-49bd-98ae-19e165c7a003 percona 1" trove Datastore version '5.7' updated. root@ trove :/etc/trove# su -s /bin/bash trove -c "trove-manage db_load_datastore_config_parameters percona 5.7 /usr/lib/python3/dist-packages/trove/templates/percona/validation-rules.json" Loading config parameters for datastore (percona) version (5.7) I have added percona section in trove.conf [percona] tcp_ports = 3306 When I try to deploy a database instance, it gives an error. Digging down further via ssh to the db instance, I have found below repetitive errors in agent logs. 2021-02-08 09:33:01.661 1288 DEBUG oslo_concurrency.processutils [-] Running cmd (subprocess): sudo groupadd --gid 1001 database execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:384 2021-02-08 09:33:01.689 1288 DEBUG oslo_concurrency.processutils [-] CMD "sudo groupadd --gid 1001 database" returned: 9 in 0.029s execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:423 2021-02-08 09:33:01.691 1288 DEBUG oslo_concurrency.processutils [-] 'sudo groupadd --gid 1001 database' failed. Not Retrying. execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:474 2021-02-08 09:33:01.692 1288 DEBUG oslo_concurrency.processutils [-] Running cmd (subprocess): sudo useradd --uid 1001 --gid 1001 -M database execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:384 2021-02-08 09:33:01.708 1288 DEBUG oslo_concurrency.processutils [-] CMD "sudo useradd --uid 1001 --gid 1001 -M database" returned: 9 in 0.016s execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:423 2021-02-08 09:33:01.709 1288 DEBUG oslo_concurrency.processutils [-] 'sudo useradd --uid 1001 --gid 1001 -M database' failed. Not Retrying. execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:474 2021-02-08 09:33:01.709 1288 DEBUG oslo_concurrency.processutils [-] Running cmd (subprocess): grep '^/dev/vdb ' /etc/mtab execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:384 2021-02-08 09:33:01.716 1288 DEBUG oslo_concurrency.processutils [-] CMD "grep '^/dev/vdb ' /etc/mtab" returned: 0 in 0.007s execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:423 2021-02-08 09:33:01.877 1288 CRITICAL root [-] Unhandled error: ModuleNotFoundError: No module named 'trove.guestagent.datastore.experimental' 2021-02-08 09:33:01.877 1288 ERROR root Traceback (most recent call last): 2021-02-08 09:33:01.877 1288 ERROR root File "/home/ubuntu/trove/contrib/trove-guestagent", line 34, in <module> 2021-02-08 09:33:01.877 1288 ERROR root sys.exit(main()) 2021-02-08 09:33:01.877 1288 ERROR root File "/home/ubuntu/trove/trove/cmd/guest.py", line 94, in main 2021-02-08 09:33:01.877 1288 ERROR root rpc_api_version=guest_api.API.API_LATEST_VERSION) 2021-02-08 09:33:01.877 1288 ERROR root File "/home/ubuntu/trove/trove/common/rpc/service.py", line 48, in __init__ 2021-02-08 09:33:01.877 1288 ERROR root _manager = importutils.import_object(manager) 2021-02-08 09:33:01.877 1288 ERROR root File "/opt/guest-agent-venv/lib/python3.6/site-packages/oslo_utils/importutils.py", line 44, in import_object 2021-02-08 09:33:01.877 1288 ERROR root return import_class(import_str)(*args, **kwargs) 2021-02-08 09:33:01.877 1288 ERROR root File "/opt/guest-agent-venv/lib/python3.6/site-packages/oslo_utils/importutils.py", line 30, in import_class 2021-02-08 09:33:01.877 1288 ERROR root __import__(mod_str) 2021-02-08 09:33:01.877 1288 ERROR root ModuleNotFoundError: No module named 'trove.guestagent.datastore.experimental' 2021-02-08 09:33:01.877 1288 ERROR root 2021-02-08 09:33:08.287 1394 INFO trove.cmd.guest [-] Creating user and group for database service 2021-02-08 09:33:08.288 1394 DEBUG oslo_concurrency.processutils [-] Running cmd (subprocess): sudo groupadd --gid 1001 database execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:384 2021-02-08 09:33:08.314 1394 DEBUG oslo_concurrency.processutils [-] CMD "sudo groupadd --gid 1001 database" returned: 9 in 0.026s execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:423 2021-02-08 09:33:08.315 1394 DEBUG oslo_concurrency.processutils [-] 'sudo groupadd --gid 1001 database' failed. Not Retrying. execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:474 -- Regards, Ammad

2 1

Trove Multi-Tenancy
by Ammad Syed 08 Feb '21

08 Feb '21

Hi, I have deployed trove and database instance deployment is successful. But the problem is all the database servers are being created in service account i.e openstack instance list shows the database instances in admin user but when I check openstack server list the database instance won't show up here, its visible in trove service account. Can you please advise how the servers will be visible in admin account ? I want to enable multi-tenancy. Below is the configuration [DEFAULT] log_dir = /var/log/trove # RabbitMQ connection info transport_url = rabbit://openstack:password@controller control_exchange = trove trove_api_workers = 5 network_driver = trove.network.neutron.NeutronDriver taskmanager_manager = trove.taskmanager.manager.Manager default_datastore = mysql cinder_volume_type = database_storage reboot_time_out = 300 usage_timeout = 900 agent_call_high_timeout = 1200 nova_keypair = trove-key debug = true trace = true # MariaDB connection info [database] connection = mysql+pymysql://trove:password@mariadb01/trove [mariadb] tcp_ports = 3306,4444,4567,4568 [mysql] tcp_ports = 3306 [postgresql] tcp_ports = 5432 [redis] tcp_ports = 6379,16379 # Keystone auth info [keystone_authtoken] www_authenticate_uri = http://controller:5000 auth_url = http://controller:5000 memcached_servers = controller:11211 auth_type = password project_domain_name = default user_domain_name = default project_name = service username = trove password = servicepassword [service_credentials] auth_url = http://controller:5000 region_name = RegionOne project_domain_name = default user_domain_name = default project_name = service username = trove password = servicepassword -- Regards, Syed Ammad Ali

2 5

[neutron] Bug Deputy Report Feb 1-8
by Lucas Alvares Gomes 08 Feb '21

08 Feb '21

Hi, This is the Neutron bug report of the week of 2021-02-01. High: * https://bugs.launchpad.net/neutron/+bug/1914394 - "[OVN] RowNotFound exception while waiting for Chassis metadata networks" Assigned to: lucasagomes * https://bugs.launchpad.net/neutron/+bug/1914747 - " Trunk subport's port status and binding:host_id don't updated after live-migration" Assigned to: slaweq Medium: * https://bugs.launchpad.net/neutron/+bug/1914754 - " [OVN][FT] Use the correct SB chassis table in testing" Assigned to: ralonsoh Needs further triage: * https://bugs.launchpad.net/neutron/+bug/1914745 - "[OVN/OVS] security groups erroneously dropping IGMP/multicast traffic" Unassigned * https://bugs.launchpad.net/neutron/+bug/1914231 - "IPv6 subnet creation in segmented network partially fails" Unassigned * https://bugs.launchpad.net/neutron/+bug/1914522 - "migrate from iptables firewall to ovs firewall" Unassigned * https://bugs.launchpad.net/neutron/+bug/1914842 - "Create vlan network will get 500 error when enable network_segment_range service plugin" Unassigned * https://bugs.launchpad.net/neutron/+bug/1914857 - "AttributeError: 'NoneType' object has no attribute 'db_find_rows" Unassigned Wishlist: * https://bugs.launchpad.net/neutron/+bug/1914757 - "[ovn] add ovn driver for security-group-logging" Assigned to: flaviof

1 0

[neutron] cancel the neutron L3 meeting next week 2021-02-10
by LIU Yulong 06 Feb '21

06 Feb '21

Hi there, The Spring Festival holiday will start at next Wednesday, I will be 10 days offline. So let's cancel the L3 meeting next week. Next neutron L3 meeting will be scheduled for 2021-02-24. Happy lunar New Year! 春节快乐! Regards, LIU Yulong

1 0

bindep, pacman, and PyPI release
by Jakob Lykke Andersen 05 Feb '21

05 Feb '21

Dear developers, I'm trying to use bindep on Arch but hitting a problem with the output handling. It seems that 'pacman -Q' may output warning lines if you have a file with the same name as the package. E.g.,: $ mkdir cmake $ pacman -Q cmake error: package 'cmake' was not found warning: 'cmake' is a file, you might want to use -p/--file. The current detection assumes the "was not found" is the last part of the output. Applying the patch below seems to fix it. After applying this patch, or whichever change you deem reasonable to fix the issue, it would be great if you could make a new release on PyPI. Thanks, Jakob diff --git a/bindep/depends.py b/bindep/depends.py index bb9553f..cacc863 100644 --- a/bindep/depends.py +++ b/bindep/depends.py @@ -558,7 +558,8 @@ class Pacman(Platform): stderr=subprocess.STDOUT).decode(getpreferredencoding(False)) except subprocess.CalledProcessError as e: eoutput = e.output.decode(getpreferredencoding(False)) - if e.returncode == 1 and eoutput.strip().endswith('was not found'): + s = "error: package '{}' was not found".format(pkg_name) + if e.returncode == 1 and s in eoutput: return None raise # output looks like

2 2

[oslo][keystone] Future of oslo.limit
by Ben Nemec 05 Feb '21

05 Feb '21

Hi, Last week in the Oslo meeting it was noted that we have some rather old patches open against oslo.limit. Before we spend a bunch of time getting those reviewed and merged, we wanted to confirm that this was still something people wanted to pursue. Things have been pretty quiet on the limit front for a while now, and doing the Oslo side does us no good if no one is going to consume it. I realize this is something of a chicken-and-egg situation since the library was somewhat blocked on [0], but that's been ready to merge for months and so far has only one review. If we do want to continue, merging that would be the first step. Then we should look at [1] which was the patch that prompted this conversation. Thanks. -Ben 0: https://review.opendev.org/c/openstack/oslo.limit/+/733881 1: https://review.opendev.org/c/openstack/oslo.limit/+/695527

2 1

[all][mentoring][outreachy][GSoC]Summer Interns/ Student Coders Anyone?
by Kendall Nelson 05 Feb '21

05 Feb '21

Hello :) So, if you've been involved in Outreachy, the Google Summer of Code[1] is pretty similar. It looks like the applications for projects open January 29, 2021 at 11:00 (Pacific Standard Time) if anyone wants to apply. I encourage you all to do so! It gets a lot of attention from university students so it's a great opportunity to get some new contributors and teach some more of the world about our community and open source! If you are interested in applying, let me know and I will do what I can to help you with the application to get it done on time (deadline not listed on the site yet, but they always come faster than we'd like)! -Kendall (diablo_rojo) [1] https://summerofcode.withgoogle.com/get-started/

1 1

[ironic] Node wont boot from virtual media
by Derek Higgins 05 Feb '21

05 Feb '21

Hi, I've been trying to get virtual media booting to work on a ProLiant DL380 Gen10 but not having any luck. Over redfish Ironic attaches the media, sets the Next boot option to 'cd' and then restarts the node. But it continues to boot from the HD as if the vmedia is being ignored. I'm wondering if anybody has seen anything similar, I'm thinking perhaps I don't have a bios setting configured that I need? I have the same problem if I set the One time boot on the iLo dashboard. System ROM U30 v2.40 (10/26/2020) iLO Firmware Version 2.33 Dec 09 2020 On another ProLiant DL380 Gen10 with the same ROM and iLo version where this works. Some of the hardware is different, in particular the one that works has a "HPE Smart Array P408i-a SR Gen10 " but the one that doesn't has a "HPE Smart Array E208i-a SR Gen10" could this be the relevant difference? any ideas would be great, thanks, Derek.

2 2

[All][StoryBoard] Angular.js Alternatives
by Kendall Nelson 05 Feb '21

05 Feb '21

Hello Everyone! The StoryBoard team is looking at alternatives to Angular.js since its going end of life. After some research, we've boiled all the options down to two possibilities: Vue.js or React.js I am diving more deeply into researching those two options this week, but any opinions or feedback on your experiences with either of them would be helpful! Here is the etherpad with our research so far[3]. Feel free to add opinions there or in response to this thread! -Kendall Nelson (diablo_rojo) & The StoryBoard Team [1] https://vuejs.org/ [2] https://reactjs.org/ [3] https://etherpad.opendev.org/p/replace-angularjs-storyboard-research

10 15

[zaqar][stable]Proposing Hao Wang as a stable branches core reviewer
by hao wang 05 Feb '21

05 Feb '21

Hi, Thierry I want to propose myself(wanghao) to be a new core reviewer of the Zaqar stable core team. I have been PTL in Zaqar for almost two years. I also want to help the stable branches better. Would you help me to add myself to the zaqar stable core team? Thank you.

2 2

[neutron][victoria] Front / Back Routers
by DHilsbos＠performair.com 04 Feb '21

04 Feb '21

All; My team and I have been working through the tutorials on Server World (server-world.com/ean/) in order to learn and build an OpenStack cluster. We've also been looking at the official documentation to attempt to increase our knowledge of the subject. I have a question about Neutron though. All the examples that I remember have Neutron setup with a single router. The router is part of a "provider" network, and subnet on the outside, and one or more "tenant" networks on the inside. Floating IPS, then appear to be IP addresses belonging to the "provider" subnet, that are applied to the router, and which the router then NATs. These setups look like this: Physrouter1 (physical router) subnet: 192.168.0.0/24, IP address: 192.168.0.1 | Physnet1 (192.168.0.0/24)(ovs network definition) | Router1 (ovs router)(allocation pool: 192.168.0.100 - 192.168.0.254) <-- Floating IPs are "owned" by this, and are in the range of the allocation pool | Tenant network(s) This has the advantage of being easy, fast, secure, and simple to setup. What if you wanted something where you could route whole subnet into your OpenStack cluster. Physrouter1 (physical router) subnet: 172.16.255.0/24, IP address: 172.16.255.1 | Physnet1 (172.16.255.0/24)(ovs network definition) | Router1 (ovs router)(fixed IP addresses: 172.16.255.2 & 172.16.254.1/24 + static / dynamic routing) | Network (17216.254.0/24) | Router2(ovs router)(allocation pool: 172.16.254.5 - 172.16.254.254) <-- Floating IPs are "owned" by this, and are in the range of the allocation pool | Tenant network(s) Is my understanding accurate? Are there advantages of one over the other? What commands are used to specify static IPs for ovs routers, and static routing rules? Thank you, Dominic L. Hilsbos, MBA Director - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

3 3

[ops][largescale-sig] How many compute nodes in a single cluster ?
by Thierry Carrez 04 Feb '21

04 Feb '21

Hi everyone, As part of the Large Scale SIG[1] activities, I'd like to quickly poll our community on the following question: How many compute nodes do you feel comfortable fitting in a single-cluster deployment of OpenStack, before you need to scale it out to multiple regions/cells/.. ? Obviously this depends on a lot of deployment-dependent factors (type of activity, choice of networking...) so don't overthink it: a rough number is fine :) [1] https://wiki.openstack.org/wiki/Large_Scale_SIG Thanks in advance, -- Thierry Carrez (ttx)

7 12

[neutron] Drivers meeting 05.02.2021
by Slawek Kaplonski 04 Feb '21

04 Feb '21

Hi, Due to lack of the topics to discuss, lets cancel tomorrow's drivers meeting. Please instead spent some time reviewing some opened specs :) Have a great weekend and see You online. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0