- openstack-discuss - lists.openstack.org

external network on rhosp 16.1 all in one installation
by Chen Sagi 12 Oct '20

12 Oct '20

Hi all, I have an All in one installation of RHOSP for evaluation purposes and I am trying to understand external network and the Octavia service. I have a VM with the openstack installed on, with 2 NICs in the management network as required by Red hat. I tried using the RHOSP Octavia guide, and also tried to create an external network but I seem to be missing something. Notice: the network that I am using is a flat network and is not configured for VLANs at all, but is a routable address. Thanks in advance, Chen Sagi.

1 0

Re: [Ussuri] [openstack-ansible] [cinder] Can't attach volumes to instances
by Oliver Wenz 12 Oct '20

12 Oct '20

> However, I could not read the logs the way Dmitriy suggested, it simply > returns > > -- Logs begin at Mon 2020-10-05 14:30:22 UTC, end at Mon 2020-10-12 > 11:17:20 UTC. -- > -- No entries -- > > so I couldn't investigate the request. ( I tried this on both utility > and cinder api containers on the management node and on the storage and > respective compute node to be sure) ... it seems that I've missed the storage node, since I just tried again and got something: Oct 12 12:57:09 bc1bl10 cinder-volume[30198]: 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server [req-e9175ddf-8ee4-4135-b89b-6e9c61f63999 2223bca5520044b7b7646e2f8141a440 5fbba868d04b47fa87a72b9dd821ee12 - default default] Exception during message handling: cinder.exception.InvalidInput: Invalid input received: Connector doesn't have required information: initiator 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/cinder/volume/manager.py", line 4471, in _connection_create 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server self.driver.validate_connector(connector) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/cinder/volume/drivers/lvm.py", line 859, in validate_connector 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server return self.target_driver.validate_connector(connector) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/cinder/volume/targets/iscsi.py", line 297, in validate_connector 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server raise exception.InvalidConnectorException(missing='initiator') 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server cinder.exception.InvalidConnectorException: Connector doesn't have required information: initiator 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 276, in dispatch 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 196, in _do_dispatch 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/cinder/volume/manager.py", line 4554, in attachment_update 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server connector) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server File "/openstack/venvs/cinder-21.0.1/lib/python3.6/site-packages/cinder/volume/manager.py", line 4473, in _connection_create 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server raise exception.InvalidInput(reason=six.text_type(err)) 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server cinder.exception.InvalidInput: Invalid input received: Connector doesn't have required information: initiator 2020-10-12 12:57:09.554 30198 ERROR oslo_messaging.rpc.server Kind regards, Oliver

1 0

[release][ptg] Wallaby PTG planning
by Herve Beraud 12 Oct '20

12 Oct '20

Hello, As you know our PTG starts on 26th October, we already have some topics to bring there, if you'd like to discuss something else during the session please add topics at https://etherpad.opendev.org/p/relmgmt-wallaby-ptg . If you plan to assist our meeting don't hesitate to add your name to the attendee list. I already proposed a date but if it doesn't fit your availability don't hesitate to propose another date. Cheers, -- Hervé Beraud Senior Software Engineer Red Hat - Openstack Oslo irc: hberaud -----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

[sdk] empty image dict if volume is attached
by thoralf schulze 12 Oct '20

12 Oct '20

hi there, openstack instances that have a cinder volume attached as their primary block device won't return any information regarding the image that has been used during their creation: openstack server show -f shell -c image -c volumes_attached test1 image="" volumes_attached="id='c0650208-f39c-4427-a73b-e1aa88531016'" vs. openstack server show -f shell -c image -c volumes_attached test2 image="Ubuntu 20.04 LTS (5cf81857-0dba-497e-ad9a-23a88dd97506)" volumes_attached="" as a result, this information won't be available in ansible inventories created with the relevant plugin¹ either … this is unfortunate, since i need to set certain variables for ansible based on the image resp. the operating system an instance uses. now, the necessary information seems to be available as a volume's metadata: openstack volume show -f shell -c volume_image_metadata c0650208-f39c-4427-a73b-e1aa88531016 volume_image_metadata="{'signature_verified': 'False', 'hw_rng_model': 'virtio', 'hypervisor_type': 'qemu', 'os_distro': 'centos', 'os_type': 'linux', 'image_id': '1572c62f-438c-4a70-be84-973fef0d3c77', 'image_name': 'CentOS 8', 'checksum': 'd89eb49f2c264d29225cecf2b6c83322', 'container_format': 'bare', 'disk_format': 'qcow2', 'min_disk': '10', 'min_ram': '1024', 'size': '716176896'}" … would it be a good idea to extend openstacksdk to look for image_name in the volumes attached to an instance and use this value for the image key? thank you very much & with kind regards, t. ¹ - https://docs.ansible.com/ansible/latest/collections/openstack/cloud/opensta… , this plugin makes use of openstacksdk

1 1

[all][elections][ptl][tc] Combined PTL/TC Voting 48 Hours Remain
by Jeremy Stanley 11 Oct '20

11 Oct '20

We are coming down to the last hours for voting in the TC and Telemetry elections. Voting ends Oct 13, 2020 23:45 UTC. Search your Gerrit preferred email address[0] for the messages with subjects like... Poll: OpenStack Wallaby Cycle Technical Committee Election Poll That is your ballot and links you to the voting application. Please vote. If you have voted, please encourage your colleagues to vote. Candidate statements are linked to the names of all confirmed candidates: https://governance.openstack.org/election/ What to do if you don't see the email and have a commit in at least one of the official project teams' deliverable repositories[1]: * check the trash of your Gerrit Preferred Email address[0], in case it went into trash or spam * find the ID of at least one commit merged to an official deliverable repo[1] over the current or previous cycle, confirm you are an OpenStack Foundation Individual Member[2], and then email the election officials[3] or get in touch in the #openstack-elections channel on the Freenode IRC network. If we can confirm that you are entitled to vote, we will add you to the voters list and you will be emailed a ballot. Please vote! Thank you, [0] Sign into review.openstack.org and go to Settings > Contact Information. Look at the email listed as your Preferred Email. That is where the ballot has been sent. [1] https://opendev.org/openstack/governance/src/tag/0.8.0/reference/projects.y… [2] https://www.openstack.org/profile/ [3] https://governance.openstack.org/election/#election-officials -- Jeremy Stanley

1 0

[all][tc][goals] Migrate CI/CD jobs to new Ubuntu LTS Focal : Final update
by Ghanshyam Mann 10 Oct '20

10 Oct '20

Hello Everyone, With the Integration testing moved to Ubuntu Focal, I am marking the 'Ubuntu Focal migration' community goal as complete. Tracking: https://storyboard.openstack.org/#!/story/2007865 Summary: ======== * Lot of work was involved in this. There are many changes required for this migration as compare to previous migration from Xenial to Bionic. ** Many dependencies lower constraint compatible with py3.8 and Focal distro had to be updated. Almost in all the repos. ** Mysql 8.0 caused many incompatible DB issues. * I missed the original deadline of m-2 to complete this goal due to falling gates and to avoid any gate block for any projects. * More than 300 repo had been fixed or tested in advance before migration happened. This helped a lot to keep gate green during this migration. * We had to keep few jobs in Bionic due to time constraints and move the rest of the other projects jobs on Focal. These are under work by the respective team. ** Manila, freezer-tempest, magnum-tempest-plugin-tests-api, ironic-python-agent-builder due to diskimage-builder[1] etc * Deployment projects are communicated (openstack-helm, tripleo if needed) or already in-progress (puppet-openstack) for this migration and the respective team need to check if any updates needed. I would like to convey special Thanks to everyone who helped in this goal and made it possible to complete it in Victoria cycle itself. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-October/017843.… -gmann

2 1

[Magnum][kolla-ansible][kayobe] Information gathering for 2 blocking issues
by Tony Pearce 09 Oct '20

09 Oct '20

Hi all, hope you are all keeping safe and well. I am looking for information on the following two issues that I have which surrounds Magnum project: 1. Magnum does not support Openstack API with HTTPS 2. Magnum forces compute nodes to consume disk capacity for instance data My environment: Openstack Train deployed using Kayobe (Kolla-ansible). With regards to the HTTPS issue, Magnum stops working after enabling HTTPS because the certificate / CA certificate is not trusted by Magnum. The certificate which I am using is one that was purchased from GoDaddy and is trusted in web browsers (and is valid), just not trusted by the Magnum component. Regarding compute node disk consumption issue - I'm at a loss with regards to this and so I'm looking for more information about why this is being done and is there any way that I could avoid it? I have storage provided by a Cinder integration and so the consumption of compute node disk for instance data I need to avoid. Any information the community could provide to me with regards to the above would be much appreciated. I would very much like to use the Magnum project in this deployment for Kubernetes deployment within projects. Thanks in advance, Regards, Tony

3 9

[release] Release countdown for week R-0 Oct 12-16
by Sean McGinnis 09 Oct '20

09 Oct '20

Development Focus ----------------- We will be releasing the coordinated OpenStack Victoria release next week, on October 14. Thanks to everyone involved in the Victoria cycle! We are now in pre-release freeze, so no new deliverable will be created until final release, unless a release-critical regression is spotted. Otherwise, teams attending the virtual PTG should start to plan what they will be discussing there, by creating and filling team etherpads. You can access the list of PTG etherpads at: http://ptg.openstack.org/etherpads.html General Information ------------------- On release day, the release team will produce final versions of deliverables following the cycle-with-rc release model, by re-tagging the commit used for the last RC. A patch doing just that will be proposed. PTLs and release liaisons should watch for that final release patch from the release team. While not required, we would appreciate having an ack from each team before we approve it on the 16th, so that their approval is included in the metadata that goes onto the signed tag. Upcoming Deadlines & Dates -------------------------- Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0

vPTG Oct 2020 Registration & Schedule
by Kendall Nelson 09 Oct '20

09 Oct '20

Hey everyone, The October 2020 Project Teams Gathering is right around the corner! The official schedule has now been posted on the PTG website [1], the PTGbot has been updated[2], and we have also attached it to this email. Friendly reminder, if you have not already registered, please do so [3]. It is important that we get everyone to register for the event as this is how we will contact you about tooling information/passwords and other event details. Please let us know if you have any questions. Cheers, The Kendalls (diablo_rojo & wendallkaters) [1] PTG Website www.openstack.org/ptg [2] PTGbot: http://ptg.openstack.org/ptg.html [3] PTG Registration: https://october2020ptg.eventbrite.com

5 7

OpenStack Ironic Issue
by Akshay 346 09 Oct '20

09 Oct '20

Hello Team, I hope you all are good. I am using openstack ironic deployment and have some issues and some observations. These are: Issue: At the time of "openstack server create" for launching baremetal node, I came across the following multiple observations: - Sometimes when I launch baremetal node on openstack, after one time pxe booting, the baremetal node goes down again and then comes up and goes into second time booting and gets stuck there in "Probing" state ( Seen on node's console) BUT according to openstack horizon, it is up and running and according to "openstack baremetal node show", it is in "Active" state. - And sometimes when i launch baremetal node on openstack, after one time pxe booting, the baremetal node goes down again and then comes up, the "spawning" state on openstack horizon goes into ERROR. Error seen in "nova-compute-ironic-0" container is : "ERROR nova.compute.manager [instance: edd447c6-12ac-49ba-b0bc-f419aff4892a] nova.exception.InstanceDeployFailure: Failed to provision instance edd447c6-12ac-49ba-b0bc-f419aff4892a: Timeout reached while waiting for callback for node 75210cc4-ad98-442d-ace1-89ce69467580" - The baremetal node always takes near about 2 hours to be in "available" state from "cleaning" and "clean-wait". Is it correct behaviour ? Please guide me how to resolve this. Regards Akshay DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

3 2

[tripleo][ptg] Wallaby PTG timezone - 1300-1700 UTC
by Marios Andreou 09 Oct '20

09 Oct '20

Hi folks, Unless there is disagreement and we can find a better time that suits all, the current plan is to use the same timezone as we had in the last virtual PTG - that is 1300-1700 UTC ( https://etherpad.opendev.org/p/tripleo-ptg-wallaby ). Please speak up if you would like to propose and discuss an alternative thanks, marios

1 0

[tripleo][ptg] PTG reminder please add topics this week
by Marios Andreou 09 Oct '20

09 Oct '20

Hi tripleo friends, reminder: PTG is coming 26th October - if you'd like to discuss something there please add topics at https://etherpad.opendev.org/p/tripleo-wallaby-topics - at the moment it doesn't look like we'll need more than the first day to cover what we have there. Ideally I'd like to socialise a tentative schedule at the end of next week so we can make changes depending on folks availability. thanks for your help, marios

1 0

[tempest][nova][interop] Deletion of test_reboot_server_soft from Tempest
by Martin Kopec 09 Oct '20

09 Oct '20

Hello, we'd like to inform you that we are going to remove the following compute test by this commit [1]: test_reboot_server_soft with id 4640e3ef-a5df-482e-95a1-ceeeb0faa84d The reasons are: - Nova has switched to hard reboot if the guest is not responding, there is no way to see the difference from the API - minimum scenario test uses soft reboot and the nova functional test also covers reboot - the test has been skipped on Tempest side for more than 6 years - the test is not part of any latest guideline of interop [2] [1] https://review.opendev.org/#/c/647718 [2] http://codesearch.openstack.org/?q=test_reboot_server_soft&i=nope&files=&re… Please let us know in case of any objection on this test removal. Regards, -- Martin Kopec Software Quality Engineer Red Hat EMEA <https://www.redhat.com> <https://red.ht/sig>

1 0

[cloudkitty] Core team cleanup
by Pierre Riteau 09 Oct '20

09 Oct '20

Hello, In the cloudkitty-core team there is zhangguoqing, whose email address (zhang.guoqing(a)99cloud.net) is bouncing with "551 5.1.1 recipient is not exist". I propose to remove them from the core team. zhangguoqing, if you read us and want to stay in the team, please contact me. Best wishes, Pierre Riteau (priteau)

2 5

help with Openstack magnum in train
by Robert Duncan 09 Oct '20

09 Oct '20

Hi, I have openstack train deployed by kolla-ansible and am trying to deploy a k8s cluster on Fedora Atomic 27 with magnum it seems there is no podman binary in the Atomic 27 image specifically, Fedora-Atomic-27-20180419.0.x86_64.qcow2 I have set the label use_podman=false however, the template seems to ignore that which results in this error in the heat agent log: WARNING Attempt 12: Trying to install kubectl. Sleeping 5s * i=12 * '[' 12 -gt 60 ']' * echo 'WARNING Attempt 12: Trying to install kubectl. Sleeping 5s' * sleep 5s * ssh -F /srv/magnum/.ssh/config root@localhost '/usr/bin/podman run --entrypoint /bin/bash --name install-kubectl --net host --privileged --rm --user root --volume /srv/magnum/bin:/host/srv/magnum/bin k8s.gcr.io/hyperkube:v1.15.7<http://k8s.gcr.io/hyperkube:v1.15.7> -c '''cp /usr/local/bin/kubectl /host/srv/magnum/bin/kubectl'''' bash: /usr/bin/podman: No such file or directory [fedora@test-quznqfqfa5ld-master-0 ~]$ which podman /usr/bin/which: no podman in (/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/fedora/.local/bin:/home/fedora/bin) I have tried a later version of atomic but the dependencies are closely coupled and it seems I must use version 27 - what am I missing? I'm following along with the Train documentation https://docs.openstack.org/magnum/train/install/launch-instance.html and was able to deploy a docker swarm cluster. thanks, Rob. ________________________________ The information contained and transmitted in this e-mail is confidential information, and is intended only for the named recipient to which it is addressed. The content of this e-mail may not have been sent with the authority of National College of Ireland. Any views or opinions presented are solely those of the author and do not necessarily represent those of National College of Ireland. If the reader of this message is not the named recipient or a person responsible for delivering it to the named recipient, you are notified that the review, dissemination, distribution, transmission, printing or copying, forwarding, or any other use of this message or any part of it, including any attachments, is strictly prohibited. If you have received this communication in error, please delete the e-mail and destroy all record of this communication. Thank you for your assistance. ________________________________

3 4

VIM in Pending issue for VNF Deployment.
by Raman Preet 09 Oct '20

09 Oct '20

Hey. I am facing exactly the same issue as mentioned in this link. but on stein version of openstack http://opendiscussione.blogspot.com/2018/08/re-openstack-tacker-vim-status-… Do you have any resolution for this.? Thanks. Regards

1 0

[Ussuri] [openstack-ansible] [cinder] Can't attach volumes to instances
by Oliver Wenz 09 Oct '20

09 Oct '20

Hi, I've deployed OpenStack successfully using openstack-ansible. I use cinder with LVM backend and can create volumes. However, when I attach them to an instance, they stay detached (though there's no Error Message) both using CLI and the Dashboard. Looking for a solution I read that the cinder logs might contain relevant information but in Ussuri they don't seem to be present under /var/log/cinder... Here's the part of my openstack_user_config.yml regarding Cinder: ``` storage_hosts: lvm-storage1: ip: 192.168.110.202 container_vars: cinder_backends: lvm: volume_backend_name: LVM_iSCSI volume_driver: cinder.volume.drivers.lvm.LVMVolumeDriver volume_group: cinder-volumes iscsi_ip_address: 10.0.3.202 limit_container_types: cinder_volume ``` I've created cinder-volumes with vgcreate before the installation and all cinder services are up: # openstack volume service list +------------------+--------------------------------------+------+---------+-------+----------------------------+ | Binary | Host | Zone | Status | State | Updated At | +------------------+--------------------------------------+------+---------+-------+----------------------------+ | cinder-backup | bc1bl10 | nova | enabled | up | 2020-10-07T11:24:10.000000 | | cinder-volume | bc1bl10@lvm | nova | enabled | up | 2020-10-07T11:24:05.000000 | | cinder-scheduler | infra1-cinder-api-container-1dacc920 | nova | enabled | up | 2020-10-07T11:24:05.000000 | +------------------+--------------------------------------+------+---------+-------+----------------------------+ Thanks in advance! Kind regards, Oliver

3 2

[ceilometer] How to install older version of gnocchi
by WALSH CHANG 08 Oct '20

08 Oct '20

I use Ubuntu 18.04 to install https://docs.openstack.org/ceilometer/stein/install/install-base-ubuntu.html (ceilometer) When I run service gnocchi-api restart, I get Failed to restart gnocchi-api.service: Unit gnocchi-api.service not found. I can't find any solution to address this issue. Someone said the new version doesn't include the gnocchi-api, so I am trying to install the previous version, but I don't know where I can find the old version of gnocchi-api https://stackoverflow.com/questions/47520779/service-gnocchi-api-not-found Can anyone help? Thanks

1 0

[neutron] Drivers meeting - 09.10.2020
by Slawek Kaplonski 08 Oct '20

08 Oct '20

Hi, I don't have any new or updated RFEs to discuss for drivers team for this week. So lets cancel the meeting this week. Have a great weekend and see You all next week :) -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[Octavia][kolla-ansible][kayobe] - network configuration knowledge gathering
by Tony Pearce 08 Oct '20

08 Oct '20

Hi all, Openstack version is Train Deployed via Kayobe I am trying to deploy octavia lbaas but hitting some blockers with regards to how this should be set up. I think the current issue is the lack of neutron bridge for the octavia network and I cannot locate how to achieve this from the documentation. I have this setup at the moment which I've added another layer 2 network provisioned to the controller and compute node, for running octavia lbaas: [Controller node]------------octavia network-----------[Compute node] However as there's no bridge, the octavia instance cannot connect to it. The exact error from the logs: 2020-10-05 14:37:34.070 6 INFO neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Mapping physical network physnet3 to bridge broct 2020-10-05 14:37:34.070 6 ERROR neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] Bridge broct for physical network physnet3 does not Bridge "broct" does exist but it's not a neutron bridge: [root@juc-kocon1-prd kolla]# brctl show bridge name bridge id STP enabled interfaces brext 8000.001a4a16019a no eth5 p-brext-phy broct 8000.001a4a160173 no eth6 docker0 8000.0242f5ed2aac no [root@juc-kocon1-prd kolla]# I've been through the docs a few times but I am unable to locate this info. Most likely the information is there but I am unsure what I need to look for, hence missing it. Would any of you be able to help shed light on this or point me to the documentation? Thank you Tony Pearce

2 5

[neutron][security groups] Drop egress traffic to specific subnets
by Sebastian Luna Valero 08 Oct '20

08 Oct '20

Hi, I am looking at the docs in here: https://wiki.openstack.org/wiki/Neutron/SecurityGroups and I find: > For egress traffic: Only traffic matched with security group rules are allowed. So we currently have the default security group rule allowing all traffic to everywhere. We would like to prevent egress traffic from our VMs into a couple of internally reachable subnets in our deployment. Is there a way to achieve this in OpenStack? Many thanks, Sebastian

1 0

[largescale-sig] Next meeting: October 7, 16utc
by Thierry Carrez 08 Oct '20

08 Oct '20

Hi everyone, Our next meeting will be a EU-US-friendly meeting, this Wednesday, October 7 at 16 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201007T16 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - ttx to draft a plan to tackle "meaningful monitoring" as a new SIG workstream - all to describe briefly how you solved metrics/billing in your deployment in https://etherpad.openstack.org/p/large-scale-sig-documentation - masahito to push latest patches to oslo.metrics Talk to you all later, -- Thierry Carrez

1 1

[Octavia] Please help with amphorav2 provider populate db command
by Bujack, Stefan 08 Oct '20

08 Oct '20

Hello, I think I need a little help again with the configuration of the amphora v2 provider. I get an error when I try to populate the database. It seems that the name of the localhost is used for the DB host and not what I configured in octavia.conf as DB host root@octavia04:~# octavia-db-manage --config-file /etc/octavia/octavia.conf upgrade_persistence 2020-09-29 11:45:01.911 818313 WARNING taskflow.persistence.backends.impl_sqlalchemy [-] Engine connection (validate) failed due to '(pymysql.err.OperationalError) (1045, "Access denied for user 'octavia'@'octavia04.desy.de' (using password: YES)") (Background on this error at: http://sqlalche.me/e/e3q8)' 2020-09-29 11:45:01.912 818313 CRITICAL octavia-db-manage [-] Unhandled error: sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1045, "Access denied for user 'octavia'@'octavia04.desy.de' (using password: YES)") (Background on this error at: http://sqlalche.me/e/e3q8) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage Traceback (most recent call last): 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2276, in _wrap_pool_connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return fn() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 303, in unique_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return _ConnectionFairy._checkout(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 760, in _checkout 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage fairy = _ConnectionRecord.checkout(pool) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 492, in checkout 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage rec = pool._do_get() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/impl.py", line 139, in _do_get 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self._dec_overflow() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py", line 68, in __exit__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage compat.reraise(exc_type, exc_value, exc_tb) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 153, in reraise 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise value 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/impl.py", line 136, in _do_get 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self._create_connection() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 308, in _create_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return _ConnectionRecord(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 437, in __init__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self.__connect(first_connect_check=True) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 639, in __connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage connection = pool._invoke_creator(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/strategies.py", line 114, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return dialect.connect(*cargs, **cparams) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 482, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self.dbapi.connect(*cargs, **cparams) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/__init__.py", line 94, in Connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return Connection(*args, **kwargs) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 325, in __init__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self.connect() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 599, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self._request_authentication() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 861, in _request_authentication 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage auth_packet = self._read_packet() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 684, in _read_packet 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage packet.check_error() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/protocol.py", line 220, in check_error 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage err.raise_mysql_exception(self._data) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/err.py", line 109, in raise_mysql_exception 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise errorclass(errno, errval) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage pymysql.err.OperationalError: (1045, "Access denied for user 'octavia'@'octavia04.desy.de' (using password: YES)") 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage The above exception was the direct cause of the following exception: 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage Traceback (most recent call last): 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/local/bin/octavia-db-manage", line 8, in <module> 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage sys.exit(main()) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/local/lib/python3.8/dist-packages/octavia/db/migration/cli.py", line 156, in main 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage CONF.command.func(config, CONF.command.name) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/local/lib/python3.8/dist-packages/octavia/db/migration/cli.py", line 98, in do_persistence_upgrade 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage persistence.initialize() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/local/lib/python3.8/dist-packages/octavia/controller/worker/v2/taskflow_jobboard_driver.py", line 50, in initialize 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage with contextlib.closing(backend.get_connection()) as connection: 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/taskflow/persistence/backends/impl_sqlalchemy.py", line 335, in get_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage conn.validate(max_retries=self._max_retries) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/taskflow/persistence/backends/impl_sqlalchemy.py", line 394, in validate 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage _try_connect(self._engine) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 311, in wrapped_f 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self.call(f, *args, **kw) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 391, in call 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage do = self.iter(retry_state=retry_state) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 338, in iter 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return fut.result() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3.8/concurrent/futures/_base.py", line 432, in result 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self.__get_result() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise self._exception 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/tenacity/__init__.py", line 394, in call 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage result = fn(*args, **kwargs) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/taskflow/persistence/backends/impl_sqlalchemy.py", line 391, in _try_connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage with contextlib.closing(engine.connect()): 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2209, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self._connection_cls(self, **kwargs) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 103, in __init__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage else engine.raw_connection() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2306, in raw_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self._wrap_pool_connect( 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2279, in _wrap_pool_connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage Connection._handle_dbapi_exception_noconnection( 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1547, in _handle_dbapi_exception_noconnection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage util.raise_from_cause(sqlalchemy_exception, exc_info) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 398, in raise_from_cause 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage reraise(type(exception), exception, tb=exc_tb, cause=cause) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 152, in reraise 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise value.with_traceback(tb) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 2276, in _wrap_pool_connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return fn() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 303, in unique_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return _ConnectionFairy._checkout(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 760, in _checkout 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage fairy = _ConnectionRecord.checkout(pool) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 492, in checkout 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage rec = pool._do_get() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/impl.py", line 139, in _do_get 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self._dec_overflow() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py", line 68, in __exit__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage compat.reraise(exc_type, exc_value, exc_tb) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 153, in reraise 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise value 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/impl.py", line 136, in _do_get 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self._create_connection() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 308, in _create_connection 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return _ConnectionRecord(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 437, in __init__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self.__connect(first_connect_check=True) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/pool/base.py", line 639, in __connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage connection = pool._invoke_creator(self) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/strategies.py", line 114, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return dialect.connect(*cargs, **cparams) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 482, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return self.dbapi.connect(*cargs, **cparams) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/__init__.py", line 94, in Connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage return Connection(*args, **kwargs) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 325, in __init__ 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self.connect() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 599, in connect 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage self._request_authentication() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 861, in _request_authentication 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage auth_packet = self._read_packet() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/connections.py", line 684, in _read_packet 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage packet.check_error() 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/protocol.py", line 220, in check_error 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage err.raise_mysql_exception(self._data) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage File "/usr/lib/python3/dist-packages/pymysql/err.py", line 109, in raise_mysql_exception 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage raise errorclass(errno, errval) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (1045, "Access denied for user 'octavia'@'octavia04.desy.de' (using password: YES)") 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage (Background on this error at: http://sqlalche.me/e/e3q8) 2020-09-29 11:45:01.912 818313 ERROR octavia-db-manage root@octavia04:~# cat /etc/octavia/octavia.conf [DEFAULT] transport_url = rabbit://openstack:password@rabbit-intern.desy.de use_journal = True [api_settings] bind_host = 0.0.0.0 bind_port = 9876 [certificates] cert_generator = local_cert_generator ca_certificate = /etc/octavia/certs/server_ca.cert.pem ca_private_key = /etc/octavia/certs/server_ca.key.pem ca_private_key_passphrase = passphrase [controller_worker] amp_image_owner_id = f89517ee676f4618bd55849477442aca amp_image_tag = amphora amp_ssh_key_name = octaviakey amp_secgroup_list = 2236e82c-13fe-42e3-9fcf-bea43917f231 amp_boot_network_list = 9f7fefc4-f262-4d8d-9465-240f94a7e87b amp_flavor_id = 200 network_driver = allowed_address_pairs_driver compute_driver = compute_nova_driver amphora_driver = amphora_haproxy_rest_driver client_ca = /etc/octavia/certs/client_ca.cert.pem [database] connection = mysql+pymysql://octavia:password@maria-intern.desy.de/octavia [haproxy_amphora] client_cert = /etc/octavia/certs/client.cert-and-key.pem server_ca = /etc/octavia/certs/server_ca.cert.pem [health_manager] bind_port = 5555 bind_ip = 172.16.0.2 controller_ip_port_list = 172.16.0.2:5555 [keystone_authtoken] www_authenticate_uri = https://keystone-intern.desy.de:5000/v3 auth_url = https://keystone-intern.desy.de:5000/v3 memcached_servers = nova-intern.desy.de:11211 auth_type = password project_domain_name = default user_domain_name = default project_name = service username = octavia password = password service_token_roles_required = True [oslo_messaging] topic = octavia_prov [service_auth] auth_url = https://keystone-intern.desy.de:5000/v3 memcached_servers = nova-intern.desy.de:11211 auth_type = password project_domain_name = Default user_domain_name = Default project_name = service username = octavia password = password [task_flow] persistence_connection = mysql+pymysql://octavia:woxSGH45cdZL1Sa4@maria-intern.desy.de/octavia_persistence jobboard_backend_driver = 'redis_taskflow_driver' jobboard_backend_hosts = 10.254.28.113 jobboard_backend_port = 6379 jobboard_backend_password = password jobboard_backend_namespace = 'octavia_jobboard' root@octavia04:~# octavia-db-manage current 2020-09-29 12:02:23.159 819432 INFO alembic.runtime.migration [-] Context impl MySQLImpl. 2020-09-29 12:02:23.160 819432 INFO alembic.runtime.migration [-] Will assume non-transactional DDL. fbd705961c3a (head) We have an Openstack Ussuri deployment on Ubuntu 20.04. Thanks in advance, Stefan Bujack

3 4

[cinder] wallaby PTG planning + happy hour
by Brian Rosmaita 07 Oct '20

07 Oct '20

Here's your weekly reminder to add topics to the cinder PTG planning etherpad: https://etherpad.opendev.org/p/wallaby-ptg-cinder-planning (and don't forget to register for the PTG) At today's Cinder meeting, we decided to hold a happy hour on the first day Cinder is meeting during the PTG so that everyone can get to know each other informally a bit before we get down to serious business for the rest of the week. So please plan to be happy for this hour: 15:00-16:00 UTC on Tuesday 27 October 2020 You don't have to work on Cinder or even be attending the Cinder sessions of the PTG to attend the happy hour; but we do request that you be happy if you attend. Unfortunately, due to the virtual nature of the PTG, the only beverages available will also be virtual (but you can have as much as you want!). Or you can bring your own actual beverages (in which case, you can also have as much as you want!). cheers, brian

1 0

[cinder] type-checking hackfest next week
by Brian Rosmaita 07 Oct '20

07 Oct '20

At today's Cinder meeting, we decided to celebrate the Victoria release happening next Wednesday by cancelling the Cinder meeting we'd be having on that day, and instead using the time for a hackfest to review the patches Eric has posted for using mypy for type checking in the cinder code, and to add type annotations elsewhere in the code. So we'll be meeting from 1300-1600 UTC on Wednesday 14 October in the opendev Jitsi: https://meetpad.opendev.org/cinder-type-checking-hackfest If you want an advance look, you can start here: - https://review.opendev.org/#/c/733620/ - https://review.opendev.org/#/c/733621/ For general information: - https://docs.python.org/3/library/typing.html - https://www.python.org/dev/peps/pep-3107/ - http://mypy-lang.org/index.html See you on Wednesday! brian

1 0

[cyborg] Edge sync up at the PTG
by Ildiko Vancsa 07 Oct '20

07 Oct '20

Hi Cyborg Team, I’m reaching out to check if you are available during the upcoming PTG to continue discussions we were having in June to see where Cyborg evolved since then and how we can continue collaborating. Like last time, the OSF Edge Computing Group is meeting on the first three days and we have a slot reserved to sync up with OpenStack projects such as Cyborg on Wednesday (October 28) at 1300 UTC - 1400 UTC. Would the team be available to join at that time? Our planning etherpad is here: https://etherpad.opendev.org/p/ecg-vptg-october-2020 Thanks, Ildikó

1 0

[kolla] Restarting RMQ
by Braden, Albert 07 Oct '20

07 Oct '20

When I learned OpenStack at eBay we ran RMQ on dedicated VMs. My new employer runs kolla and everything is in containers. When I was running RMQ on VMs, it would lock up and we would have to restart it on all 3 VMs. If that didn't work, we had a "cold start" procedure where we would stop all 3, delete the contents of /var/lib/rabbitmq/mnesia/ and then run some commands to set the correct config and permissions before starting. What is the correct way to restart RMQ in kolla? Should I log into the containers and restart services there, or use rabbitmqctl, or just stop and start the containers? Is stop/starting the containers the equivalent of the "cold start" procedure? I apologize for the nonsense below. So far I have not been able to stop it from being attached to my external emails. I'm working on it. E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

3 2

Nova-Docker package missing in the git repository
by Nischay Mundas 07 Oct '20

07 Oct '20

Hi, I am trying to deploy docker with OpenStack Nova on CentOs7 VM. For this reason, I am referring to the link - https://wiki.openstack.org/wiki/Docker. I have come across a point where the nova-docker package is not present in the mentioned git repository i.e https://opendev.org/x/nova-docker. So, can you please help me with this? -- Thanks & Regards, Nischay Mundas Sooktha Consulting Pvt. Ltd., Bangalore Web: www.sooktha.com Email: nischay.mundas(a)sooktha.com Mob: +91 8496861949

3 2

[kolla] kolla_docker ansible module
by Braden, Albert 07 Oct '20

07 Oct '20

I opened bug #1897948[1] the other day and today I was trying to figure out what needs to be done to fix it. In the mariadb backup container I see the offending line "--history=$(date +%d-%m-%Y)" in /usr/local/bin/kolla_mariadb_backup.sh and I had assumed that it was coming from https://github.com/openstack/kolla/blob/master/docker/mariadb/mariadb/backu… and the obvious solution is to replace "$(date +%d-%m-%Y)" with "$HISTORY_NAME" where HISTORY_NAME=`ls -t $BACKUP_DIR/mysqlbackup*|head -1|cut -d- -f2-4` but when I look at the playbook I see that backup.sh appears to be part of a docker image. Is the docker image pulling /usr/local/bin/kolla_mariadb_backup.sh from https://github.com/openstack/kolla/blob/master/docker/mariadb/mariadb/backu… ? On my kolla-ansible build server I see /opt/openstack/share/kolla-ansible/ansible/roles/mariadb/tasks/backup.yml[2] which appears to be an ansible playbook calling module kolla_docker, but I can't find anything about the kolla_docker module on the googles nor on the ansible site. Where can I find the documentation for ansible module kolla_docker? [1] https://bugs.launchpad.net/kolla-ansible/+bug/1897948 [2] http://www.hastebin.net/bimufefosy.yaml E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

3 2

[kolla] Kolla klub meeting
by Mark Goddard 07 Oct '20

07 Oct '20

Hi, Tomorrow (Thursday) we will have a Kolla Klub meeting. As usual, the meeting will be at 15:00 UTC. Let's discuss the following topics: * Virtual PTG * Open discussion on networking Look forward to seeing you there. https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… Thanks, Mark

1 0

[oslo] Proposing Lance Bragstad as oslo.cache core
by Moises Guimaraes de Medeiros 07 Oct '20

07 Oct '20

Hello everybody, It is my pleasure to propose Lance Bragstad (lbragstad) as a new member of the oslo.core core team. Lance has been a big contributor to the project and is known as a walking version of the Keystone documentation, which happens to be one of the biggest consumers of oslo.cache. Obviously we think he'd make a good addition to the core team. If there are no objections, I'll make that happen in a week. Thanks. -- Moisés Guimarães Software Engineer Red Hat <https://www.redhat.com> <https://red.ht/sig>

7 7

[charms] Zaza bundle tests
by Xav Paice 06 Oct '20

06 Oct '20

I was writing a patch recently and in order to test it, I needed to make changes to the test bundles. I ended up making the same change across several files, and missing one (thanks to the reviewer for noticing that!). Some of the other projects I'm involved with use symlinks to a base bundle with overlays: ./tests$ ls -l bundles/ total 20 -rw-rw---- 2 xav xav 5046 Sep 29 14:56 base.yaml lrwxrwxrwx 1 xav xav 9 Sep 29 10:01 bionic.yaml -> base.yaml lrwxrwxrwx 1 xav xav 9 Sep 29 10:01 focal.yaml -> base.yaml drwxrwx--x 2 xav xav 4096 Sep 29 10:01 overlays lrwxrwxrwx 1 xav xav 9 Sep 29 10:01 xenial.yaml -> base.yaml ./tests$ ls bundles/overlays/ bionic.yaml.j2 focal.yaml.j2 local-charm-overlay.yaml.j2 xenial.yaml.j2 This means that I can edit base.yaml just once, and if a change is specific to any of the particular bundles there's a place for that in the individual overlays. When we have bundles for each release going back to Mitaka, this could be quite an effort saver. I gather there's been some discussion around this already, and would be keen to see if there's a reason folks might avoid that pattern?

4 8

[all][elections][ptl][tc] Conbined PTL/TC Voting Kickoff
by Jeremy Stanley 06 Oct '20

06 Oct '20

Polls for PTL and TC elections are now open and will remain open for you to cast your vote until Oct 13, 2020 23:45 UTC. We are selecting 4 TC members, and are having PTL elections for Telemetry. Please rank all candidates in your order of preference. You are eligible to vote in the TC election if you are a Foundation individual member[0] that also has committed to any official project team's deliverable repositories[1] over the Sep 27, 2019 00:00 UTC - Sep 29, 2020 00:00 UTC timeframe (Ussuri to Victoria) or if you are in the list of extra-atcs[2] for any official project team. You are eligible to vote in a PTL election if you are a Foundation individual member[0] and had a commit in one of that team's deliverable repositories[1] over the Sep 27, 2019 00:00 UTC - Sep 29, 2020 00:00 UTC timeframe (Ussuri to Victoria) or if you are in that team's list of extra-atcs[2]. If you are eligible to vote in an election, you should find your email with a link to the Condorcet page to cast your vote in the inbox of your Gerrit preferred email[3]. What to do if you don't see the email and have a commit in at least one of the projects having an election: * check the trash or spam folders of your Gerrit preferred email address, in case it went into trash or spam * wait a bit and check again, in case your email server is a bit slow * find the sha of at least one commit from the project's deliverable repos[0] and email the election officials[4]. If we can confirm that you are entitled to vote, we will add you to the voters list for the appropriate election. Our democratic process is important to the health of OpenStack, please exercise your right to vote! Candidate statements/platforms can be found linked to Candidate names on this page: https://governance.openstack.org/election/ Happy voting, [0] https://www.openstack.org/community/members/ [1] The list of the repositories eligible for electoral status: https://opendev.org/openstack/governance/raw/tag/0.8.0/reference/projects.y… [2] Look for the extra-atcs element in [1] [3] Sign into review.openstack.org: Go to Settings > Contact Information. Look at the email listed as your preferred email. That is where the ballot has been sent. [4] https://governance.openstack.org/election/#election-officials -- Jeremy Stanley on behalf of the OpenStack Technical Election Officials

1 0

[octavia] PTG planning
by Michael Johnson 06 Oct '20

06 Oct '20

Hello Octavia community! I have set up a time slot during the Wallaby PTG to discuss all things Octavia on October 27th and 28th, 13:00-17:00 UTC. There is an Octavia etherpad for PTG planning: https://etherpad.opendev.org/p/wallaby-ptg-octavia Please add your topics to the list and I will try to set a rough agenda. Michael

1 0

[designate] PTG planning
by Michael Johnson 06 Oct '20

06 Oct '20

Hello Designate community! I have set up a time slot during the Wallaby PTG to discuss all things Designate on October 29th, 13:00-15:00 UTC. I have also created an etherpad for PTG planning: https://etherpad.opendev.org/p/wallaby-ptg-designate Please add your topics to the list and I will try to set a rough agenda. Michael

1 0

[nova][ops] The need for healing instance info cache to base itself on neutron for its port list
by Jean-Philippe Méthot 06 Oct '20

06 Oct '20

Hi, This is related to bug https://bugs.launchpad.net/nova/+bug/1751923 <https://bugs.launchpad.net/nova/+bug/1751923> . I don’t see if this was fixed in more recent versions as we are running Rocky, but according to the different code reviews linked to the bug report, this was never committed into Openstack master. I apologize in advance if this was already fixed elsewhere (it’s marked as fixed in Stein, but the reviews say the code was never committed?). Essentially, we’re running into a production issue where sometimes, after being shutdown for a while, our VMs ports just straight up disappear from Nova. Obviously, since this is production, we have to scramble to link back the port to the VM to bring the VM back up. As a result, we have not identified yet the exact source of our issue. However, we do have tested Mohammed Naser’s patch linked to this issue and it has at the very least offered us a band-aid since the VMs appear to be keeping their ports now. Would it be possible to review and commit this patch or Matt Riedeman’s patch to master and backport it? Couldn’t it just have a configuration option to enable it? While I’m not convinced it can fix the root cause of our problem, it could at least contribute to the stability of our and other people’s Openstack cluster. Jean-Philippe Méthot Senior Openstack system administrator Administrateur système Openstack sénior PlanetHoster inc. 4414-4416 Louis B Mayer Laval, QC, H7P 0G1, Canada TEL : +1.514.802.1644 - Poste : 2644 FAX : +1.514.612.0678 CA/US : 1.855.774.4678 FR : 01 76 60 41 43 UK : 0808 189 0423

3 3

[requirements][all] requirements is unfrozen, cycle trailing beware
by Matthew Thode 06 Oct '20

06 Oct '20

Hi all, The requirements project just branched stable/victoria meaning that we are also now unfrozen and open for business. This also means that non-branched (cycle trailing) projects will need to watch out for constraints updates meant for wallaby (now master) could impact your development work on victoria. -- Matthew Thode

1 0

[tripleo][undercloud] use local container images in insecure repo
by Ruslanas Gžibovskis 06 Oct '20

06 Oct '20

Hi all, I have been trying to use containers from local container image repo which is insecure, but it is always trying to use TLS version, and I do not have https there. even if I would have, I would not have CERT signed, so still it is insecure. It is always trying to access over WWW:443. my registries.conf [1] and I am able to fetch image from the registry [1] and my container image prepare file contains updated repos, I have even added insecure: true any tips? I am following [2] and [3] [1] http://paste.openstack.org/show/cYQM2k77bIh14Zzr5Kjn/ [2] https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deploym… [3] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16… -- Ruslanas Gžibovskis +370 6030 7030

2 4

[Trove] Project udpate
by Lingxian Kong 06 Oct '20

06 Oct '20

Hi there, As the official Victoria release is approaching and it has been a long time silence for Trove in the upstream, I think it's good time for me as the Trove PTL for the last 3 dev cycles to have a project update. The things that will be described below have not been achieved in one single dev cycle, but are some significant changes since the 'dark time' of Trove project in the past. Tips hat to those who have made contributions to Trove project ever before. ## Service tenant configuration Service tenant configuration was added in Stein release, before that, it's impossible to deploy Trove in the public cloud (even not for some private cloud due to security concerns) because the user may have access to the guest instance which contains sensitive data in the config files, the users can also perform operations towards either storage or networking resources which may bring much management overhead and make it easy to break the database functionality. With service tenant configuration (which is currently the default setting in devstack), almost all the cloud resources(except the Swift objects for backup data) created for a Trove instance are only visible to the Trove service user. As Trove users, they can only see a Trove instance, but know nothing about the Nova VM, Cinder volume, Neutron management network, and security groups under the hood. The only way to operate Trove instances is to interact with Trove API. ## Message queue security concerns To do database operations, trove controller services communicate with trove-guestagent service inside the instance via message queue service (i.e. RabbitMQ in most environments). In the meantime, trove-guestagent periodically sends status update information to trove-conductor through the same messaging system. In the current design, the RabbitMQ username and password need to be configured in the trove-guestagent config file, which brought significant security concern for the cloud deployers in the past. If the guest instance is compromised, then guest credentials are compromised, which means the messaging system is compromised. As part of the solution, a security enhancement was introduced in the Ocata release, using encryption keys to protect the messages between the control plane and the guest instances. First, the rabbitmq credential should only have access to trove services. Second, even with the rabbitmq credential and the message encryption key of the particular instance, the communication from the guest agent and trove controller services are restricted in the context of that particular instance, other instances are not affected as the malicious user doesn't know their message encryption keys. Additionally, since Ussuri, trove is running in service tenant model in devstack by default which is also the recommended deployment configuration. Most of the cloud resources(except the Swift objects for backup data) created for a trove instance should only be visible to the trove service user, which also could decrease the attack surface. ## Datastore images Before Victoria, Trove provided a bunch of diskimage-builder elements for building different datastore images. As contributors were leaving, most of the elements just became unmaintained except for MySQL and MariaDB. To solve the problem, database containerization was introduced in Victoria dev cycle, so that the database service is running in a docker container inside the guest instance, trove guest agent is pulling container image for a particular datastore when initializing guest instance. Trove is not maintaining those container images. That means, since Victoria, the cloud provider only needs to maintain one single datastore image which only contains common code that is datastore independent. However, for backward compatibility, the cloud provider still needs to create different datastores but using the same Glance image ID. Additionally, using database container also makes it much easier for database operations and management. To upgrade from the older version to Victoria onwards, the Trove user has to create backups before upgrading, then create instances from the backup, so downtime is expected. ## Supported datastores Trove used to support several datastores such as MySQL, MariaDB, PostgreSQL, MongoDB, CouchDB, etc. Most of them became unmaintained because of a lack of maintainers in the community. Currently, only MySQL and MariaDB drivers are fully supported and tested in the upstream. PostgreSQL driver was refactored in Victoria dev cycle and is in experimental status again. Adding extra datastores should be quite easy by implementing the interfaces between trove task manager and guest agent. Again, no need to maintain separate datastore images thanks to the container technology. ## Instance backup At the same time as we were moving to use container for database services, we also moved the backup and restore functions out of trove guest agent code because the backup function is usually using some 3rd party software which we don't want to pre-install inside the datastore image. As a result, we are using container as well for database backup and restore. For more information about the backup container image, see https://lingxiankong.github.io/2020-04-14-database-backup-docker-image.html. ## Others There are many other improvements not mentioned above added to Trove since Train, e.g. * Access configuration for the instance. * The swift backend customization for backup. * Online volume resize support. * XFS disk format for database data volume. * API documentation improvement. * etc. By the way, Catalyst Cloud has already deployed Trove (in Alpha) in our public cloud in New Zealand, we are getting feedback from customers. I believe there are other deployers already have Trove in their production but running an old version because of previous upstream situation in the past. If you are one of them and interested in upgrading to the latest, please either reply to this email or send personal email to me, I would be very happy to provide any help or guidance. For those who are still in evaluation phase, you are also welcome to reach out for any questions. I'm always in the position to help in #openstack-trove IRC channel. --- Lingxian Kong Senior Software Engineer Catalyst Cloud www.catalystcloud.nz

2 1

[tripleo][ci] RFC, supported releases of TripleO
by Wesley Hayutin 06 Oct '20

06 Oct '20

Greetings, I just wanted to give folks the opportunity to speak up before we make any changes. Please review https://releases.openstack.org/ As we are branching master -> victoria it looks like we can definitely remove stable/rocky from both upstream and RDO software factory. Any comments about rocky? Stein is end of maintenance on 2020 November 11th. Any thoughts on dropping stein from upstream and rdo software factory? Thanks! Please be specific if you have comments as to which release you are referring to.

4 5

Modify devstack after basic deployment
by Md. Hejbul Tawhid MUNNA 06 Oct '20

06 Oct '20

Hi, I have deployed a basic openstack using devstack. now I want to install additional component like designate or magnum. What is the way to do that? Regards, Munna

2 1

[nova]: Separation of VM size and extra specs in flavors
by Csatari, Gergely (Nokia - FI/Espoo) 06 Oct '20

06 Oct '20

Hi, During some discussions about CNTT<https://cntt.readthedocs.io/>, where several flavor sizes and extra specs are specified we realized, that the combination of all flavor sizes and the different extra specs results in a very large number of flavors. One idea was to separate the size and the extra specs on the creation of flavors and just define some kind of rules do define how the different sizes and extra specs can be combined. The other idea was just to leave things as they are. Are there any opinions on which idea is better? Thanks, Gerg0

2 1

[tripleo][ussuri][release] bugfix stable/ussuri release for tripleo 'cycle-with-intermediary'
by Marios Andreou 06 Oct '20

06 Oct '20

o/ tripleo On request I made a bugfix stable/ussuri release for the tripleo 'cycle-with-intermediary' repos. If you are interested see [1] for the latest hashes. If you need a release for a different branch reach out to me. thanks, marios [1] https://review.opendev.org/#/c/755718/

1 0

[Neutron] Cancelled QoS team meeting October 6
by Rodolfo Alonso Hernandez 06 Oct '20

06 Oct '20

Hello: Due to the lack of agenda, the Neutron QoS meeting will be cancelled today. Next meeting will be held on October 20. Regards.

1 0

qemu ussuri can't launch instance
by ops＠clustspace.com 06 Oct '20

06 Oct '20

Hello, Does anyone know where to find the problem? Searched few days in google :) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [req-f16a5b6c-3475-4322-a664-45f3bd9c041a cb4c181d25a14dda958e40792968f97e 5242bcab73714ab192cca8d909b72e9a - default default] [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] Instance failed to spawn: libvirt.libvirtError: internal error: cannot load AppArmor$ 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] Traceback (most recent call last): 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/nova/compute/manager.py", line 2614, in _build_resources 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] yield resources 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/nova/compute/manager.py", line 2378, in _build_and_run_instance 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] accel_info=accel_info) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 3580, in spawn 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] power_on=power_on) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 6438, in _create_domain_and_network 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] destroy_disks_on_failure) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] self.force_reraise() 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] six.reraise(self.type_, self.value, self.tb) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/six.py", line 703, in reraise 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] raise value 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 6410, in _create_domain_and_network 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] post_xml_callback=post_xml_callback) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/driver.py", line 6351, in _create_domain 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] guest.launch(pause=pause) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/guest.py", line 142, in launch 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] self._encoded_xml, errors='ignore') 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] self.force_reraise() 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] six.reraise(self.type_, self.value, self.tb) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/six.py", line 703, in reraise 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] raise value 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/nova/virt/libvirt/guest.py", line 137, in launch 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] return self._domain.createWithFlags(flags) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/eventlet/tpool.py", line 193, in doit 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] result = proxy_call(self._autowrap, f, *args, **kwargs) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/eventlet/tpool.py", line 151, in proxy_call 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] rv = execute(f, *args, **kwargs) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/eventlet/tpool.py", line 132, in execute 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] six.reraise(c, e, tb) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/six.py", line 703, in reraise 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] raise value 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/eventlet/tpool.py", line 86, in tworker 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] rv = meth(*args, **kwargs) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] File "/usr/lib/python3/dist-packages/libvirt.py", line 1265, in createWithFlags 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f] libvirt.libvirtError: internal error: cannot load AppArmor profile 'libvirt-63bb4205-fcbb-4f2b-9ade-e055e7ff966f' 2020-10-05 23:11:04.054 1585 ERROR nova.compute.manager [instance: 63bb4205-fcbb-4f2b-9ade-e055e7ff966f]

3 2

[neutron] Security groups with SR-IOV as a second ML2 mechanism driver
by GABRIEL OMAR GAMERO MONTENEGRO 05 Oct '20

05 Oct '20

Dear all, I'm planning to use the SR-IOV Networking L2 Agent with another L2 Agent as Open vSwitch or Linux Bridge (a configuration with multiple ML2 mechanism drivers). Does anybody know if I can use the Open vSwitch or Linux Bridge L2 agents with security group feature (implemented with iptables firewall driver or Native Open vSwitch firewall driver)? Or am I restricted to apply no security to my instances because SR-IOV L2 agent is being used as a second mechanism driver in the same OpenStack deployment? Thanks in advance, Gabriel Gamero

3 2

[tc] weekly update
by Mohammed Naser 05 Oct '20

05 Oct '20

Hi everyone, Here's an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. # Patches ## Open Reviews - Select Prvisep as the Wallaby Goal https://review.opendev.org/755590 - Add assert:supports-standalone https://review.opendev.org/722399 - Add Ironic charms to OpenStack charms https://review.opendev.org/754099 - Clarify impact on releases for SIGs https://review.opendev.org/752699 - Add election schedule exceptions in charter https://review.opendev.org/751941 ## Project Updates - Retire devstack-plugin-pika project https://review.opendev.org/748730 - Retire openstack/os-loganalyze https://review.opendev.org/753834 ## General Changes - Define TC-approved release in a resolution https://review.opendev.org/752256 - Reorder repos alphabetically https://review.opendev.org/754097 - Remove tc:approved-release tag https://review.opendev.org/749363 - Migrate rpm-packaging to a SIG https://review.opendev.org/752661 # Other Reminders - PTG Brainstorming: https://etherpad.opendev.org/p/tc-wallaby-ptg - PTG Registration: https://october2020ptg.eventbrite.com Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[tc][all][interop] Removed the 'tc:approved-release' tag in favor of projects.yaml
by Ghanshyam Mann 05 Oct '20

05 Oct '20

Hello Everyone, TC has merged the recent change to remove the 'tc:approved-release' tag[1]. This tag was used as the superset of projects used by the OpenStack Foundation when creating commercial trademark programs. Basically, this tag was used to know if the project under OpenStack governance is mature and follows the defined release model so that it can be considered as a possible candidate for trademark programs. This situation was in the early stage of OpenStack when we used to have incubated vs integrated project status but now everything in projects.yaml[2] file is considered as mature, following release, active. We do not need any changes in the bylaw as all projects listed in projects.yaml file is applicable as bylaw term "OpenStack Technical Committee Approved Release" which is made clear in the resolution also[3]. Interop group can refer to the OpenStack governed projects list for possible candidates for the trademark program. [1] https://review.opendev.org/#/c/749363/ [2] https://governance.openstack.org/tc/reference/projects/ [3] https://governance.openstack.org/tc/resolutions/20200920-tc-approved-releas… -gmann

1 0

[cloudkitty] Joining the "CloudKitty Drivers" Launchpad team
by Pierre Riteau 05 Oct '20

05 Oct '20

Hello, While CloudKitty has moved to Storyboard to track its bugs [1], there is still a lot of content under the Launchpad project [2], including years of bug reports, blueprints, etc. As PTL, I would like to be able to administer the CloudKitty Launchpad project. I have requested access to the "CloudKitty Drivers" Launchpad team [3], but haven't heard back. I see some people have been on the waiting list for years [4]. Since the "OpenStack Administrators" team [5] is the owner "CloudKitty Drivers", would one of its members be able to grant me access? Many thanks, Pierre Riteau (priteau) [1] https://storyboard.openstack.org/#!/project/890 [2] https://launchpad.net/cloudkitty [3] https://launchpad.net/~cloudkitty-drivers [4] https://launchpad.net/~cloudkitty-drivers/+members#proposed [5] https://launchpad.net/~openstack-admins

3 9

Re: [charms] Zaza bundle tests
by Aurelien Lourot 05 Oct '20

05 Oct '20

Wasn't one of the reasons for this that we're striving to have stand-alone / complete bundles? So that we could "just give" the one-file bundle to someone and it would "just work". Anyway I'm also in favour of any solution leading to less repetition, i.e. what was suggested by Xav. Aurelien

1 0