October 2020 - openstack-discuss - lists.openstack.org

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

10 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 10 Oct '20

10 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 09 Oct '20

09 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 09 Oct '20

09 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 08 Oct '20

08 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 08 Oct '20

08 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 08 Oct '20

08 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 07 Oct '20

07 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 07 Oct '20

07 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