November 2022 - openstack-discuss

[neutron] Neutron drivers meeting cancelled
by Rodolfo Alonso Hernandez 18 Nov '22

18 Nov '22

Hello Neutrinos: Due to the lack of agenda, today's drivers meeting is cancelled. Have a nice weekend!

1 0

[kolla-ansible][Yoga] Install with self-signed certificate
by wodel youchi 18 Nov '22

18 Nov '22

Hi, To deploy Openstack with a self-signed certificate, the documentation says to generate the certificates using kolla-ansible certificates, to configure the support of TLS in globals.yml and to deploy. I am facing a problem, my old certificate has expired, I want to use a self-signed certificate. I backported my servers to an older date, then generated a self-signed certificate using kolla, but the deploy/reconfigure won't work, they say : self._sslobj.do_handshake()\n File \"/usr/lib64/python3.6/ssl.py\", line 648, in do_handshakeself._sslobj.do_handshake()\nssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED certificate verify failed PS : in my globals.yml i have : *kolla_verify_tls_backend: "yes"* Regards.

2 11

[tc][policy] RBAC (policy-popup team) meeting time
by Ghanshyam Mann 18 Nov '22

18 Nov '22

Hello Everyone, I am starting the RBAC (policy-pop up) bi-weekly meeting on alternate Tuesday (starting Nov 22) at 17:00 UTC on #openstack-meeting IRC channel. Details: https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popu… ICS File: https://meetings.opendev.org/#Secure_Default_Policies_Popup-Team_Meeting -gmann

1 0

[all][tc] 2023.1 cycle updated testing runtime (recommended Upgrade Path testing)
by Ghanshyam Mann 17 Nov '22

17 Nov '22

Hello Everyone, You might have seen the TC discussion[1] in PTG for the best possible testing for smooth upgrade. When there is a distro version change in testing runtime, then we need to test both the old and the new distro versions (for the cycle when we are bumping the distro version). We have documented the recommended upgrade path testing in PTI also[2], refer to that for details. In 2023.1 cycle, we are moving from Ubuntu Focal (20.04) to Jammy (22.04)[3] and as per the upgrade path testing we should test the Focal (20.04) also. TC has merged these updates in the 2023.1 cycle testing runtime document[4] which are basically: 1. Testing Ubuntu Focal (20.04) in a single job (one job is enough to test the old version) in project gate. For example, neutron did[5]. This can be a new job or one of the existing jobs. 2. Python minimum version to test is python 3.8 (default version in Ubuntu Focal). We will be testing python 3.8 and python 3.10 unit/functional jobs. Unit test job template change has been merged[6] which will automatically start running py38 unit test job and functional jobs can be modified (if needed) by project side. [1] https://etherpad.opendev.org/p/tc-2023-1-ptg#L422 [2] https://governance.openstack.org/tc/reference/project-testing-interface.htm… [3] https://governance.openstack.org/tc/goals/selected/migrate-ci-jobs-to-ubunt… [4] https://review.opendev.org/c/openstack/governance/+/860599 [5] https://review.opendev.org/c/openstack/neutron/+/862492 [6] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/864464 -gmann

1 0

[openstack-ansible] Designate: rndc config file not generated
by Taltavull Jean-François 17 Nov '22

17 Nov '22

Hello, I'm deploying Designate on OpenStack Wallaby/Ubuntu 20.04 with DNS servers located outside the OpenStack platform. After running 'os-designate-install.yml' playbook, 'bind9-utils' package is correctly installed but I can't find rndc config file anywhere inside the lxc container. This prevents rndc from running well and communicating with the DNS servers. Any idea ? Regards, Jean-Francois

3 4

[Kolla][kolla-ansible][HAProxy] Splitting the load balancer into internal and external?
by Mariusz Karpiarz 17 Nov '22

17 Nov '22

All, Was the idea of moving internal components deployed by kolla-ansible (like the MySQL database) to a load balancer separate to the one used by user-facing APIs discussed anywhere? This feels like a good option to have for security but, as far as I'm aware, it's not supported by kolla-ansible. It should be possible to use existing Kolla HAProxy images, but mount config files from subdirectories of `/etc/kolla/haproxy/` for each container. I suspect the main hurtle here would be rewriting the user interface of kolla-ansible to account for the split whilst maintaining backward compatibility... Mariusz Karpiarz

3 4

Re:
by K Santhosh 17 Nov '22

17 Nov '22

can any one help me out with this freezer_scheduler container On Wed, Nov 16, 2022 at 6:00 PM K Santhosh <sandcruz666(a)gmail.com> wrote: > /var/log/kolla/freezer_scheduler.log > and > logs from container > > <https://mail.google.com/mail/u/0?ui=2&ik=849caec82f&attid=0.1&permmsgid=msg…> > > On Tue, Nov 15, 2022 at 4:18 PM Michal Arbet <michal.arbet(a)ultimum.io> > wrote: > >> What about logs from container ? >> What about log in /var/log/kolla..... >> >> >> Michal Arbet >> Openstack Engineer >> >> Ultimum Technologies a.s. >> Na Poříčí 1047/26, 11000 Praha 1 >> Czech Republic >> >> +420 604 228 897 >> michal.arbet(a)ultimum.io >> *https://ultimum.io <https://ultimum.io/>* >> >> LinkedIn <https://www.linkedin.com/company/ultimum-technologies> | >> Twitter <https://twitter.com/ultimumtech> | Facebook >> <https://www.facebook.com/ultimumtechnologies/timeline> >> >> >> út 15. 11. 2022 v 6:18 odesílatel K Santhosh <sandcruz666(a)gmail.com> >> napsal: >> >>> Hai , >>> I am Santhosh, >>> I do facing a problem with freezer deploymentnt >>> After the deployment of freezer . The freezer_scheduler >>> container is continuously restarting in kolla openstack >>> can you help me out with this freezer_scheduler container >>> >>

1 0

[kolla-ansible]Reset Configuration
by Franck VEDEL 17 Nov '22

17 Nov '22

Hello, yesterday I sent a desperate message about the functioning of my Openstack (kolla-ansible, yoga, centos8Stream). The situation is incomprehensible. For some accounts in some projects, everything works (creation of networks, subnets, dhcp configuration, instances, everything works). For other accounts, everything works except having an IP address per dhcp on a subnet. The servers have restarted following a power outage. I managed to put everything back together except those DHCP issues. As I can start from an empty configuration, how to reset everything ... for example with a command: kolla-ansible -i multinode ____________ Or how to fix my configuration. It seems very complicated to me. I would like some opinions if possible. Thanks in advance Franck

3 10

[CloudKitty][os-api-ref][openstack-dev] v1 API docs
by Mariusz Karpiarz 16 Nov '22

16 Nov '22

All, CloudKitty docs for v1 APIs (https://docs.openstack.org/cloudkitty/latest/api-reference/v1/v1.html) appear to be generated from the source code instead of using `os-api-ref` (https://opendev.org/openstack/os-api-ref) like in case of v2 docs. I want to move both v1 and v2 API docs to a separate `api-ref/source` directory in the root of the repository, where we will only be using "os_api_ref" and "openstackdocstheme" Sphinx extensions, so we need to decide what to do with v1 docs. I started rewriting v1 docs to the format supported by `os-api-ref` but they don't quite translate well to the new format, mainly because of different ways results are presented (Python objects vs JSONs). How much do we care about proper v1 API docs and would it be worth for someone (likely me) to write them again from scratch? There is also the option for carrying over the old extensions (they are all listed here: https://opendev.org/openstack/cloudkitty/src/branch/stable/zed/doc/source/c…) but I'm not sure all of them are still supported by the system building https://docs.openstack.org/api/ and this is a good opportunity to clean this list up. :) Please let me know if you have any ideas. Mariusz

2 1

[puppet] Configure openid with Keycloak IdP in Keystone
by Fernandez Rodriguez Daniel 16 Nov '22

16 Nov '22

Hello, this is a bit of a long shot but maybe some of you succesfully configured Openstack to use Keycloak as an Identity Provider so we can use Single Sign-On on Horizon. To install and configure OpenStack Keystone I am using 'stable/xena' version of the https://github.com/openstack/puppet-keystone . Likewise for Horizon. So far so good. I would like to enable openid in Keystone so I can have Single Sign-On via Horizon. I am pretty much following the official docs: https://docs.openstack.org/keystone/latest/admin/federation/configure_feder… with the help of the puppet module. To do it I included the class: include ::keystone::federation::openidc And configured some hiera variables: keystone::federation::openidc::keystone_url: "https://openstackdev.loadbalancer:5000" keystone::federation::openidc::methods: 'password,token,oauth1,mapped,openid' keystone::federation::openidc::idp_name: 'keycloak' keystone::federation::openidc::openidc_provider_metadata_url: 'https://keycloak_server/auth/realms/BBP/.well-known/openid-configuration' keystone::federation::openidc::openidc_client_id: 'a_keycloak_client' keystone::federation::openidc::openidc_client_secret: <redacted> keystone::federation::openidc::openidc_crypto_passphrase: <redacted> keystone::federation::openidc::remote_id_attribute: 'HTTP_OIDC_ISS' And this is the resulting relevant configuration in /etc/httpd/conf.d/10-keystone_wsgi.conf [...] OIDCClaimPrefix "OIDC-" OIDCResponseType "id_token" OIDCScope "openid email profile" OIDCProviderMetadataURL "https://keycloak_server/auth/realms/BBP/.well-known/openid-configuration" OIDCClientID "a_keycloak_client" OIDCClientSecret <redacted> OIDCCryptoPassphrase <redacted> # The following directives are necessary to support websso from Horizon # (Per https://docs.openstack.org/keystone/pike/advanced-topics/federation/websso.…) OIDCRedirectURI "https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/identity_provi…" OIDCRedirectURI "https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/websso/openid" <LocationMatch "/v3/auth/OS-FEDERATION/websso/openid"> AuthType "openid-connect" Require valid-user </LocationMatch> <LocationMatch "/v3/auth/OS-FEDERATION/identity_providers/keycloak/protocols/openid/websso"> AuthType "openid-connect" Require valid-user </LocationMatch> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ But unfortunately this does not work. First of all, the OIDCRedirectURI the module set points to a valid URL with content. So I manually changed them by: OIDCRedirectURI "https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/identity_provi…" OIDCRedirectURI "https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/websso/openid/…" After changing that now I get redirected to the Keycloak login page and I am able to enter my username and pass, after the login is done I get redirected to: https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/websso/openid?…<https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/websso/openid?…>openstackdev.loadbalancer<https://openstackdev.loadbalancer:5000/v3/auth/OS-FEDERATION/websso/openid?…>/dashboard/auth/websso/ and it shows the following error: error code 404 message "Could not find Identity Provider: https://keycloak_server/auth/realms/BBP<https://bbpauth.epfl.ch/auth/realms/BBP>." title "Not Found" And in: /var/log/keystone/keystone.log {"message": "Could not find Identity Provider: https://keycloak_server/auth/realms/BBP.", "asctime": "2022-11-16 16:24:56", "name": "keystone.server.flask.application", "msg": "Could not find Identity Provider: https://keycloak_server/auth/realms/BBP.", "args": [], "levelname": "WARNING", "levelno": 30, "pathname": "/usr/lib/python3.6/site-packages/keystone/server/flask/application.py", "filename": "application.py", "module": "application", "lineno": 87, "funcname": "_handle_keystone_exception", "created": 1668612296.6284614, "msecs": 628.4613609313965, "relative_created": 32117.148637771606, "thread": 140579135473408, "thread_name": "Dummy-1", "process_name": "MainProcess", "process": 3051629, "traceback": null, "hostname": "bbpcb030.bbp.epfl.ch", "error_summary": "keystone.exception.IdentityProviderNotFound: Could not find Identity Provider: https://keycloak_server/auth/realms/BBP.", "context": {"user_name": null, "project_name": null, "domain_name": null, "user_domain_name": null, "project_domain_name": null, "user": null, "tenant": null, "system_scope": null, "project": null, "domain": null, "user_domain": null, "project_domain": null, "is_admin": false, "read_only": false, "show_deleted": false, "auth_token": null, "request_id": "req-5187f72d-cb4b-470f-9635-6c05565707eb", "global_request_id": null, "resource_uuid": null, "roles": [], "user_identity": "- - - - -", "is_admin_project": true}, "extra": {"project": null, "version": "unknown"}} And this is how I configured the identity provider, mapping and federation protocol. # openstack identity provider show keycloak +-------------------+-----------------------------------------+ | Field | Value | +-------------------+-----------------------------------------+ | authorization_ttl | None | | description | None | | domain_id | 96a75a2b29b5411497a9971c14a2167c | | enabled | True | | id | keycloak | | remote_ids | https://keycloak_server/auth/realms/BBP | +-------------------+-----------------------------------------+ # openstack mapping show openid_mapping +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+ | id | openid_mapping | | rules | [{'local': [{'user': {'name': '{0}'}, 'group': {'domain': {'name': 'Default'}, 'name': 'federated_users'}}], 'remote': [{'type': 'OIDC-preferred_username'}]}] | +-------+----------------------------------------------------------------------------------------------------------------------------------------------------------------+ # openstack federation protocol show --identity-provider keycloak openid +---------+----------------+ | Field | Value | +---------+----------------+ | id | openid | | mapping | openid_mapping | +---------+----------------+ Can someone please give me a hand with this? Thank you very much, Daniel.

1 0

[kolla-ansible][Yoga] Deployment stuck
by wodel youchi 16 Nov '22

16 Nov '22

Hi, I am trying to deploy a new platform using kolla-ansible Yoga and I am trying to upgrade another platform from Xena to yoga. On both platforms the prechecks went well, but when I start the process of deployment for the first and upgrade for the second, the process gets stuck. I tried to tail -f /var/log/kolla/*/*.log but I can't get hold of the cause. In the first platform, some services get deployed, and at some point the script gets stuck, several times in the modprobe phase. In the second platform, the upgrade gets stuck on : Escalation succeeded [204/1859] <20.3.0.28> (0, b'\n{"path": "/etc/kolla/cron", "changed": false, "diff": {"before": {"path": "/etc/kolla/cro n"}, "after": {"path": "/etc/kolla/cron"}}, "uid": 0, "gid": 0, "owner": "root", "group": "root", "mode": "07 70", "state": "directory", "secontext": "unconfined_u:object_r:etc_t:s0", "size": 70, "invocation": {"module_ args": {"path": "/etc/kolla/cron", "owner": "root", "group": "root", "mode": "0770", "recurse": false, "force ": false, "follow": true, "modification_time_format": "%Y%m%d%H%M.%S", "access_time_format": "%Y%m%d%H%M.%S", "unsafe_writes": false, "state": "directory", "_original_basename": null, "_diff_peek": null, "src": null, " modification_time": null, "access_time": null, "seuser": null, "serole": null, "selevel": null, "setype": nul l, "attributes": null}}}\n', b'') ok: [20.3.0.28] => (item={'key': 'cron', 'value': {'container_name': 'cron', 'group': 'cron', 'enabled': True , 'image': '20.3.0.34:4000/openstack.kolla/centos-source-cron:yoga', 'environment': {'DUMMY_ENVIRONMENT': 'ko lla_useless_env', 'KOLLA_LOGROTATE_SCHEDULE': 'daily'}, 'volumes': ['/etc/kolla/cron/:/var/lib/kolla/config_f iles/:ro', '/etc/localtime:/etc/localtime:ro', '', 'kolla_logs:/var/log/kolla/'], 'dimensions': {}}}) => { "ansible_loop_var": "item", "changed": false, "diff": { "after": { "path": "/etc/kolla/cron" }, "before": { "path": "/etc/kolla/cron" } }, "gid": 0, "group": "root", How to start debugging the situation. Regards.

1 5

[neutron-dynamic-routing] BGPspeaker LOOP
by Roberto Bartzen Acosta 16 Nov '22

16 Nov '22

Hey folks, Please, I have a question here, the bgpspeaker should only "learn" and not "advertise" the AS_PATHs via BGP, right? In my tests, I can see that it is learning routes from BGP neighbors. This behavior can cause an AS_PATH loop because the bgpspeaker learns back its own advertised routes, and I see a message like this in the logs: 2022-11-11 19:45:41.967 7220 ERROR bgpspeaker.peer [-] AS_PATH on UPDATE message has loops. Ignoring this message: BGPUpdate(len=91,nlri=[],path_attributes=[BGPPathAttributeMpReachNLRI(afi=2,flags=144,length=46,next_hop='2001:db7:1::1',nlri=[IP6AddrPrefix(addr='2001:db9:1234::',length=64)],safi=1,type=14), BGPPathAttributeOrigin(flags=64,length=1,type=1,value=0), BGPPathAttributeAsPath(flags=80,length=10,type=2,value=[[65001, 65000]])],total_path_attribute_len=68,type=2,withdrawn_routes=[],withdrawn_routes_len=0) This can be fixed by suppressing the neighbor route advertisement (using route-map export), but have I misunderstood how neutron-dymanic-routing works or do we have a possible bug here? Regards -- _‘Esta mensagem é direcionada apenas para os endereços constantes no cabeçalho inicial. Se você não está listado nos endereços constantes no cabeçalho, pedimos-lhe que desconsidere completamente o conteúdo dessa mensagem e cuja cópia, encaminhamento e/ou execução das ações citadas estão imediatamente anuladas e proibidas’._ * **‘Apesar do Magazine Luiza tomar todas as precauções razoáveis para assegurar que nenhum vírus esteja presente nesse e-mail, a empresa não poderá aceitar a responsabilidade por quaisquer perdas ou danos causados por esse e-mail ou por seus anexos’.*

2 2

[cinder] Bug report from 11-08-2022 to 11-16-2022
by Sofia Enriquez 16 Nov '22

16 Nov '22

This is a bug report from 11-08-2022 to 11-16-2022. Agenda: https://etherpad.opendev.org/p/cinder-bug-squad-meeting ----------------------------------------------------------------------------------------- High - https://bugs.launchpad.net/cinderlib/+bug/1996738 "Cinderlib Gate broken in Zed." Unassigned. Invalid - https://bugs.launchpad.net/cinder/+bug/1990257 "[OpenStack Yoga] Creating a VM fails when stopping only one rabbitmq." Moved to Nova. Cheers, Sofia -- 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

Issue installing OpenStack in CentOS VMs - cannot launch instances
by André Ferreira 16 Nov '22

16 Nov '22

Hello, I'm trying to setup an openstack cluster by following the instructions on https://docs.openstack.org/install-guide/openstack-services.html#minimal-de… I'm using two CentOS8 VMs: - VM1: controller node - VM2: compute node After installing all the minimum services, I've tried to create a server instance but it's failing. >From the logs, looks like that nova is not able to find a compute node to launch the instance: 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager [req-c1aa668e-73db-4799-baa4-d782ec5986e9 e6529a38880d4efcb55308277aeabb88 6a857bb3fb7f47849ff5a11d97968344 - default default] Failed to schedule i host was found. Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 241, in inner return func(*args, **kwargs) File "/usr/lib/python3.6/site-packages/nova/scheduler/manager.py", line 209, in select_destinations raise exception.NoValidHost(reason="") nova.exception.NoValidHost: No valid host was found. 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager Traceback (most recent call last): 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 1549, in schedule_and_build_instances 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager instance_uuids, return_alternates=True) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/nova/conductor/manager.py", line 910, in _schedule_instances 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager return_alternates=return_alternates) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/nova/scheduler/client/query.py", line 42, in select_destinations 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager instance_uuids, return_objects, return_alternates) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/nova/scheduler/rpcapi.py", line 160, in select_destinations 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager return cctxt.call(ctxt, 'select_destinations', **msg_args) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/client.py", line 192, in call 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager retry=self.retry, transport_options=self.transport_options) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/oslo_messaging/transport.py", line 128, in _send 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager transport_options=transport_options) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 691, in send 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager transport_options=transport_options) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 681, in _send 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager raise result 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager nova.exception_Remote.NoValidHost_Remote: No valid host was found. 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager Traceback (most recent call last): 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/oslo_messaging/rpc/server.py", line 241, in inner 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager return func(*args, **kwargs) 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager File "/usr/lib/python3.6/site-packages/nova/scheduler/manager.py", line 209, in select_destinations 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager raise exception.NoValidHost(reason="") 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager 2022-11-15 16:54:11.889 3963 ERROR nova.conductor.manager nova.exception.NoValidHost: No valid host was found >From nova-scheduler: 2022-11-15 16:54:11.797 3978 INFO nova.scheduler.manager [req-c1aa668e-73db-4799-baa4-d782ec5986e9 e6529a38880d4efcb55308277aeabb88 6a857bb3fb7f47849ff5a11d97968344 - default default] Got no allocation can cient resources or a temporary occurrence as compute nodes start up. 2022-11-15 16:54:23.160 3978 DEBUG oslo_service.periodic_task [req-d477e747-537b-48b2-8913-ef84447d5a21 - - - - -] Running periodic task SchedulerManager._discover_hosts_in_cells run_periodic_tasks /usr/li 2022-11-15 16:54:23.169 3978 DEBUG oslo_concurrency.lockutils [req-4dbefd76-0b81-47d9-b6cf-382f43e3505e - - - - -] Lock "79648906-0ea8-4672-8c5f-73d5998a7b73" acquired by "nova.context.set_target_cell.<loc .000s inner /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:390 2022-11-15 16:54:23.170 3978 DEBUG oslo_concurrency.lockutils [req-4dbefd76-0b81-47d9-b6cf-382f43e3505e - - - - -] Lock "79648906-0ea8-4672-8c5f-73d5998a7b73" "released" by "nova.context.set_target_cell.<l .001s inner /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:405 2022-11-15 16:54:59.097 3977 DEBUG oslo_service.periodic_task [req-bb4ca11b-2089-414c-b8d5-6c45aa58c1bf - - - - -] Running periodic task SchedulerManager._discover_hosts_in_cells run_periodic_tasks /usr/li 2022-11-15 16:54:59.112 3977 DEBUG oslo_concurrency.lockutils [req-cf62a2b4-6721-4f98-a97d-7b51e58a34b3 - - - - -] Lock "79648906-0ea8-4672-8c5f-73d5998a7b73" acquired by "nova.context.set_target_cell.<loc .000s inner /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:390 2022-11-15 16:54:59.113 3977 DEBUG oslo_concurrency.lockutils [req-cf62a2b4-6721-4f98-a97d-7b51e58a34b3 - - - - -] Lock "79648906-0ea8-4672-8c5f-73d5998a7b73" "released" by "nova.context.set_target_cell.<l .001s inner /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:405 The problem is that the compute node is not placed on the cell. The list of hypervisors is also empty. I've searched online but I don't find a way to fix this. (admin-rc) [andrefe@controller0 ~]$ openstack compute service list +--------------------------------------+----------------+------------------------+----------+---------+-------+----------------------------+ | ID | Binary | Host | Zone | Status | State | Updated At | +--------------------------------------+----------------+------------------------+----------+---------+-------+----------------------------+ | fa781cbb-732c-43db-8c9f-4c31bd73bbd2 | nova-scheduler | controller0.os.lab.com | internal | enabled | up | 2022-11-15T15:59:40.000000 | | 106e9574-5ae3-45e2-a7c2-09ce3624a1d6 | nova-conductor | controller0.os.lab.com | internal | enabled | up | 2022-11-15T15:59:40.000000 | | 28072820-609a-4066-abc8-affea51c3600 | nova-compute | compute0.os.lab.com | nova | enabled | up | 2022-11-15T15:59:41.000000 | +--------------------------------------+----------------+------------------------+----------+---------+-------+----------------------------+ [root@controller0 ~]# /bin/sh -c "nova-manage cell_v2 list_cells" nova +-------+--------------------------------------+-------------------------------------------+--------------------------------------------------+----------+ | Name | UUID | Transport URL | Database Connection | Disabled | +-------+--------------------------------------+-------------------------------------------+--------------------------------------------------+----------+ | cell0 | 00000000-0000-0000-0000-000000000000 | none:/ | mysql+pymysql://nova:****@controller0/nova_cell0 | False | | cell1 | 79648906-0ea8-4672-8c5f-73d5998a7b73 | rabbit://openstack:****@controller0:5672/ | mysql+pymysql://nova:****@controller0/nova | False | +-------+--------------------------------------+-------------------------------------------+--------------------------------------------------+----------+ [root@controller0 ~]# /bin/sh -c "nova-manage cell_v2 list_hosts" +-----------+--------------------------------------+---------------------+ | Cell Name | Cell UUID | Hostname | +-----------+--------------------------------------+---------------------+ | cell1 | 79648906-0ea8-4672-8c5f-73d5998a7b73 | compute0.os.lab.com | +-----------+--------------------------------------+---------------------+ [root@controller0 ~]# /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova Found 2 cell mappings. Skipping cell0 since it does not contain hosts. Getting computes from cell 'cell1': 79648906-0ea8-4672-8c5f-73d5998a7b73 Found 0 unmapped computes in cell: 79648906-0ea8-4672-8c5f-73d5998a7b73 (admin-rc) [andrefe@controller0 ~]$ nova hypervisor-list +----+---------------------+-------+--------+ | ID | Hypervisor hostname | State | Status | +----+---------------------+-------+--------+ +----+---------------------+-------+--------+ Any idea on how I can fix this and add the compute to the cell? Thanks.

2 1

[all][tc] Technical Committee next weekly meeting on 2022 Nov 16 at 1600 UTC
by Ghanshyam Mann 16 Nov '22

16 Nov '22

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

1 1

[mistral][keystone] Updating credentials and trusts
by Arnaud Morin 15 Nov '22

15 Nov '22

Hey team, Mistral is using keystone "trusts" in order to perform action on behalf of another customer. If I understand correctly the trust mechanism in keystone, it's related to a specific user_id. Imagine I want to update the user (and password) of the mistral service (mistral-api), then the user ID may change, so the trust will be broken. Is there any way to update the user of mistral-api without breaking the trusts? One answer is to not change the user, but only the password. But doing so will break my service for a moment (while I update the passwords in both services - keystone and mistral). Is there any other option? Regards, Arnaud - OVHcloud.

1 0

[tripleo] gate blocker /tripleo/+bug/1996482 - please hold rechecks
by Marios Andreou 15 Nov '22

15 Nov '22

Hi folks, per $subject we have a gate blocker at https://bugs.launchpad.net/tripleo/+bug/1996482 Please avoid recheck if you are hitting this issue - it fails during undercloud/standalone install and looks like: ERROR! Unexpected Exception, this is probably a bug: 'Task' object has no attribute '_valid_attrs' Fix is coming with https://review.opendev.org/c/openstack/tripleo-ansible/+/864392 thanks to Takashi for chasing that today regards, marios

1 1

EMC SAN with Openstack ansible
by Derek O keeffe 15 Nov '22

15 Nov '22

Hi all, I've been chatting on the IRC channel and I've gotten some feedback that I need to read up on regarding overrides, but just in case I'm about to reinvent the wheel (try at least) has anyone set up cinder volumes on an EMC SAN using OSA? and if so could yo give me some advice, examples, pointers, etc... We had it set up manually on an old cluster but are unsure how to do it through OSA (starting to look at it today based on the advice we got) This explains how to do it manually https://www.delltechnologies.com/asset/en-us/products/storage/industry-mark… Any info would be great and hugely appreciated. Should we figure it out before then we will drop the config here for others that may be interested. Regards,Derek

2 1

(no subject)
by K Santhosh 15 Nov '22

15 Nov '22

Hai , I am Santhosh, I do facing a problem with freezer deploymentnt After the deployment of freezer . The freezer_scheduler container is continuously restarting in kolla openstack can you help me out with this freezer_scheduler container

2 1

how to remove image with still used volumes
by Christoph Anton Mitterer 15 Nov '22

15 Nov '22

Hey. I have instances with a volume that were once created from some image. Now the volume's OS was upgraded over time to the respective current releases, while the image is long obsolete and just uses up space. Is there a way to remove those images? It seems normal commands don't allow me, as long as there are volumes which were created from them. Thanks, Chris.

5 12

Unable to snapshot instances on backend storage
by Derek O keeffe 15 Nov '22

15 Nov '22

Hi all, When we create an instance and leave the "Create new volume" option as no then we can manage the instance with no issues (migrate, snapshot, etc..) These instances are saved locally on the compute nodes. When we create an instance and select "Create new volume" yes the instance is spun up fine on our backend storage with no obvious issues (reachable with ping & ssh. shutdown, restart, networking, etc.. all fine) however, when we try to snapshot it or migrate it it fails. We can however take volume snapshots of volumes that we have created and are stored on the same shared backend. Has anyone came across this or maybe a pointer as to what they may think is causing it? It sounds to us as if nova try's to create a snapshot of the VM but thinks it's a volume maybe? Any help greatly appreciated. Regards,Derek

2 2

[tc] Fwd: Invitation: OpenInfra Board sync with OpenStack TC @ Wed Nov 16, 2022 20:00 - 21:00 (UTC)
by Jeremy Stanley 14 Nov '22

14 Nov '22

Just a reminder that a few months ago we arranged a November meeting time between the OpenStack community and the OpenInfra Board of Directors, Wednesday 2022-11-16 at 20:00 UTC. Julia has graciously supplied a conference call connection for the hour. I've also added the connection info to the pad we've been using for planning this call: https://etherpad.opendev.org/p/2022-11-board-openstack-sync -- Jeremy Stanley ----- Forwarded message from juliaashleykreger(a)gmail.com ----- Date: Mon, 14 Nov 2022 18:10:42 +0000 Subject: Invitation: OpenInfra Board sync with OpenStack TC @ Wed Nov 16, 2022 2pm - 3pm (CST) (jeremy(a)openinfra.dev) OpenInfra Board sync with OpenStack TC Wednesday Nov 16, 2022 ⋅ 2pm – 3pm Central Time - Chicago Location https://us02web.zoom.us/j/84584540710?pwd=aVdpaytPcG01NW9VWVZERDNtZURaZz09 https://www.google.com/url?q=https%3A%2F%2Fus02web.zoom.us%2Fj%2F8458454071… Greetings Directors & All, During the last meeting between the Board and the OpenStack TC, we determined we would attempt to meet on the 16th of November to have another general open discussion between the two groups. Mailing list posts were made, but a calendar invite was not sent out directly to the attendees. This is that invite. Please use the attached meeting link for call. -Julia ----- End forwarded message -----

1 0

Need information
by Gk Gk 14 Nov '22

14 Nov '22

Hi All, At the core of nova-api, I am trying to trace the function which executes the SQL query for listing all the instances for a user. I want to know where in the code this query is executed. I have traced it till this point in the code: ---- if self.cells: results = context.scatter_gather_cells(ctx, self.cells, context.CELL_TIMEOUT, query_wrapper, do_query) --- in the file " https://github.com/openstack/nova/blob/c97507dfcd57cce9d76670d3b0d48538900c… " But where in the above file, is the SQL query executed ? Please help me Thanks Kumar

2 1

RDO Zed Released
by Amy Marrich 14 Nov '22

14 Nov '22

The RDO community is pleased to announce the general availability of the RDO build for OpenStack Zed for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Zed is the 26th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. As with the Upstream release, this release of RDO is dedicated to Ilya Etingof who was an upstream and RDO contributor. The release is already available for CentOS Stream 9 on the CentOS mirror network in: http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-zed/ The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud Infrastructure SIG. The Cloud Infrastructure SIG focuses on delivering a great user experience for CentOS users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/zed/highlights.html *TripleO in the RDO Zed release:* Since the Xena development cycle, TripleO follows the Independent release model ( https://specs.openstack.org/openstack/tripleo-specs/specs/xena/tripleo-inde… ). For the Zed cycle, TripleO project will maintain and validate stable Zed branches. As for the rest of packages, RDO will update and publish the releases created during the maintenance cycle. *Contributors* During the Zed cycle, we saw the following new RDO contributors: - Miguel Garcia Cruces - Michael Johnson - René Ribaud - Paras Babbar - Maurício Harley - Jesse Pretorius - Francesco Pantano - Carlos Eduardo - Arun KV Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all *57* contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and redhat-website repositories: - Adriano Vieira Petrich - Alan Bishop - Alan Pevec - Alfredo Moralejo Alonso - Amol Kahat - Amy Marrich - Ananya Banerjee - Arun KV - Arx Cruz - Bhagyashri Shewale - Carlos Eduardo - Chandan Kumar - Cédric Jeanneret - Daniel Pawlik - Dariusz Smigiel - Douglas Viroel - Emma Foley - Eric Harney - Fabien Boucher - Francesco Pantano - Gregory Thiemonge - Jakob Meng - Jesse Pretorius - Jiří Podivín - Joel Capitao - Jon Schlueter - Julia Kreger - Karolina Kula - Leif Madsen - Lon Hohberger - Luigi Toscano - Marios Andreou - Martin Kopec - Mathieu Bultel - Matthias Runge - Maurício Harley - Michael Johnson - Miguel Garcia Cruces - Nate Johnston - Nicolas Hicher - Paras Babbar - Pooja Jadhav - Rabi Mishra - Rafael Castillo - René Ribaud/780 - Riccardo Pittau - Ronelle Landy - Sagi Shnaidman - Sandeep Yadav - Sean Mooney - Shreshtha Joshi - Slawomir Kaplonski - Steve Baker - Takashi Kajinami - Tobias Urdin - Tristan De Cacqueray - Yatin Karel *The Next Release Cycle* At the end of one release, focus shifts immediately to the next release i.e Antelope. *Get Started* To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. Finally, for those that don’t have any hardware or physical resources, there’s the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. *Get Help* The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on OFTC IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS and TripleO IRC channels (#centos, #centos-devel in Libera.Chat network, and #tripleo on OFTC), however we have a more focused audience within the RDO venues. *Get Involved* To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and #tripleo on the OFTC IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube.

1 0

[neutron] Bug deputy Nov 7 to Nov 13
by Rodolfo Alonso Hernandez 14 Nov '22

14 Nov '22

Hello Neutrinos: This is the bug list from the past week: High: * https://bugs.launchpad.net/neutron/+bug/1996150: Neutron fails to create network with enforced scopes and new RBAC policies. Assigned: Slawek. * https://bugs.launchpad.net/neutron/+bug/1996129: With new RBAC enabled: Tempest test failing on NetworkNotFound. Duplicate of 1996150. Medium: * https://bugs.launchpad.net/neutron/+bug/1995972: L3 router is doing schedule_routers when adding/removing external gateway. Unassigned. * https://bugs.launchpad.net/neutron/+bug/1995974: [OVN] Router "router_extra_attributes" register is not created. Patch: https://review.opendev.org/c/openstack/neutron/+/864051 * https://bugs.launchpad.net/neutron/+bug/1996180: [OVN] "standard_attr" register missing during inconsistency check. Assigned: Rodolfo. Low: * https://bugs.launchpad.net/neutron/+bug/1996241: Manual install & Configuration in Neutron. Low hanging fruit. * https://bugs.launchpad.net/neutron/+bug/1996421: 'openstack port list' should display ports only from current project. Not sure this is a legit bug, commented in the bug and the patch. Invalid/opinion/incomplete/duplicated: * https://bugs.launchpad.net/neutron/+bug/1995872: A stuck INACTIVE port binding causes wrong l2pop fdb entries to be sent. Duplicated of https://bugs.launchpad.net/neutron/+bug/1979072. * https://bugs.launchpad.net/neutron/+bug/1996199: router external gateway assigning unsupported IPv6. Justification: https://bugs.launchpad.net/neutron/+bug/1996199/comments/1. Regards.

1 0