- openstack-discuss - lists.openstack.org

[osprofiler][rally][openstack] Using osprofiler/rally directly on production Openstack system
by hai wu 06 Mar '23

06 Mar '23

Is there any concern with using osprofiler/rally directly on the production Openstack system?

2 3

Re: [manila] share server with multiple tenant networks
by Goutham Pacha Ravi 06 Mar '23

06 Mar '23

On Mon, Mar 6, 2023 at 12:12 PM garcetto <garcetto(a)gmail.com> wrote: > thank you, so how can i have multiple shares on different tenant networks, > creating more share servers right? > Yes; map these tenant networks into share networks in manila, and create your shares with the share networks. Each share network will trigger the creation of a share server if one already doesn't exist. > > > On Mon, Mar 6, 2023 at 7:56 PM Goutham Pacha Ravi <gouthampravi(a)gmail.com> > wrote: > >> Hi Garcetto, >> >> On Mon, Mar 6, 2023 at 9:07 AM garcetto <garcetto(a)gmail.com> wrote: >> >>> good afternoon, >>> i am trying to add a second share server or share to existing share >>> server on different network inside same tenant, actually i have: >>> >> >>> tenant-net-01 (with the share server), ok working. >>> tenant-net-02 (tried to add a share network, but the error says >>> " >>> create: Could not find an existing share server or allocate one on the >>> share network provided. You may use a different share network, or verify >>> the network details in the share network and retry your request. If this >>> doesn't work, contact your administrator to troubleshoot issues with your >>> network. >>> " >>> >> >> As the message suggests, manila was unable to obtain network allocations >> to create a share server for you on the second network. Are you a user, or >> an administrator of this cloud? If you are an administrator, you >> should look at the logs from manila's share-manager service to check what >> failed. >> >> You cannot expect to attach multiple tenant networks to the same share >> server unfortunately - that isn't supported today. >> >> >> >>> any clue or doc i can read? >>> thank you >>> >>

1 0

[manila] ha for share server
by garcetto 06 Mar '23

06 Mar '23

good afternoon, is it possible to have HA for share server vm in openstack? i mean, the vm that is created on every tenant and used as nfs server. thank you

2 1

[manila] share server with multiple tenant networks
by garcetto 06 Mar '23

06 Mar '23

good afternoon, i am trying to add a second share server or share to existing share server on different network inside same tenant, actually i have: tenant-net-01 (with the share server), ok working. tenant-net-02 (tried to add a share network, but the error says " create: Could not find an existing share server or allocate one on the share network provided. You may use a different share network, or verify the network details in the share network and retry your request. If this doesn't work, contact your administrator to troubleshoot issues with your network. " any clue or doc i can read? thank you

2 1

[ironic] PTL Availability
by Jay Faulkner 06 Mar '23

06 Mar '23

Hi all, Just a heads up -- I'll be out of town and mostly out of IRC from Wednesday, 3/8 to Monday 3/13. If there are emergent issues that need to be addressed urgently, please send an email directly to me and I can have a look. Alternatively, I have a large amount of trust in our delegated release managers and former Ironic PTLs and support them if they need to take action in my stead. - Jay Faulkenr

1 0

[openstack-helm] Get rid of cephfs and rbd provisioners
by Vladimir Kozhukalov 06 Mar '23

06 Mar '23

Hi everyone, I would like to suggest getting rid of cephfs and rbd provisioners. They have been retired and have not been maintained for about 2.5 years now [1]. I believe the CSI approach is what all users rely on nowadays and we can safely remove them. The trigger for this suggestion is that we are currently experiencing issues while trying to switch cephfs provisioner to Ubuntu Focal and fixing this is just wasting time. [2] Stephen spent some time debugging the issues and can give more details if needed. What do you think? [1] https://github.com/kubernetes-retired/external-storage/tree/master/ceph [2] https://review.opendev.org/c/openstack/openstack-helm-infra/+/872976 -- Best regards, Kozhukalov Vladimir

3 3

Paying for Openstack support
by Albert Braden 06 Mar '23

06 Mar '23

I have a question for the operators here. Is anyone paying for Openstack support and getting good value for your money? Can you contact someone for help with an issue, and get a useful response in a reasonable time? If you have an emergency, can you get help quickly? If so, I would like to hear about your experience. Who are you getting good support from? Do they support your operating system too? If not, where do you get your OS support, and how good is it? If you work for a company that provides openstack and/or Linux support, you are welcome to send me a sales pitch, but my goal is to hear from operators.

5 5

[neutron] CI meeting Tuesday 7.03.2023 cancelled
by Slawek Kaplonski 06 Mar '23

06 Mar '23

Hi, Due to some internal event which I have tomorrow in the same time as our CI meeting I will not be able to run the CI meeting. I don't see any really serious issues in our CI this week and after discussing that with Rodolfo we decided to cancel this week's CI meeting. See You on the meeting next week. -- Slawek Kaplonski Principal Software Engineer Red Hat

1 0

[cinder] Error when creating backups from iscsi volume
by Rishat Azizov 06 Mar '23

06 Mar '23

Hello! We have an error with creating backups from iscsi volume. Usually, this happens with large backups over 100GB. 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server [req-f6619913-6f96-4226-8d75-2da3fca722f1 23de1b92e7674cf59486f07ac75b886b a7585b47d1f143e9839c49b4e3bbe1b4 - - -] Exception during message handling: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. Command: multipath -f 3624a93705842cfae35d7483200015ec6 Exit code: 1 Stdout: '' Stderr: 'Feb 16 00:22:45 | 3624a93705842cfae35d7483200015ec6 is not a multipath device\n' 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/cinder/utils.py", line 890, in wrapper 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return func(self, *args, **kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 410, in create_backup 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server volume_utils.update_backup_error(backup, str(err)) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 227, in __exit__ 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_utils/excutils.py", line 200, in force_reraise 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server raise self.value 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 399, in create_backup 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server updates = self._run_backup(context, backup, volume) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 493, in _run_backup 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server ignore_errors=True) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/cinder/backup/manager.py", line 1066, in _detach_device 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server force=force, ignore_errors=ignore_errors) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/utils.py", line 141, in trace_logging_wrapper 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py", line 360, in inner 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", line 880, in disconnect_volume 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server is_disconnect_call=True) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/connectors/iscsi.py", line 942, in _cleanup_connection 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server self._linuxscsi.flush_multipath_device(multipath_name) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/initiator/linuxscsi.py", line 382, in flush_multipath_device 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server root_helper=self._root_helper) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/executor.py", line 52, in _execute 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server result = self.__execute(*args, **kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/os_brick/privileged/rootwrap.py", line 172, in execute 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return execute_root(*cmd, **kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_privsep/priv_context.py", line 247, in _wrap 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server return self.channel.remote_call(name, args, kwargs) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server File "/usr/lib/python3.6/site-packages/oslo_privsep/daemon.py", line 224, in remote_call 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server raise exc_type(*result[2]) 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command. 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Command: multipath -f 3624a93705842cfae35d7483200015ec6 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Exit code: 1 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Stdout: '' 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Stderr: 'Feb 16 00:22:45 | 3624a93705842cfae35d7483200015ec6 is not a multipath device\n' 2023-02-16 00:23:25.298 1920 ERROR oslo_messaging.rpc.server Could you please help with this error?

2 1

[neutron] Bug deputy report (week 09, starting on Feb-27-2022)
by Lajos Katona 06 Mar '23

06 Mar '23

Hi neutrinos, Here are the bugs reported between February 27 and March 05. *First the unassigned bugs:* * https://bugs.launchpad.net/neutron/+bug/2009043 neutron-l3-agent restart some random ha routers get wrong state *High prio bugs* * https://bugs.launchpad.net/neutron/+bug/2008712 Security group rule deleted by cascade (because its remote group had been deleted) is not deleted in the backend * https://bugs.launchpad.net/neutron/+bug/2008947 Investigate test_restart_rpc_on_sighup_multiple_workers failure * https://bugs.launchpad.net/neutron/+bug/2009055 Performance issue when creating lots of ports * https://bugs.launchpad.net/neutron/+bug/2009215 [OVS] Error during OVS agent start *Medium or lower:* * https://bugs.launchpad.net/neutron/+bug/2008858 Call the api and do not return for a long time * https://bugs.launchpad.net/neutron/+bug/2008912 "_validate_create_network_callback" failing with 'NoneType' object has no attribute 'qos_policy_id' * https://bugs.launchpad.net/neutron/+bug/2008943 OVN DB Sync utility cannot find NB DB Port Group * https://bugs.launchpad.net/neutron/+bug/2009053 OVN: default stateless SG blocks metadata traffic * https://bugs.launchpad.net/neutron/+bug/2009221 [OVS] Custom ethertype traffic is not coming into the VM *One incomplete:* * https://bugs.launchpad.net/neutron/+bug/2008808 Duplicate packet when ping to external with out floating ip *Already merged / released bugs:* * https://bugs.launchpad.net/neutron/+bug/2008695 Remove any LB HM references from the external_ids upon deleting an HM * https://bugs.launchpad.net/neutron/+bug/2008767 [sqlalchemy-20][vnpaas] SQL execution without transaction in progress Have a bugless week :-) Lajos (lajoskatona)

1 0

[kolla] Weekly meeting on 8th March cancelled
by Michał Nasiadka 06 Mar '23

06 Mar '23

Hola Koalas, Weekly meeting on Wed this week is cancelled - I’m off on vacation. See you next week! Best regards, Michal

1 0

[Openstack Trove] Fails to create DB container - "context deadline exceeded", even though images can be pulled manually
by ddorra＠t-online.de 05 Mar '23

05 Mar '23

Hi, my Trove service installed into a Openstack Victoria fails in starting DB instances: 2023-03-05 12:06:17.172 1015 INFO trove.guestagent.datastore.mysql_common.service [-] Starting docker container, image: mysql:5.7.29 2023-03-05 12:06:17.174 1015 WARNING trove.guestagent.utils.docker [-] Failed to get container database: docker.errors.NotFound: 404 Client Error: Not Found ("No such container: database") 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service [-] Failed to start mysql: docker.errors.APIError: 500 Server Error: Internal Server Error ("Get "https://registry-1.docker.io/v2/": context deadline exceeded") It sounds that it's unable to connect to Docker in order to download the image. However, after logging in to the DB instance I am able to pull docker images manually, or even a cloudinit action can successfully pull images during instance creation... root@t1:~# docker images REPOSITORY TAG IMAGE ID CREATED SIZE mysql 5.7.29 5d9483f9a7b2 2 years ago 455MB root@t1:~# <mailto:root@t1:~#> The cloudinit I need to adjust the default GW in oder to reach internet. I hope that is early enough in the boot process and doesn't hamper the guestagent. Any hint what I can do? ============= Trove cloudinit root@voscontrol:~# cat /etc/trove/cloudinit/mysql.cloudinit #cloud-config write_files: - content: | ... path: /etc/ssh/sshd_config - content: | ... path: /root/.bash_aliases runcmd: - [ ip, route, delete, default, via, 10.0.0.79 ] - [ ip, route, add, default, via, 10.0.0.62 ] - [ service, ssh, restart ] - [ docker, pull, "mysql:5.7.29" ] root@voscontrol:~# ================ guest config root@t1:/etc/trove# cat ./conf.d/guest_info.conf [DEFAULT] guest_id=291070bc-671d-437a-a68c-9cee840e614c datastore_manager=mysql datastore_version=5.7.29 tenant_id=606b291caeab4dc2bb1072e2e43b082a instance_rpc_encr_key=EEKenGHSe4exOOU8a0ivV2aR8FwOr2yw root@t1:/etc/trove# cat ./conf.d/trove-guestagent.conf [DEFAULT] log_file = trove-guestagent.log log_dir = /var/log/trove/ ignore_users = os_admin control_exchange = trove #transport_url = rabbit://openstack:pass123@192.168.100.79:5672/ transport_url = rabbit://openstack:pass123@10.0.0.79:5672/ rpc_backend = rabbit command_process_timeout = 60 use_syslog = False debug = True [service_credentials] #auth_url = http://192.168.100.79:5000/v3 auth_url = http://10.0.0.79:5000/v3 region_name = RegionOne project_name = service password = pass123 project_domain_name = Default user_domain_name = Default username = trove root@t1:/etc/trove# ================ /var/log/trove/trove-guestagent.log ... 2023-03-05 12:06:17.162 1015 DEBUG oslo_concurrency.processutils [-] CMD "sudo mkdir -p /var/run/mysqld" returned: 0 in 0.009s execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:423 2023-03-05 12:06:17.162 1015 DEBUG oslo_concurrency.processutils [-] Running cmd (subprocess): sudo chown -R 1001:1001 /var/run/mysqld execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:384 2023-03-05 12:06:17.171 1015 DEBUG oslo_concurrency.processutils [-] CMD "sudo chown -R 1001:1001 /var/run/mysqld" returned: 0 in 0.009s execute /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_concurrency/processutils.py:423 2023-03-05 12:06:17.172 1015 INFO trove.guestagent.datastore.mysql_common.service [-] Starting docker container, image: mysql:5.7.29 2023-03-05 12:06:17.174 1015 WARNING trove.guestagent.utils.docker [-] Failed to get container database: docker.errors.NotFound: 404 Client Error: Not Found ("No such container: database") 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service [-] Failed to start mysql: docker.errors.APIError: 500 Server Error: Internal Server Error ("Get "https://registry-1.docker.io/v2/": context deadline exceeded") 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service Traceback (most recent call last): 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 259, in _raise_for_status 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service response.raise_for_status() 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service raise HTTPError(http_error_msg, response=self) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.41/containers/database/json 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service Traceback (most recent call last): 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/utils/docker.py", line 58, in start_container 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service container = client.containers.get(name) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 887, in get 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service resp = self.client.api.inspect_container(container_id) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/utils/decorators.py", line 19, in wrapped 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service return f(self, resource_id, *args, **kwargs) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/container.py", line 771, in inspect_container 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service self._get(self._url("/containers/{0}/json", container)), True 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 265, in _result 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service self._raise_for_status(response) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 261, in _raise_for_status 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service raise create_api_error_from_http_exception(e) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service raise cls(e, response=response, explanation=explanation) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service docker.errors.NotFound: 404 Client Error: Not Found ("No such container: database") 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service Traceback (most recent call last): 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 259, in _raise_for_status 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service response.raise_for_status() 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service raise HTTPError(http_error_msg, response=self) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.41/containers/create?name=database 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service Traceback (most recent call last): 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 810, in run 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service detach=detach, **kwargs) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 868, in create 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service resp = self.client.api.create_container(**create_kwargs) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/container.py", line 430, in create_container 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service return self.create_container_from_config(config, name) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/container.py", line 441, in create_container_from_config 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service return self._result(res, True) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 265, in _result 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service self._raise_for_status(response) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 261, in _raise_for_status 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service raise create_api_error_from_http_exception(e) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service raise cls(e, response=response, explanation=explanation) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service docker.errors.ImageNotFound: 404 Client Error: Not Found ("No such image: mysql:5.7.29") 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service Traceback (most recent call last): 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 259, in _raise_for_status 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service response.raise_for_status() 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service raise HTTPError(http_error_msg, response=self) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.41/images/create?tag=5.7.29&fromImage=mysql 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service Traceback (most recent call last): 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/mysql_common/service.py", line 612, in start_db 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service command=command 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/utils/docker.py", line 73, in start_container 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service command=command 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 812, in run 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service self.client.images.pull(image, platform=platform) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/images.py", line 445, in pull 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service repository, tag=tag, stream=True, **kwargs 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/image.py", line 415, in pull 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service self._raise_for_status(response) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 261, in _raise_for_status 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service raise create_api_error_from_http_exception(e) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service raise cls(e, response=response, explanation=explanation) 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service docker.errors.APIError: 500 Server Error: Internal Server Error ("Get "https://registry-1.docker.io/v2/": context deadline exceeded") 2023-03-05 12:06:32.540 1015 ERROR trove.guestagent.datastore.mysql_common.service 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager [-] Failed to prepare datastore: Failed to start mysql: trove.common.exception.TroveError: Failed to start mysql 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager Traceback (most recent call last): 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 259, in _raise_for_status 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager response.raise_for_status() 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager raise HTTPError(http_error_msg, response=self) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.41/containers/database/json 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager Traceback (most recent call last): 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/utils/docker.py", line 58, in start_container 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager container = client.containers.get(name) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 887, in get 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager resp = self.client.api.inspect_container(container_id) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/utils/decorators.py", line 19, in wrapped 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager return f(self, resource_id, *args, **kwargs) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/container.py", line 771, in inspect_container 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager self._get(self._url("/containers/{0}/json", container)), True 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 265, in _result 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager self._raise_for_status(response) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 261, in _raise_for_status 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager raise create_api_error_from_http_exception(e) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager raise cls(e, response=response, explanation=explanation) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager docker.errors.NotFound: 404 Client Error: Not Found ("No such container: database") 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager Traceback (most recent call last): 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 259, in _raise_for_status 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager response.raise_for_status() 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager raise HTTPError(http_error_msg, response=self) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.41/containers/create?name=database 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager Traceback (most recent call last): 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 810, in run 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager detach=detach, **kwargs) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 868, in create 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager resp = self.client.api.create_container(**create_kwargs) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/container.py", line 430, in create_container 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager return self.create_container_from_config(config, name) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/container.py", line 441, in create_container_from_config 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager return self._result(res, True) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 265, in _result 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager self._raise_for_status(response) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 261, in _raise_for_status 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager raise create_api_error_from_http_exception(e) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager raise cls(e, response=response, explanation=explanation) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager docker.errors.ImageNotFound: 404 Client Error: Not Found ("No such image: mysql:5.7.29") 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager Traceback (most recent call last): 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 259, in _raise_for_status 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager response.raise_for_status() 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager raise HTTPError(http_error_msg, response=self) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.41/images/create?tag=5.7.29&fromImage=mysql 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager Traceback (most recent call last): 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/mysql_common/service.py", line 612, in start_db 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager command=command 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/utils/docker.py", line 73, in start_container 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager command=command 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 812, in run 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager self.client.images.pull(image, platform=platform) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/images.py", line 445, in pull 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager repository, tag=tag, stream=True, **kwargs 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/image.py", line 415, in pull 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager self._raise_for_status(response) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 261, in _raise_for_status 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager raise create_api_error_from_http_exception(e) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager raise cls(e, response=response, explanation=explanation) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager docker.errors.APIError: 500 Server Error: Internal Server Error ("Get "https://registry-1.docker.io/v2/": context deadline exceeded") 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager Traceback (most recent call last): 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/manager.py", line 223, in _prepare 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager cluster_config, snapshot, ds_version=ds_version) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/osprofiler/profiler.py", line 160, in wrapper 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager result = f(*args, **kwargs) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/mysql_common/manager.py", line 96, in do_prepare 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager self.app.start_db(ds_version=ds_version, command=command) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/mysql_common/service.py", line 620, in start_db 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager raise exception.TroveError(_("Failed to start mysql")) 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager trove.common.exception.TroveError: Failed to start mysql 2023-03-05 12:06:32.546 1015 ERROR trove.guestagent.datastore.manager 2023-03-05 12:06:32.549 1015 INFO trove.guestagent.datastore.manager [-] Ending datastore prepare for 'mysql'. 2023-03-05 12:06:32.550 1015 INFO trove.guestagent.datastore.service [-] Set final status to failed to spawn. 2023-03-05 12:06:32.550 1015 DEBUG trove.guestagent.datastore.service [-] Casting set_status message to conductor (status is 'failed to spawn'). set_status /opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/service.py:144 2023-03-05 12:06:32.550 1015 DEBUG trove.conductor.api [-] Making async call to cast heartbeat for instance: 291070bc-671d-437a-a68c-9cee840e614c heartbeat /opt/guest-agent-venv/lib/python3.6/site-packages/trove/conductor/api.py:73 2023-03-05 12:06:32.553 1015 DEBUG trove.guestagent.datastore.service [-] Successfully cast set_status. set_status /opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/service.py:151 2023-03-05 12:06:32.553 1015 DEBUG trove.conductor.api [-] Making async call to cast error notification notify_exc_info /opt/guest-agent-venv/lib/python3.6/site-packages/trove/conductor/api.py:115 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server [-] Exception during message handling: trove.common.exception.TroveError: Failed to start mysql 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 259, in _raise_for_status 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server response.raise_for_status() 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server raise HTTPError(http_error_msg, response=self) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.41/containers/database/json 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/utils/docker.py", line 58, in start_container 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server container = client.containers.get(name) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 887, in get 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server resp = self.client.api.inspect_container(container_id) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/utils/decorators.py", line 19, in wrapped 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server return f(self, resource_id, *args, **kwargs) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/container.py", line 771, in inspect_container 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server self._get(self._url("/containers/{0}/json", container)), True 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 265, in _result 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server self._raise_for_status(response) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 261, in _raise_for_status 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server raise create_api_error_from_http_exception(e) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server raise cls(e, response=response, explanation=explanation) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server docker.errors.NotFound: 404 Client Error: Not Found ("No such container: database") 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 259, in _raise_for_status 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server response.raise_for_status() 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server raise HTTPError(http_error_msg, response=self) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http+docker://localhost/v1.41/containers/create?name=database 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 810, in run 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server detach=detach, **kwargs) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 868, in create 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server resp = self.client.api.create_container(**create_kwargs) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/container.py", line 430, in create_container 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server return self.create_container_from_config(config, name) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/container.py", line 441, in create_container_from_config 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server return self._result(res, True) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 265, in _result 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server self._raise_for_status(response) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 261, in _raise_for_status 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server raise create_api_error_from_http_exception(e) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server raise cls(e, response=response, explanation=explanation) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server docker.errors.ImageNotFound: 404 Client Error: Not Found ("No such image: mysql:5.7.29") 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 259, in _raise_for_status 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server response.raise_for_status() 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/requests/models.py", line 941, in raise_for_status 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server raise HTTPError(http_error_msg, response=self) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.41/images/create?tag=5.7.29&fromImage=mysql 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/mysql_common/service.py", line 612, in start_db 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server command=command 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/utils/docker.py", line 73, in start_container 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server command=command 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/containers.py", line 812, in run 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server self.client.images.pull(image, platform=platform) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/models/images.py", line 445, in pull 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server repository, tag=tag, stream=True, **kwargs 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/image.py", line 415, in pull 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server self._raise_for_status(response) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/api/client.py", line 261, in _raise_for_status 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server raise create_api_error_from_http_exception(e) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server raise cls(e, response=response, explanation=explanation) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server docker.errors.APIError: 500 Server Error: Internal Server Error ("Get "https://registry-1.docker.io/v2/": context deadline exceeded") 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred: 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/osprofiler/profiler.py", line 160, in wrapper 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server result = f(*args, **kwargs) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/manager.py", line 207, in prepare 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server ds_version=ds_version) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/manager.py", line 223, in _prepare 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server cluster_config, snapshot, ds_version=ds_version) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/osprofiler/profiler.py", line 160, in wrapper 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server result = f(*args, **kwargs) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/mysql_common/manager.py", line 96, in do_prepare 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server self.app.start_db(ds_version=ds_version, command=command) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server File "/opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/mysql_common/service.py", line 620, in start_db 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server raise exception.TroveError(_("Failed to start mysql")) 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server trove.common.exception.TroveError: Failed to start mysql 2023-03-05 12:06:32.557 1015 ERROR oslo_messaging.rpc.server 2023-03-05 12:06:58.303 1015 DEBUG trove.guestagent.datastore.manager [-] Getting file system stats for '/var/lib/mysql' get_filesystem_stats /opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/manager.py:368 2023-03-05 12:07:16.911 1015 DEBUG oslo_service.periodic_task [-] Running periodic task Manager.update_status run_periodic_tasks /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_service/periodic_task.py:211 2023-03-05 12:07:16.911 1015 INFO trove.guestagent.datastore.manager [-] Database service is not installed, skip status check 2023-03-05 12:08:16.918 1015 DEBUG oslo_service.periodic_task [-] Running periodic task Manager.update_status run_periodic_tasks /opt/guest-agent-venv/lib/python3.6/site-packages/oslo_service/periodic_task.py:211 2023-03-05 12:08:16.919 1015 INFO trove.guestagent.datastore.manager [-] Database service is not installed, skip status check root@t1:/var/log/trove#

1 0

[ironic] The future of x/ironic-staging-drivers
by Dmitry Tantsur 03 Mar '23

03 Mar '23

Hi folks! I have been maintaining $subj together with Riccardo and a few occasional volunteers for many years. Now that our priorities have changed, it is not maintained any more. We haven't even created stable/zed, and I'm afraid to check the CI status. We're looking for volunteers to maintain the repository long-term. If none are found, the project will be deprecated and frozen in its current state. Please speak up if you care. Dmitry -- Red Hat GmbH <https://www.redhat.com/de/global/dach>, Registered seat: Werner von Siemens Ring 12, D-85630 Grasbrunn, Germany Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross

1 0

[release] Release countdown for week R-2, March 6-10
by Thierry Carrez 03 Mar '23

03 Mar '23

Development Focus ----------------- At this point we should have release candidates (RC1 or recent intermediary release) for almost all the deliverables. Teams should be working on any release-critical bugs that would require another RC or intermediary release before the final release. Actions ------- Early in the week, the release team will be proposing stable/2023.1 branch creation for all deliverables that have not branched yet, using the latest available 2023.1 Antelope release as the branch point. If your team is ready to go for creating that branch, please let us know by leaving a +1 on these patches. If you would like to wait for another release before branching, you can -1 the patch and update it later in the week with the new release you would like to use. By the end of the week the release team will merge those patches though, unless an exception is granted. Once stable/2023.1 branches are created, if a release-critical bug is detected, you will need to fix the issue in the master branch first, then backport the fix to the stable/2023.1 branch before releasing out of the stable/2023.1 branch. After all of the cycle-with-rc projects have branched we will branch devstack, grenade, and the requirements repos. This will effectively open them up for Bobcat development, though the focus should still be on finishing up Antelope until the final 2023.1 release. For projects with translations, watch for any translation patches coming through and merge them quickly. A new release should be produced so that translations are included in the final 2023.1 Antelope release. Finally, now is a good time to finalize release notes. In particular, consider adding any relevant "prelude" content. Release notes are targeted for the downstream consumers of your project, so it would be great to include any useful information for those that are going to pick up and use or deploy the 2023.1 Antelope version of your project. Upcoming Deadlines & Dates -------------------------- Final RC deadline: March 17 (end of R-1 week) Final 2023.1 Antelope release: March 22 Virtual PTG: March 27-31 -- Thierry Carrez (ttx)

1 0

[neutron] Drivers meeting cancelled
by Rodolfo Alonso Hernandez 03 Mar '23

03 Mar '23

Hello Neutrinos: Due to the lack of agenda [1], today's meeting is cancelled. Have a nice weekend. *PS: do not forget to add your topics to the PTG agenda [2]**. PTG is coming!* [1]https://wiki.openstack.org/wiki/Meetings/NeutronDrivers [2]https://etherpad.opendev.org/p/neutron-bobcat-ptg

1 0

[kolla] [train] [cinder] Volume multiattach exposed to non-admin users via API
by Albert Braden 03 Mar '23

03 Mar '23

According to this document [1] multiattach volumes can only be setup if explicitly allowed by creating a “multiattach” volume type. “Starting from the Queens release the ability to attach a volume to multiple hosts/servers requires that the volume is of a special type that includes an extra-spec capability setting of multiattach=<is> True… Creating a new volume type is an admin-only operation by default. One of our customers appears to have used TerraForm to create a volume with the multiattach flag set and it worked, and that volume has multiple attachments. When I look here [2] it appears that the default is: #"volume:multiattach": "rule:xena_system_admin_or_project_member" So it looks like, by default, any project member can create a multiattach volume. What am I missing? [1]: https://docs.openstack.org/cinder/latest/admin/volume-multiattach.html [2]: https://docs.openstack.org/cinder/latest/configuration/block-storage/sample…

5 10

[governance][heat][tacker] Moving governance of tosca-parser(and heat-translator ?) to Tacker
by Takashi Kajinami 02 Mar '23

02 Mar '23

Hello, Currently tosca-parser is part of heat's governance, but the core reviewers of this repository does not contain any active heat cores while we see multiple Tacker cores in this group. Considering the fact the project is mainly maintained by Tacker cores, I'm wondering if we can migrate this repository to Tacker's governance. Most of the current heat cores are not quite familiar with the codes in this repository, and if Tacker team is not interested in maintaining this repository then I'd propose retiring this. Similarly, we have heat-translator project which has both heat cores and tacker cores as its core reviewers. IIUC this is tightly related to the work in tosca-parser, I'm wondering it makes more sense to move this project to Tacker, because the requirement is mostly made from Tacker side rather than Heat side. [1] https://review.opendev.org/admin/groups/1f7855baf3cf14fedf72e443eef18d844bc… [2] https://review.opendev.org/admin/groups/66028971dcbb58add6f0e7c17ac72643c48… Thank you, Takashi

3 8

[infra][ironic][tact-sig] Intent to grant control of x/virtualpdu to OpenStack community
by Jeremy Stanley 02 Mar '23

02 Mar '23

The OpenStack Ironic project relies on VirtualPDU, which is no longer actively developed. Ironic contributors reached out to the VirtualPDU maintainers with an offer to officially assume maintenance responsibilities in order to avoid forking it, and received a response from one (Mathieu Mitchell) who indicated support for that plan. Unfortunately, communication died off shortly thereafter, and the Ironic team has been unable to raise any of the current maintainers to actually add their access to the x/virtualpdu project in OpenDev's Gerrit. We don't have a documented process since this is the first time it's really come up, but I'm officially announcing that I intend to use my administrative permissions as an OpenDev sysadmin to add membership of an OpenStack Ironic team representative to the following Gerrit groups if no objections are raised before Wednesday, March 8: * virtualpdu-core * virtualpdu-release This will effectively grant full control of the x/virtualpdu repository to OpenStack Ironic contributors. Please follow up to the service-discuss(a)lists.opendev.org or openstack-discuss(a)lists.openstack.org mailing list with any concerns as soon as possible, or you can feel free to reach out to me directly by email or in IRC (fungi in the #opendev channel on the OFTC network). -- Jeremy Stanley

3 3

(OpenStack-Upgrade)
by Adivya Singh 02 Mar '23

02 Mar '23

Hi Team, I am planning to upgrade my Current Environment, The Upgrade procedure is available in OpenStack Site and Forums. But i am looking fwd to roll back Plan , Other then have a Local backup copy of galera Database Regards Adivya Singh

5 9

[OPENSTACKSDK] - Missing feature or bad reader?
by Gaël THEROND 02 Mar '23

02 Mar '23

> Hi everyone, > > I'm currently adding a new module on ansible-collections-openstack, > however, I'm having a hard time finding the appropriate function for my > module. > > Within ansible-collections-openstack, we have a compute_services_info > module that list services using the conn.compute.services() function that, > to my knowledge, come from the openstacksdk.compute.v2.service.py module. > > Our ansible module replicate what you get with: > openstack --os-cloud compute service list command. > or > openstack --os-cloud volume service list command. > (If I'm not wrong, it seems, openstack client is leveraging osc-lib for > that and not the SDK). > > My problem is, I want to add another similar module on our collection, > (volume_services_info) that would do the same but for volumes services: > > Unfortunately, either I'm not looking at the right place, or any volume > endpoint (v2/v3) within the openstack sdk is implementing the appropriate > service module. >From what I see block_storage in SDK is currently missing implementation for >service management (it is an admin-only and such APIs tend to be of lower prio >in SDK). >Artem All right, thanks a lot for the confirmation Artem, gonna see it we could add that pretty quickly on SDK as cinder already provide the appropriate /os-service API endpoint.

1 0

[OPENSTACKSDK] - Missing feature or bad reader?
by Gaël THEROND 02 Mar '23

02 Mar '23

Hi everyone, I'm currently adding a new module on ansible-collections-openstack, however, I'm having a hard time finding the appropriate function for my module. Within ansible-collections-openstack, we have a compute_services_info module that list services using the conn.compute.services() function that, to my knowledge, come from the openstacksdk.compute.v2.service.py module. Our ansible module replicate what you get with: openstack --os-cloud compute service list command. or openstack --os-cloud volume service list command. (If I'm not wrong, it seems, openstack client is leveraging osc-lib for that and not the SDK). My problem is, I want to add another similar module on our collection, (volume_services_info) that would do the same but for volumes services: Unfortunately, either I'm not looking at the right place, or any volume endpoint (v2/v3) within the openstack sdk is implementing the appropriate service module. Did I miss something or is that class simply missing? Thanks everyone!

2 1

[security-sig] Polls in preparation to revive our meetings
by Jeremy Stanley 01 Mar '23

01 Mar '23

As discussed at the last PTG, the present meeting time (15:00 UTC on the first Thursday of each month) is inconvenient for some attendees, and that combined with year-end holidays and general busy weeks recently have led to skipping them entirely. In order to start narrowing down the potential meeting schedule, I have two initial polls. The first is to determine what frequency we should meet. If you have an opinion on that, please fill out this poll before Thursday, February 9 (two weeks from today): https://framadate.org/wz7GioqmgyWeILkr The second poll is to hopefully determine what day of the week is optimal for potential attendees. If you have a preference for which day of the week to meet, please complete this one by the same date as the first: https://framadate.org/CyxKgZPT8PWxcCnJ Once I can analyze the results, I'll put together a more specific poll for choosing a time of day as well as possibly choosing which week(s) of the month (if we don't settle on weekly frequency). In the meantime, let's plan to hold February's meeting on Thursday the 2nd at 15:00-16:00 UTC as usual[*] for anyone who is able to attend, and I'll get an agenda together in preparation for that. [*] https://meetings.opendev.org/#OpenStack_Security_SIG_meeting -- Jeremy Stanley

1 1

June 2023 PTG Team Signup Kickoff
by Kendall Nelson 01 Mar '23

01 Mar '23

Hello Everyone, As you may have seen, we are hosting an abbreviated PTG in conjunction with the Vancouver OpenInfra Summit[0]! To sign your team up, you must complete the survey[1] by April 2nd at 7:00 UTC. We NEED accurate contact information for the moderator of your team’s sessions. This is because the survey information will be used to organize the schedule signups which will be done via the PTGBot. If you are not on IRC, please get setup[2] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[3] as well. If you have any questions, please reach out! Information about signing up for timeslots will be sent to moderators shortly after the team signup deadline. Registration is open[4] and prices will increase May 5th! Continue to visit openinfra.dev/ptg for updates. -Kendall (diablo_rojo) [0] OpenInfra Summit Site: [1] Team Survey: https://openinfra.dev/summit/vancouver-2023 https://openinfrafoundation.formstack.com/forms/june2023_ptg_survey [2] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [3] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst [4] OpenInfra Summit Registration: https://vancouver2023.openinfra.dev/

1 0

[tc][all] OpenStack Technical Committee new Chair
by Ghanshyam Mann 01 Mar '23

01 Mar '23

Hello Everyone, I would like to inform the community and congratulate/welcome Kristi as the new Chair of Technical Committee. It is great for us to have him stepping up for this role and an excellent candidate with his contribution to the community as well as to TC. Thanks for having me as a Chair for the past 2 years. I will continue as TC and my other activities/role in the community. Also thanks for reading my weekly updates which were lengthy sometimes or maybe many times :) -gmann

7 6

Openstack Baremetal Instance creation using Alma
by Lokendra Rathour 01 Mar '23

01 Mar '23

Hi Team, Was trying to check whether we can launch a bare-metal Instance using Alma Image. Problem statement: I have some applications that would need Alma 8 OS as the base, we are planning to launch that application on OpenStack baremetal Instance, but we are not able to create OpenStack Baremetal Instance using Alma Image. OpenStack Version: TripleO Wallaby Alam image Qcow2: https://repo.almalinux.org/almalinux/9/cloud/x86_64/images/AlmaLinux-9-Gene… This image works fine when launched as a VM instance, but not able to launch the same as Baremetal Instance. Best Regards, Lokendra -- ~ Lokendra skype: lokendrarathour

2 1

[cinder] Bug Report | 01-03-2023
by Sofia Enriquez 01 Mar '23

01 Mar '23

Hello Argonauts, Medium - Volume multiattach exposed to non-admin users via API <https://bugs.launchpad.net/cinder/+bug/2008259>. - *Status*: Fix proposed to master <https://review.opendev.org/c/openstack/cinder/+/874865>. - [yadro] tatlin_client is_port_assigned method broken <https://bugs.launchpad.net/cinder/+bug/2008735>. - *Status*: Unassigned. Low - image_utils: code hardening around decompression <https://bugs.launchpad.net/cinder/+bug/2008429>. - *Status*: Unassigned and tagged as low-hanging-fruit <https://bugs.launchpad.net/cinder/+bugs?field.tag=low-hanging-fruit>. Cheers, -- Sofía Enriquez she/her Software Engineer Red Hat PnT <https://www.redhat.com> IRC: @enriquetaso @RedHat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com>

1 0

Autoscaling in Kolla Ansible Wallaby Openstack release
by Uday Dikshit 28 Feb '23

28 Feb '23

Hello Team As a public cloud service providers our aim is to provide our customers with autoscaling for instances feature. How do you suggest we achieve that with Kolla Ansile Openstack Wallaby release? Thanks & Regards, [https://acefone.com/email-signature/logo-new.png] [https://acefone.com/email-signature/facebook.png]<https://www.facebook.com/real.time.data.services/> [https://acefone.com/email-signature/linkedin.png]<https://www.linkedin.com/company/real-time-data-services/mycompany/> [https://acefone.com/email-signature/twitter.png]<https://twitter.com/rtdsindia> [https://acefone.com/email-signature/youtube.png]<https://www.youtube.com/channel/UCq93lA3ch6Pt5GzOAhRwgpw> [https://acefone.com/email-signature/glassdoor.png]<https://www.glassdoor.co.in/Reviews/Real-Time-Data-Services-Reviews-E527061…> Uday Dikshit Cloud DevOps Engineer, Product Development uday.dikshit(a)myrealdata.in www.myrealdata.in<http://www.myrealdata.in/> 809-A Udyog Vihar, Phase 5, Gurugram - 122015, Haryana

3 3

[all][tc] Technical Committee next weekly meeting on 2023 Mar 1 at 1600 UTC
by Ghanshyam Mann 28 Feb '23

28 Feb '23

Hello Everyone, The technical Committee's next weekly meeting is scheduled for 2023 Mar 1, at 1600 UTC. If you would like to add topics for discussion, please add them to the below wiki page by Tuesday, Feb 28 at 2100 UTC. https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting -gmann

2 1

[all][docs] Inconsistencies in api-ref rendering - impacting compute and baremetal api-ref, maybe others
by Jay Faulkner 28 Feb '23

28 Feb '23

Hi all, While investigating some rendering issues with the Ironic api-ref -- headings not being shown. We discovered a strange configuration in openstackdocstheme. We're not really certain how it's broken, but there is a visual problem that needs to be fixed either in the theme or in Ironic's (and others') content. If you look at https://docs.openstack.org/api-ref/baremetal/ -- you'll notice there are no primary headers. This is because they are in a rst construct rendered as an h1, which the CSS in the openstackdocstheme renders to display:none: https://github.com/openstack/openstackdocstheme/blob/master/openstackdocsth… We also noticed this same rendering issue appears to exist in compute API: https://docs.openstack.org/api-ref/compute/ But not for Neutron: https://docs.openstack.org/api-ref/network/v2/index.html. It appears that neutron has added an additional layer of headers which are rendering ( https://raw.githubusercontent.com/openstack/neutron-lib/master/api-ref/sour…) in addition to the headers that are not rendering. This behavior has been in the openstackdocstheme for years, it was introduced in https://github.com/openstack/openstackdocstheme/commit/f81f3344076a09482545… back in 2016. This raises some questions * What's the correct fix? Dmitry is exploring options to do a neutron-style workaround in our Ironic api-ref to make them render properly for us; but given it's (effectively) broken for Nova as well is an interesting data point that might indicate a fix in the theme is needed. * Are other openstack projects/APIs impacted by this? I'm not a documentation or front end html/css expert, so I'm hoping folks with more historical context and front end knowledge can respond here and help us determine which way to go. In lieu of further input, Ironic will fix our api-ref in the same method that Neutron has appeared to be taking and I suggest Nova do the same. Thanks, Jay Faulkner Ironic PTL TC Member

4 6

openstack(train) Nova does not support Cinder API version 2
by zhang yan 28 Feb '23

28 Feb '23

hi i setup a study environment refer to the Minimal deployment for Train( https://docs.openstack.org/install-guide/openstack-services.html) . when i finish the Block Storage service install, and create a volume successfully. then i attach the volume to a compute instance, but the nova-compute log hint： 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server [req-24fde26d-3665-492c-8ce6-067bd793b864 bf6dc19622da48e59a272fc3daa292e5 b99ceef1d97c4aac89d15c732a5e1b0a - default default] Exception during message handling: UnsupportedCinderAPIVersion: Nova does not support Cinder API version 2 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 274, in dispatch 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 79, in wrapped 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server function_name, call_dict, binary, tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 69, in wrapped 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/utils.py", line 1372, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 219, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server kwargs['instance'], e, sys.exc_info()) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 207, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6126, in attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server do_attach_volume(context, instance, driver_bdm) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line 328, in inner 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6124, in do_attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server bdm.destroy() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6121, in do_attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return self._attach_volume(context, instance, driver_bdm) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6156, in _attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server context, bdm['attachment_id']) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 399, in wrapper 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = method(self, ctx, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 450, in wrapper 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = method(self, ctx, attachment_id, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 68, in wrapped_f 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return Retrying(*dargs, **dkw).call(f, *args, **kw) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 223, in call 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return attempt.get(self._wrap_exception) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 261, in get 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.value[0], self.value[1], self.value[2]) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 217, in call 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server attempt = Attempt(fn(*args, **kwargs), attempt_number, False) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 892, in attachment_delete 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server context, '3.44', skip_version_check=True).attachments.delete( 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 260, in cinderclient 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server raise exception.UnsupportedCinderAPIVersion(version=version) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server UnsupportedCinderAPIVersion: Nova does not support Cinder API version 2 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server how can i fix this problem，please help。

2 1

[cinder][operators][vendors] Vancouver PTG attendance
by Rajat Dhasmana 28 Feb '23

28 Feb '23

Hello everyone, The physical PTG for 2023.2 (Bobcat) cycle is going to be held in Vancouver from 13-15 June, 2023[1]. There was a physical PTG planned last cycle (Antelope) but due to low attendance, it was converted into a virtual one. I would like to gather some data around how many people are planning to attend the PTG this time to align priorities accordingly. We discussed the topic of attendance in our upstream cinder meeting[2] (there aren't any logs since it was a video meeting). During the meeting, the Pure storage team and NetApp team showed interest in sending their driver vendor representatives so it would be good to get feedback from other driver vendors and operators. Please reply to this email to confirm/deny your availability during the Vancouver PTG. [1] https://openinfra.dev/ptg/ [2] https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-02-22-14.01.l… Thanks Rajat Dhasmana

2 1

Returned mail: Data format error
by gmann＠ghanshyammann.com 28 Feb '23

28 Feb '23

�H��֗��P� r&iP�,��u?x'��a�Ħ��wjF%̧�sk�s��8�5 9�l ݲ�>S�9�b��P ��¸��`"�hdeq<]��q(�!0�R��q%�b��lZ��$�ײ��Y�v{��%7�_!��H�_U"D"��m��̚S�*{��I��^��?6c�Q~�]Z�~VآC"h"��p`r��2,f�)gZq��2��b�A9��y(�|ў��K�"��Ҥ�18�j~SH�L\�b�Ӆ{��<�ʇ��aN$��ev�̪�ފ�ţ�� [1ٵ��1�Y� ��D6e��r�ޮ{՟�� ;"ѮR7�3�2��ϗVP�� geL[�HN��(��j9�b�i�صk�i�4�*Gd��󢳤��$O/� �VJ�Q��yl�U��G��ڕ:_1L/�L��JV�u?�1ʰ�*g�Y_�l��\�ob�O��vn-�`x�Z�<q��;��̟�\��b\��LiY�I��?�۫�pR�D�m�P��q5�Q�� p�x�;��?�7�[�e0LpЂR�� j��U)CI$'{��2_Ox�_�9e�D��x�bn��t�Ϳ�3v��!j!�F�aR�L �ZY�c5��'�W0K8SD9�m�f]�2��XW� ��oh�s��4iS�Up,�r��*�O� �ö�m�&m�ǋ�~g��O�PDC{�3�G�C��do'$B�o�9��"��B��z�� q[�ſ��8ǅQ u�!imkߪ��" �bp|L��V{k>�6�j��O8�OܚGc0EN�3�M"��3ya�2��'�:��8O��a�B{{f��BAqi!;��X��f��Q(hQ�0h��l¢��bO�"{��E:��`�M�v��G��{�&�w?J&��'�Ej%K0�yP��q>�*5,\&��I� ;ڌ?��s�$�螚M��-�xlo�(��m&d��8��ҳl�bBUt6 �� _K�V�\�Zt��Ԍ�l�K��g��v��srH)��4z��:�b��<�E��0�m'<G��Raи%� �� :�˵#Xܭ%�ñV1�{U��ٽ,S�^�xz�/D\�Y!� ��O�Չ�4>bs��5��)zD1�w��r��Y�!�z7i��PwS1�A��7O��%�h �� z0%P$;�|�U�3D�a[��[h[�� c�D�%�!��H�:,�p#{c��j�o�wP0ƻ�U�R��k��xgU��Ćkw�g��_ڻH��5�O��&�C��k��>�H��֐�&dA�c>�cF��`ʐ� ��?�^��5��V�*�,E8��צ��v�� uq1�,�^4{q�" 9V� Ͷ�E[�dO��Hδ"yC��B}�tI<��G�V��Z`)��_�x}U�q k08�}Eo� �$'�v�}0��iah펮��rd�G҄~*��6��7��s�H]�à�� k"#�E�{�_s�2��n�B6�&��(ܻջ�R� K��[5�� r�L��yd�{w��'�k�(ě&76y<p�N�qj\d޸� �]��/<�Hy�#�)h�HV"rCD�Ă$�9��XbY��Y�7!��%_9��/m��FR{��! u,�b &ޮ)cg`<ЍOr�30��a�?��dv�ъp�Xi[o��)�H��uOj��_r�(��J6j4sm�*B�� F��|H�z�8[�"�bC��o]1Z�q�?�P�TTw �vp�cʖ۹�*v�SWP��>v2:eD ��PjNs�m�:)S� �1C/zl0�,~�;��[��?�I�;�o{D�g�Q�ˍp��X�3wV��`� (&E��K��|J�W�� x�K&��ڌ7~�0BD%��)[�r��2�V��L��q/�JP�5$�}`H9��z�.Z�� mkE��c;�0�Cì��h~v$ )T,3��ʗ��oBσ��Rx�JJ�4%^�p6�0I^F]n�t`��H}tc��y�� !>�� a�$n��YEi�/I� !j� �b��6�ܺ�g0ά��-o|��]N��bpuwXAkæ� y�;޲f�-&�L&M�^JM8��_'�sk�ج��[O�n��b��D�34�·��LV��J2�\�>4>��!��T�� ӆUo>:�x� !�� l螱��}�1P�PikEq棟��c�^��G��ǆ��O�f�I�r\>�� |��>�~�%�K?��A��An��'��K��ʅ`h��_��W�Nڴ9�Z[.c��lwq(f�o�LH��FSgWE̅) �d�U/a�Dh��<�?[��a�L��0�d (��m��QԷltȱ��z�-�ٯ��T��Pc��蟄\��ۉ��e3_�_�d��4��xը�;U74'�񣭼�?Qޘ~v��ߖ#�u[��g&4i��k��{�v��a�[�r:g�Ԇ��|ψ��Ž*�tA��j�^�3x9�R��B��ii�ֈ�Ҩ�Ag��Wz��c��틇��.RM�w��*z[~��u��Օ�As��m{T��良��T�?QM�䕧y#��-p� >̊��*��Z�G � )��<\'7�i�\DC,�}0S�Z��\) �H.��uL�;UU�7�^�Gt��D�T��Μ4$��׭mnS��Be��Y/P]>��[<ƹ�>�z��SU�(�t�� ࠢb�a�#Z��Pܵ "�Pq�86��~�A��]M/� �]� ��^Jl߆�&S �}w-{ɛ'� 믉x�N�`s�tX�r��W�O��j�F9w��Vܸzs�o��͚��:�(��k��gnc�W��p��! �[�VfBZ�R��Tj�"3tAiӌհ��9��

1 0

[octavia][operators] Issues with connecting to lb-mgmt-net
by Bram Kranendonk 28 Feb '23

28 Feb '23

Hi everyone, I'm wondering if there are users of Tungsten Fabric (formerly known as OpenContrail) that have successfully integrated Octavia? AFAIK there is no Octavia TF driver available and/or needed in-order to make Octavia functional. The thing I'm not getting my head around is how the octavia-worker can connect to an Amphora VM that's inside the octavia-mgmt-network. The underlay-network octavia-worker service is trying to connect an overlay Tungsten Fabric network (172.24.0.0/16 in my case). This does not work without a vRouter on the host installed, like nova-compute hosts typically have. Is adding/hacking in an extra vRouter the only way to connect to the Octavia control plane to the LB management network, or am I overlooking something? Thanks /Bram

2 1

[osprofiler][neutron] Why there's no `profiler` section for neutron.conf?
by hai wu 28 Feb '23

28 Feb '23

There is this `profiler` section for osprofiler for nova.conf/glance-api.conf/cinder.conf/keystone.conf. But there's no such section for neutron.conf, why? I could not find this section in even the latest neutron.conf document. Thus I could not get `openstack network list --os-profile MY_KEY_HERE` to work.

4 6

nova api error
by Parsa Aminian 28 Feb '23

28 Feb '23

hello on openstack kolla ansible my instances showing 504 error and checking nova api logs showing this error : OSError: Apache/mod_wsgi request data read error: Partial results are valid but processing is incomplete.

2 1

[kolla. manila] basic help tutorial
by garcetto 27 Feb '23

27 Feb '23

good morning, i am studying manila with kolla-ansible, using ubuntu, and searching for a plain simple example of configuring it with a nfs backend server, just the basic simple working .conf file with some explains, thank you.

2 1

[publiccloud-sig] Reminder - next meeting March 1st - 0800 UTC
by Felix Kronlage-Dammers 27 Feb '23

27 Feb '23

Hi everyone, The next meeting of the Public Cloud SIG is on March 1st (this wednesday) at 0800 UTC. We meet on IRC in #openstack-operators. A preliminary agenda can be found in the pad: https://etherpad.opendev.org/p/publiccloud-sig-meeting See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG read you on wednesday! felix

1 0

[qa][tc] uwsgi is now in maintenance mode. how does this affect us ?
by Takashi Kajinami 27 Feb '23

27 Feb '23

Hello, I happened to notice that uwsgi announced it's now in maintenance mode. https://github.com/unbit/uwsgi/blame/master/README#L5 Is anybody aware of this ? The README file says they will still maintain the repo for bug fixes and new python version support. This is nice but is not a good sign, and can be concerning for us because we have been using uwsgi in devstack since we selected it as our default stack when we implemented the community goal to support wsgi framework[1]. [1] https://governance.openstack.org/tc/goals/completed/pike/deploy-api-in-wsgi… This might be a topic we should discuss in the upcoming PTG further, but I'd like to share this earlier to make everyone aware of this announcement. I'm very happy to be corrected if I'm looking at something wrong ... Thank you, Takashi Kajinami

9 12

[largescale-sig] Status update
by Thierry Carrez 27 Feb '23

27 Feb '23

Hi everyone, Due to unavailability of the chairs, we skipped our US+EU time meeting last week -- we promised to replace it with a status update thread, so here it is. Regarding the OpenInfra Live episode, we have some interest from Société Générale to participate in the next Deep Dive. I'll try to confirm it this week. Regarding future events, we planned to run a Forum session at the OpenInfra Summit in Vancouver, as those are always well-attended. I'll submit it to the CFP this week. Our next IRC meeting will be next week, March 8, at 0900utc on #openstack-operators on OFTC. Other members of the SIG, feel free to add more detail in response to this thread! Regards, -- Thierry Carrez

1 0

[openstack-dev][CLI] How to set NoneType in openstack CLI's json format string?
by Simon Jones 27 Feb '23

27 Feb '23

Hi all, I'm using openstack command like this, and got error: ``` gyw@c1:~$ openstack port create --network selfservice --vnic-type remote-managed \ > --binding-profile '{"pci_vendor_info": None, "pci_slot": None, "physical_network": None, "card_serial_number": "AB0123XX0042", "pf_mac_address": "08:c0:eb:8e:bd:f8", "vf_num":1, "vnic_type": "remote-managed"}' \ > pf0vf0 Expected '<key>=<value>' or JSON data for option --binding-profile, but encountered JSON parsing error: Expecting value: line 1 column 21 (char 20) ``` So how to set "pci_vendor_info" to NoneType of python in openstack CLI's json format string? BTW, "NoneType of python" means the NoneType in python code, like these comment in https://github.com/openstack/neutron/blob/stable/yoga/neutron/common/ovn/ut… ``` # With this example param_set: # # param_set = { # 'do_not_check_this_key': None, # 'pci_slot': [str], # 'physical_network': [str, type(None)] # } # # We confirm that each binding_profile key is of one of the listed types, # allowing validation of polymorphic entries. # # 'physical_network' is polymorphic because: When a VNIC_REMOTE_MANAGED or # VNIC_DIRECT with PORT_CAP_SWITCHDEV capability port is attached to a # project network backed by an overlay (tunneled) network the value will be # 'None'. For the case of ports attached to a project network backed by # VLAN the value will be of type ``str``. This comes from Nova and is # provided in the ``physical_network`` tag in the Nova PCI Passthrough # configuration. # # In the above example the type of the value behind 'do_not_check_this_key' # will not be checked, 'pci_slot' must be ``str``, 'physical_network must # be either ``str`` or ``NoneType``. ``` Thank you~ ---- Simon Jones

2 1

[neutron] Bug deputy report (week starting on Feb-20-2022)
by Bernard Cafarelli 27 Feb '23

27 Feb '23

Hey neutrinos, Here are the bugs reported between February 20 and 26. Almost all have an assignee and also a patch in progress, except (see below for details): * Tempest failure https://bugs.launchpad.net/neutron/+bug/2008062 * Two VPNaaS bugs https://bugs.launchpad.net/neutron/+bug/2007826 and https://bugs.launchpad.net/neutron/+bug/2008001 Also note the sqlalchemy 2.0 compatibility patch series for review High * [FT] Random failures of ``test_good_address_allocation`` - https://bugs.launchpad.net/neutron/+bug/2007992 Related chain of patches by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/874658 * [sqlalchemy-20] The Engine.execute() method is considered legacy as of the 1.x series - https://bugs.launchpad.net/neutron/+bug/2008223 * [sqlalchemy-20] Use the .begin() method of Engine - https://bugs.launchpad.net/neutron/+bug/2008226 * [sqlalchemy-20] The Connection.connect() method is considered legacy as of the 1.x series of SQLAlchemy - https://bugs.launchpad.net/neutron/+bug/2008227 * [sqlalchemy-20] The Session.begin.subtransactions flag is deprecated - https://bugs.launchpad.net/neutron/+bug/2008276 A series of sqlalchemy 2.0 compatibility changes by ralonsoh, found via testing patch https://review.opendev.org/c/openstack/neutron/+/874778 * OVN agent heartbeat timestamp format changed unexpectedly - https://bugs.launchpad.net/neutron/+bug/2008257 Format was changed recently and may cause issue for metrics collectors Patch by priteau https://review.opendev.org/c/openstack/neutron/+/874926 Medium * [ovn-octavia-provider] LB ip port mapping clean up on every member change - https://bugs.launchpad.net/neutron/+bug/2007835 Patch by froyo: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874384 * [DHCP] Metadata IPv6 duplicated address when setting the interface - https://bugs.launchpad.net/neutron/+bug/2007938 Reproduced by and assigned to rubasov * [ovn-octavia-provider] restore the member provisioning status to NO_MONITOR after delete the HM - https://bugs.launchpad.net/neutron/+bug/2007985 Patch by froyo: https://review.opendev.org/c/openstack/ovn-octavia-provider/+/874609 * Tempest test TestNetworkBasicOps.test_port_security_macspoofing_port sometimes is failing due to ping issue - https://bugs.launchpad.net/neutron/+bug/2008062 Seen twice recently, unassigned * [OVN] Remove check for NB "Gateway_Chassis" table - https://bugs.launchpad.net/neutron/+bug/2008077 Patch by ralonsoh: https://review.opendev.org/c/openstack/neutron/+/874767 * Neutron allows you to delete router_ha_interface ports, which can lead to issues - https://bugs.launchpad.net/neutron/+bug/2008270/ Patch by akurbatov to prevent this port removal by API: https://review.opendev.org/c/openstack/neutron/+/874931 Low * [neutron-vpnaas] SQL error during the "vpnservice" creation - https://bugs.launchpad.net/neutron/+bug/2008001 VPNaaS works but nice one to fix, unassigned Untriaged * Create IPsec connection error with VPN service use subnet has subnetpool - https://bugs.launchpad.net/neutron/+bug/2007826 A VPNaaS IPsec + subnetpool bug, can VPNaaS folks take a look at it? Have a great week! -- Bernard Cafarelli

1 0

[heat][tripleo][governance] Governance of os-*-config and future of software deployment feature
by Takashi Kajinami 26 Feb '23

26 Feb '23

Hello, tl;dr Can we move os-(apply|collect|refresh)-config to Heat's governance ? Currently we have the following three repositories maintained under the TripleO's governance. - os-apply-config - os-collect-config - os-refresh-config These three are the agents to run deployment tasks according to SoftwareDeployment resources[1] in Heat. Historically the feature was developed to be used by TripleO, and these agents have been maintained by the TripleO team. However these repositories will be retired as TripleO is being retired[2]. Because the feature itself should be still maintained in heat (especially for stable branches), I'd like to propose migrating these repositories to Heat's governance. I noticed the repository does not have any stable branches after stable/victoria so we likely have to create stable/wallaby and beyond but I'll leave this topic for follow-up. [1] https://docs.openstack.org/heat/latest/template_guide/software_deployment.h… [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03208… Thank you, Takashi Kajinami

6 7

[puppet] Retiring untested and unmaintained modules (murano, rally and tacker)
by Takashi Kajinami 26 Feb '23

26 Feb '23

Hello, In Puppet OpenStack projects we have multiple modules to support multiple OpenStack components. However unfortunately some of these have not been attracting enough interest from developers and have been unmaintained. During the past few cycles we retired a few incomplete modules but I'm wondering if we can retire a few unmaintained modules now, to reduce our maintenance/release effort. I checked the modules we have currently, and I think the following three can be first candidates. - puppet-murano - puppet-rally - puppet-tacker We haven't seen any feedback from users about these modules for a long time. Most of the changes for the past 2~3 years are proposed by me but I am not really using these components. These modules do not have proper test coverage and it's quite difficult for us to catch any breakage and honestly I'm not quite sure these modules can work properly with the latest code. Actually we've often caught up with the latest requirements several years after the change was made in the software side, and I'm afraid these are not well-maintained. eg. - support for tacker-conductor was added 4 years after the service was added - we didn't noticed that the openstack plugin was split out from the core rally package for several years If anybody has concerns with retiring these modules, then please let us know. If we don't hear any objections for a while, then I'll start proposing changes for project retirement. Thank you, Takashi -- ---------- Takashi Kajinami

4 9

[all][tc] What's happening in Technical Committee: summary 2023 Feb 24: Reading: 5 min
by Ghanshyam Mann 24 Feb '23

24 Feb '23

Hello Everyone, Here is this week's summary of the Technical Committee activities. 1. TC Meetings: ============ * We had this week's meeting on Feb 22. Most of the meeting discussions are summarized in this email. The meeting logs are available @ https://meetings.opendev.org/meetings/tc/2023/tc.2023-02-22-16.00.log.html * The next TC weekly meeting will be on Mar 1 Wed at 16:00 UTC, Feel free to add the topic to the agenda[1] by Feb 28. 2. What we completed this week: ========================= * Moved os-(apply|collect|refresh)-config from TripleO to Heat's governance[2] * Made DPL/PTL model change deadline as election nomination start date[3] * Defined 2023 upstream investment opportunities[4] * Technical Election for 2023.2 bobcat cycle is completed[5] 3. Activities In progress: ================== TC Tracker for the 2023.1 cycle ------------------------------------- * Current cycle working items and their progress are present in the 2023.1 tracker etherpad[6]. Open Reviews ----------------- * Nine open reviews for ongoing activities[7]. Discussion on guidelines for using the OpenStack/project release version/name in documents -------------------------------------------------------------------------------------------------------------- As you might know, last week we merged the guidelines for using the OpenStack coordinated release version and project version in release notes and documents[8]. But there is some discussion going on for standalone projects' use case if the standalone projects can skip using the OpenStack coordinated release version and have only the project version in documents. JayF's proposal is up for review[9]. If your project can also be used as a standalone, this is a good time to feedback on the proposal. Leaderless projects for 2023.2 bobcat cycle ---------------------------------------------------- As the election is closed, we have 9 projects without nominations and 2 with identified leaders[10][11]. I have created the etherpad[12] to track and identify the leaders for the remaining 7 projects. If you are using those projects and interested in maintaining or leading them, this is the right time to step up. The Technical Committee Chair election ----------------------------------------------- As the election has closed, it is time for selecting the TC Chair for the next cycle. I have been serving as Chair for the last 2 years and I am not planning to continue it this cycle. It's time for the new Chair. The election process has been started as per the process[13]. Deprecation process for TripleO -------------------------------------- You might have seen the ML discussion for TripleO deprecation. TripelO team is looking for the volunteer to maintain the stable/zed. If you are interested to help, please reply to James' email[14] Cleanup of PyPI maintainer list for OpenStack Projects ---------------------------------------------------------------- JayF has written the process to clean up the PyPi additional maintainers[15]. And Dmitriy is updating the governance document to explicitly mention about PyPi maintainers policy[16]. Other than that, please continue the audit process[17]. The process to find the less active projects early in the cycle: ------------------------------------------------------------------------ No update this week. JayF started the etherpad to collect the data and define the criteria to help in this process[18]. Project updates ------------------- * Add Cinder Huawei charm[19] * Add the woodpecker charm to Openstack charms[20] * mistral adopting PTL model[21] * Add xstatic-angular-fileupload as Horizon team deliverables[22] 4. How to contact the TC: ==================== If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways: 1. Email: you can send the email with tag [tc] on openstack-discuss ML[23]. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 15:00 UTC [24] 3. Ping us using 'tc-members' nickname on #openstack-tc IRC channel. [1] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggesti… [2] https://review.opendev.org/c/openstack/governance/+/874719 [3] https://review.opendev.org/c/openstack/governance/+/873440 [4] https://review.opendev.org/c/openstack/governance/+/872233 [5] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03244… [6] https://etherpad.opendev.org/p/tc-2023.1-tracker [7] https://review.opendev.org/q/projects:openstack/governance+status:open [8] https://review.opendev.org/c/openstack/governance/+/872769 [9] https://review.opendev.org/c/openstack/governance/+/874484 [10] https://review.opendev.org/c/openstack/governance/+/874969 [11] https://review.opendev.org/c/openstack/governance/+/874971 [12] https://etherpad.opendev.org/p/2023.2-leaderless [13] https://governance.openstack.org/tc/reference/tc-chair-elections.html [14] https://lists.openstack.org/pipermail/openstack-discuss/2023-February/03239… [15] https://docs.opendev.org/opendev/infra-manual/latest/creators.html#give-ope… [16] https://review.opendev.org/c/openstack/governance/+/874787 [17] https://etherpad.opendev.org/p/openstack-pypi-maintainers-cleanup [18] https://etherpad.opendev.org/p/project-health-check [19] https://review.opendev.org/c/openstack/governance/+/867588 [20] https://review.opendev.org/c/openstack/governance/+/869752 [21] https://review.opendev.org/c/openstack/governance/+/873260 [22] https://review.opendev.org/c/openstack/governance/+/873845 [23] hhttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss [24] http://eavesdrop.openstack.org/#Technical_Committee_Meeting -gmann

1 0

[all][elections][tc][ptl] 2023.2 Bobcat: Technical Committee & PTL Election Conclusion & Results
by Ian Y. Choi 24 Feb '23

24 Feb '23

Thank you to the electorate, to all those who supported and to all candidates who put their name forward for Technical Committee (TC) & Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability. Thank you to all those who make this process possible. 1. Please join me in congratulating the 5 newly elected members of the TC: Amy Marrich (spotz) James Page (jamespage) Kristi Nikolla (knikolla) Brian Rosmaita (rosmaita) Sławek Kapłoński (slaweq) Full results: no election required. 2. For the results of the PTL election process, please join me in extending congratulations to the following PTLs: * Adjutant : Dale Smith (dalees) * Barbican : Grzegorz Grasza (xek) * Blazar : Pierre Riteau (priteau) * Cinder : Rajat Dhasmana () * Cloudkitty : Rafael Weingartner () * Cyborg : alex song () * Designate : Michael Johnson (johnsom) * Ec2 Api : Andrey Pavlov (andrey-mp) * Freezer : ge cong () * Glance : Pranali Deore (pdeore) * Heat : Takashi Kajinami (tkajinam) * Horizon : Vishal Manchanda (vishalmanchanda) * Ironic : Jay Faulkner (JayF) * Keystone : Dave Wilde (d34dh0r53) * Kolla : Michal Nasiadka (mnasiadka) * Kuryr : Roman Dobosz (gryf) * Magnum : Jake Yip (jakeyip) * Manila : Carlos Silva (carloss) * Masakari : sam sue () * Murano : Rong Zhu (zhurong) * Neutron : Rodolfo Alonso Hernandez (ralonsoh) * Nova : Sylvain Bauza (bauzas) * Octavia : Gregory Thiemonge (gthiemonge) * Openstack Chef : Lance Albertson (Ramereth) * OpenStack Helm : Vladimir Kozhukalov () * OpenStackAnsible : Dmitriy Rabotyagov (noonedeadpunk) * OpenStackSDK : Artem Goncharov (gtema) * Puppet OpenStack : Takashi Kajinami (tkajinam) * Quality Assurance : Martin Kopec (kopecmartin) * Skyline : Wenxiang Wu (wu_wenxiang) * Solum : Rong Zhu (zhurong) * Storlets : Takashi Kajinami (tkajinam) * Tacker : Yasufumi Ogawa (yasufum) * Telemetry : Matthias Runge (mrunge) * Trove : wu chunyang (wuchunyang) * Venus : Eric Zhang () * Watcher : chen ke () * Zaqar : Hao Wang (wanghao) * Zun : Hongbin Lu () PTL Election: no election required. For remaining projects (without PTL candidates), TC will work on the appointment. Election process details and results are also available here: https://governance.openstack.org/election/ Thank you to all of the candidates, having a good group of candidates helps engage the community in our democratic process. Thank you to all who voted and who encouraged others to vote. We need to ensure your voice is heard. Thank you for another great round. Ian Y. Choi, on behalf of the OpenStack Technical Election Officials

2 1

[requirement] RFE for multiple python-*clients
by Elõd Illés 24 Feb '23

24 Feb '23

Hi, this is kind of a late, formal bulk request of Requirements Freeze Exception for the following deliverables. Neither of them introduces big changes, rather some tox related gate fix and other minimal changes: * python-muranoclient * python-solumclient * python-heatclient * python-swiftclient * python-keystoneclient * python-saharaclient * python-freezerclient * python-monascaclient The exception is the following deliverable as this has many changes, features, bugfixes in its release: * python-openstackclient Thanks, Előd Illés irc: elodilles @ #openstack-release

1 0

[manila] Manila Bugsquash (Feb 27th to Mar 3rd)
by Carlos Silva 24 Feb '23

24 Feb '23

Hello Zorillas! We have been planning our bugsquash for a couple of weeks now, and time has come! We have seen a trend on the number of bugs increasing this cycle, and we have identified that we have many bugs that already have a fix proposed but we didn't get those changes merged. Merging such issues would help us to fix those bugs and continue reducing our bug backlog. So for this bugsquash we will be focusing on getting closure for such changes! Vida (vhari) kindly groomed the bugs list [1]. We will be meeting on Monday to have a kick-off call at 16 UTC [2], so we can assign reviewers to the changes or discuss the progress of the changes if that is the case. [1] https://ethercalc.net/8ru5hurhelyl [2] https://bluejeans.com/371190441 Looking forward to see you there! Thank you, carloss

1 0

[all][elections][ptl][tc] Combined PTL/TC 2023.2 cycle Election Nominations End
by Tony Breeds 24 Feb '23

24 Feb '23

The PTL and TC Nomination period is now over. The official candidate lists for PTLs [0] and TC seats [1] are available on the election website. -- PTL Election Details -- There are 9 projects without candidates, so according to this resolution[2], the TC will have to decide how the following projects will proceed: Monasca, OpenStack_Charms, Rally, Sahara, Senlin, Swift, Tripleo, Vitrage, Winstackers There are 0 projects that will have elections. -- TC Election Details -- There are 5 candidates for 5 seats. Given that there are no polls that need to be held, this concludes the election process. Congratulations to our new and returning leaders. Thank you, Tony, on behalf of the election officials. [0] https://governance.openstack.org/election/#bobcar-ptl-candidates [1] https://governance.openstack.org/election/#bobcat-tc-candidates [2] https://governance.openstack.org/resolutions/20141128-elections-process-for…

3 5

[release] Release countdown for week R-3, Feb 27 Mar 03
by Herve Beraud 24 Feb '23

24 Feb '23

Development Focus ----------------- The Release Candidate (RC) deadline is next Thursday, March 02. Work should be focused on fixing any release-critical bugs. General Information ------------------- All deliverables released under a cycle-with-rc model should have a first release candidate by the end of the week, from which a stable/2023.1 branch will be cut. This branch will track the 2023.1 Antelope release. Once stable/2023.1 has been created, the master branch will be ready to switch to 2023.2 Bobcat development. While the master branch will no longer be feature-frozen, please prioritize any work necessary for completing 2023.1 Antelope plans. Release-critical bugfixes will need to be merged in the master branch first, then backported to the stable/2023.1 branch before a new release candidate can be proposed. Actions ------- Early in the week, the release team will be proposing RC1 patches for all cycle-with-rc projects, using the latest commit from the master branch. If your team is ready to go for cutting RC1, please let us know by leaving a +1 on these patches. If there are still a few more patches needed before RC1, you can -1 the patch and update it later in the week with the new commit hash you would like to use. Remember, stable/2023.1 branches will be created with this, so you will want to make sure you have what you need included to avoid needing to backport changes from the master branch (which will technically then be 2023.2 Bobcat) to this stable branch for any additional RCs before the final release. The release team will also be proposing releases for any deliverable following a cycle-with-intermediary model that has not produced any 2023.1 Antelope release so far. Finally, now is a good time to finalize release highlights. Release highlights help shape the messaging around the release and make sure that your work is properly represented. Upcoming Deadlines & Dates -------------------------- RC1 deadline: March 02 (R-3 week) Final RC deadline: March 17 (R-1 week) Final 2023.1 Antelope release: March 22 -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/

1 0

[kolla-ansible] [yoga] [magnum] [k8s] cannot attach persistent volume to pod
by Stuart Whitman 24 Feb '23

24 Feb '23

Hello, When I try to attach a persistent cinder volume to a pod, I get FailedMount and FailedAttachVolume timeout events. I also get these errors in the log of the csi-cinder-controllerplugin-0 pod: E1020 13:38:41.747511 1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.VolumeAttachment: the server could not find the requested resource E1020 13:38:41.748187 1 reflector.go:126] k8s.io/client-go/informers/factory.go:133: Failed to list *v1beta1.CSINode: the server could not find the requested resource I fixed a CrashLoopBackoff error with the csi-snapshotter container in the csi-cinder-controllerplugin-0 pod by providing the label "csi_snapshotter_tag=v4.0.0" when I created the cluster template. I found that suggestion in an issue on the GitHub cloud-provider-openstack project. I'm not finding any help with this error on Google. Thanks, -Stu _____________________________________ The information contained in this e-mail and any attachments from Group W may contain confidential and/or proprietary information and is intended only for the named recipient to whom it was originally addressed. If you are not the intended recipient, be aware that any disclosure, distribution, or copying of this e-mail or its attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately of that fact by return e-mail and permanently delete the e-mail and any attachments to it.

3 5