- openstack-discuss - lists.openstack.org

Ansible OpenStack Collection 2.0.0 has been released 🥳
by Jakob Meng 01 Feb '23

01 Feb '23

Hello contributors and users, version 2.0.0 [0] of our Ansible collection for OpenStack clouds aka openstack.cloud has been released 🥂 It is a complete overhaul of our code base and brings full compatibility with openstacksdk 1.0.0 🤩 Highlights of this release are: - three new modules which for example provide a generic and uniform API for interacting with OpenStack cloud resources [1], [2], - a complete refactoring of all existing modules bringing dozens of bugfixes, new features as well as consistent and properly documented module results and options, - 100% compatibility with openstacksdk's first major release 1.0.0, - new guides for contributors [3] from devstack setup over coding guidelines to our release process and - massively increased CI coverage with many new integration tests, now covering all modules and plugins [4]. Note, this 2.0.0 release *breaks backward compatibility* with previous 1.x.x releases [5] ⚠️ - 2.x.x releases of this collection are compatible with openstacksdk 1.x.x and later *only*, - 1.x.x releases of this collection are compatible with openstacksdk 0.x.x prior to 0.99.0 *only*, - 2.x.x releases of are not backward compatible with 1.x.x releases [0], - 1.x.x release series will be in maintenance mode now and receive bugfixes only. However, this collection as well as openstacksdk continue to be backward compatible with clouds running on older OpenStack releases. For example, it is fine and a fully supported use case to use this 2.0.0 release with clouds based on OpenStack Train, Wallaby or Zed. Feel encouraged to always use the latest releases of this collection and openstacksdk regardless of which version of OpenStack is installed in your cloud. This collection is compatible with and tested with Ansible 2.9 and later. However, support for old short module names such as os_server have been dropped with this release. You have to call modules using their FQCN such as openstack.cloud.server instead. Many thanks to all contributors who made this release possible. Tens of thousands LOCs have been reviewed and changed and fixed and tested throughout last year. You rock! [0] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… [1] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… [2] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… [3] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… [4] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… [5] https://opendev.org/openstack/ansible-collections-openstack/src/branch/mast… Best, Jakob

1 0

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

01 Feb '23

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

1 1

[ZED][Kyestone][Application_credentials] Conflict occurred attempting to store application_credential - Duplicate entry found
by Vish Mudemela 01 Feb '23

01 Feb '23

Hello all, 1. I have created application credentials with the name "sa_capacity" as role - reader. 2. I have deleted application credentials , I wanted to add some access rules. 3. verified by command - *openstack application credential show sa_capacity* got output as *"**No application credential with a name or ID of 'sa_capacity' exists."* 4.verified using *openstack application credential list *, confirmed there is no application credential with name "sa_capacity" 5. no application creds on my username too *"openstack application credential list --user <<username>> --user-domain <<domain_name>>"* 6. Trying to recreate application credentials with the *same name(sa_capacity) *with a role reader and added some access rules. I got an error* "Conflict occurred attempting to store application_credential - Duplicate entry found with name sa_capacity. (HTTP 409) (Request-ID: req-0e58b336-a59b-490d-b946-30c28ca44777)"* *7.* I even tried with a different name that's never been configured* "sa_capcity_1"* but it says *Conflict occurred attempting to store application_credential - Duplicate entry found with name sa_capacity_1. (HTTP 409)* Any idea what's wrong here? Below are the keystone logs. *keystone logs:* 2023-01-31 21:51:07.193 670 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystone/common/manager.py", line 115, in wrapped 2023-01-31 21:51:07.193 670 ERROR keystone.server.flask.application __ret_val = __f(*args, **kwargs) 2023-01-31 21:51:07.193 670 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystone/application_credential/core.py", line 137, in create_application_credential 2023-01-31 21:51:07.193 670 ERROR keystone.server.flask.application ref = self.driver.create_application_credential( 2023-01-31 21:51:07.193 670 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystone/common/sql/core.py", line 563, in wrapper 2023-01-31 21:51:07.193 670 ERROR keystone.server.flask.application raise exception.Conflict(type=conflict_type, 2023-01-31 21:51:07.193 670 ERROR keystone.server.flask.application keystone.exception.Conflict: Conflict occurred attempting to store application_credential - Duplicate entry found with name sa_capacity. 2023-01-31 21:51:07.193 670 ERROR keystone.server.flask.application 2023-01-31 21:53:10.461 669 INFO keystone.token.token_formatters [None req-75dc9499-18aa-4f55-8a63-633b9ef316c5 910a75448974f088b01f96e09db0667737b84a5663dbaa2a142c4648187f40de e68db2302b1d44beb5d62c6a6268ab26 - - e025affd9237457a9d7036fb10a9b626 e025affd9237457a9d7036fb10a9b626] Fernet token created with length of 268 characters, which exceeds 255 characters 2023-01-31 21:53:14.131 673 INFO keystone.token.token_formatters [None req-66aa818c-754e-46bf-a393-6115eb14b2d3 910a75448974f088b01f96e09db0667737b84a5663dbaa2a142c4648187f40de e68db2302b1d44beb5d62c6a6268ab26 - - e025affd9237457a9d7036fb10a9b626 e025affd9237457a9d7036fb10a9b626] Fernet token created with length of 268 characters, which exceeds 255 characters 2023-01-31 21:53:55.977 671 WARNING py.warnings [None req-0e58b336-a59b-490d-b946-30c28ca44777 fba6720038a31a4c1cf2e001022466a504d6d78ec9b10ac1a8adbfd7b8902fdc e68db2302b1d44beb5d62c6a6268ab26 - - e025affd9237457a9d7036fb10a9b626 e025affd9237457a9d7036fb10a9b626] /var/lib/kolla/venv/lib/python3.10/site-packages/keystone/application_credential/backends/sql.py:144: SAWarning: New instance <ApplicationCredentialAccessRuleModel at 0x7f714f74c910> with identity key (<class 'keystone.application_credential.backends.sql.ApplicationCredentialAccessRuleModel'>, (96, 249), None) conflicts with persistent instance <ApplicationCredentialAccessRuleModel at 0x7f714f74ec80> external_id=access_rule['id']).first() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application [None req-0e58b336-a59b-490d-b946-30c28ca44777 fba6720038a31a4c1cf2e001022466a504d6d78ec9b10ac1a8adbfd7b8902fdc e68db2302b1d44beb5d62c6a6268ab26 - - e025affd9237457a9d7036fb10a9b626 e025affd9237457a9d7036fb10a9b626] Conflict occurred attempting to store application_credential - Duplicate entry found with name sa_capacity.: keystone.exception.Conflict: Conflict occurred attempting to store application_credential - Duplicate entry found with name sa_capacity. 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application Traceback (most recent call last): 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1900, in _execute_context 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application self.dialect.do_execute( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 732, in do_execute 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application cursor.execute(statement, parameters) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/cursors.py", line 148, in execute 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application result = self._query(query) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/cursors.py", line 310, in _query 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application conn.query(q) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/connections.py", line 548, in query 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application self._affected_rows = self._read_query_result(unbuffered=unbuffered) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/connections.py", line 775, in _read_query_result 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application result.read() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/connections.py", line 1156, in read 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application first_packet = self.connection._read_packet() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/connections.py", line 725, in _read_packet 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application packet.raise_for_error() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/protocol.py", line 221, in raise_for_error 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application err.raise_mysql_exception(self._data) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/err.py", line 143, in raise_mysql_exception 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application raise errorclass(errno, errval) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application pymysql.err.IntegrityError: (1062, "Duplicate entry '96-249' for key 'PRIMARY'") 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application The above exception was the direct cause of the following exception: 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application Traceback (most recent call last): 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystone/common/sql/core.py", line 528, in wrapper 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application return method(*args, **kwargs) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystone/application_credential/backends/sql.py", line 144, in create_application_credential 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application external_id=access_rule['id']).first() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/query.py", line 2823, in first 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application return self.limit(1)._iter().first() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/query.py", line 2907, in _iter 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application result = self.session.execute( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 1660, in execute 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application ) = compile_state_cls.orm_pre_session_exec( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/context.py", line 316, in orm_pre_session_exec 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application session._autoflush() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 2246, in _autoflush 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application self.flush() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3383, in flush 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application self._flush(objects) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3522, in _flush 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application with util.safe_reraise(): 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 70, in __exit__ 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application compat.raise_( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/util/compat.py", line 208, in raise_ 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application raise exception 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/session.py", line 3483, in _flush 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application flush_context.execute() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/unitofwork.py", line 456, in execute 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application rec.execute(self) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/unitofwork.py", line 630, in execute 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application util.preloaded.orm_persistence.save_obj( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/persistence.py", line 245, in save_obj 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application _emit_insert_statements( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/orm/persistence.py", line 1097, in _emit_insert_statements 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application c = connection._execute_20( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1705, in _execute_20 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application return meth(self, args_10style, kwargs_10style, execution_options) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/sql/elements.py", line 333, in _execute_on_connection 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application return connection._execute_clauseelement( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1572, in _execute_clauseelement 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application ret = self._execute_context( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1943, in _execute_context 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application self._handle_dbapi_exception( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 2122, in _handle_dbapi_exception 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application util.raise_(newraise, with_traceback=exc_info[2], from_=e) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/util/compat.py", line 208, in raise_ 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application raise exception 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 1900, in _execute_context 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application self.dialect.do_execute( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 732, in do_execute 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application cursor.execute(statement, parameters) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/cursors.py", line 148, in execute 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application result = self._query(query) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/cursors.py", line 310, in _query 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application conn.query(q) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/connections.py", line 548, in query 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application self._affected_rows = self._read_query_result(unbuffered=unbuffered) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/connections.py", line 775, in _read_query_result 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application result.read() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/connections.py", line 1156, in read 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application first_packet = self.connection._read_packet() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/connections.py", line 725, in _read_packet 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application packet.raise_for_error() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/protocol.py", line 221, in raise_for_error 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application err.raise_mysql_exception(self._data) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/pymysql/err.py", line 143, in raise_mysql_exception 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application raise errorclass(errno, errval) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application oslo_db.exception.DBDuplicateEntry: (pymysql.err.IntegrityError) (1062, "Duplicate entry '96-249' for key 'PRIMARY'") 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application [SQL: INSERT INTO application_credential_access_rule (application_credential_id, access_rule_id) VALUES (%(application_credential_id)s, %(access_rule_id)s)] 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application [parameters: {'application_credential_id': 96, 'access_rule_id': 249}] 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application (Background on this error at: https://sqlalche.me/e/14/gkpj) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application During handling of the above exception, another exception occurred: 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application Traceback (most recent call last): 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/flask/app.py", line 1820, in full_dispatch_request 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application rv = self.dispatch_request() 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/flask/app.py", line 1796, in dispatch_request 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/flask_restful/__init__.py", line 467, in wrapper 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application resp = resource(*args, **kwargs) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/flask/views.py", line 107, in view 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application return current_app.ensure_sync(self.dispatch_request)(**kwargs) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/flask_restful/__init__.py", line 582, in dispatch_request 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application resp = meth(*args, **kwargs) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystone/api/users.py", line 669, in post 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application ref = app_cred_api.create_application_credential( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystone/common/manager.py", line 115, in wrapped 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application __ret_val = __f(*args, **kwargs) 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystone/application_credential/core.py", line 137, in create_application_credential 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application ref = self.driver.create_application_credential( 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application File "/var/lib/kolla/venv/lib/python3.10/site-packages/keystone/common/sql/core.py", line 563, in wrapper 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application raise exception.Conflict(type=conflict_type, 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application keystone.exception.Conflict: Conflict occurred attempting to store application_credential - Duplicate entry found with name sa_capacity. 2023-01-31 21:53:55.981 671 ERROR keystone.server.flask.application Thanks Vish

1 0

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

01 Feb '23

Hi everyone, a bit late but nevertheless a quick reminder: the next meeting of the Public Cloud SIG is on February 1st (tomorrow - depending on your timezone ;) at 0800 UTC. We meet on IRC in #openstack-operators. See also here for all other details: https://wiki.openstack.org/wiki/PublicCloudSIG regards felix

1 0

How to create a dynamic pollster subsystem to create a pollster for senlin cluster
by Uday Dikshit 01 Feb '23

01 Feb '23

Hello Team We are a public cloud provider based on Openstack. We are working to create Autoscaling with aodh and senlin in Kolla-ansible Openstack Wallaby release. We are facing an issue as ceilometer does not support metrics for senlin cluster as a resource. Our aim is to use https://docs.openstack.org/ceilometer/wallaby/admin/telemetry-dynamic-polls… to generate a pollster to collect data for senlin. We were looking if anybody in the community has ever used this feature. OpenStack Docs: Introduction to dynamic pollster subsystem<https://docs.openstack.org/ceilometer/wallaby/admin/telemetry-dynamic-polls…> Current limitations of the dynamic pollster system¶. Currently, the following types of APIs are not supported by the dynamic pollster system: Tenant APIs: Tenant APIs are the ones that need to be polled in a tenant fashion. docs.openstack.org 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

[trove] Unable to manage databases with mariadb 10.7
by Rishat Azizov 31 Jan '23

31 Jan '23

Hello! I get this error when listing databases: "An error occurred communicating with the guest: 'utf8mb3_general_ci' not a valid collation.\nTraceback (most recent call last):\n\n File \"/opt/guest-agent-venv/lib/python3.8/site-packages/oslo_messaging/rpc/server.py\", line 165, in _process_incoming\n res = self.dispatcher.dispatch(message)\n\n File \"/opt/guest-agent-venv/lib/python3.8/site-packages/oslo_messaging/rpc/dispatcher.py\", line 309, in dispatch\n return self._do_dispatch(endpoint, method, ctxt, args)\n\n File \"/opt/guest-agent-venv/lib/python3.8/site-packages/oslo_messaging/rpc/dispatcher.py\", line 229, in _do_dispatch\n result = func(ctxt, **new_args)\n\n File \"/opt/guest-agent-venv/lib/python3.8/site-packages/osprofiler/profiler.py\", line 160, in wrapper\n result = f(*args, **kwargs)\n\n File \"/opt/guest-agent-venv/lib/python3.8/site-packages/trove/guestagent/datastore/manager.py\", line 812, in list_databases\n return self.adm.list_databases(limit, marker, include_marker)\n\n File \"/opt/guest-agent-venv/lib/python3.8/site-packages/trove/guestagent/datastore/mysql_common/service.py\", line 341, in list_databases\n mysql_db = models.MySQLSchema(name=database[0],\n\n File \"/opt/guest-agent-venv/lib/python3.8/site-packages/trove/common/db/mysql/models.py\", line 46, in __init__\n self.collate = collate\n\n File \"/opt/guest-agent-venv/lib/python3.8/site-packages/trove/common/db/mysql/models.py\", line 85, in collate\n raise ValueError(_(\"'%s' not a valid collation.\") % value)\n\nValueError: 'utf8mb3_general_ci' not a valid collation.\n.❌ 400 get /instances/78ffcc29-9a36-486d-aa4f-f4133511696d/databases trustId: a8daa2804e404a28b64df50fb824bb63" Listing failed becase in mariadb 10.7 utf8_general_ci aliased to utf8mb3_general_ci. Could you please help with this error?

1 0

[neutron][kolla] Do neutron agents in compute nodes connect to neutron database ?
by ZAOUAM Soufian (EXT) 31 Jan '23

31 Jan '23

Hi all, Do neutron agents in compute nodes have to connect to neutron database ? We are maintaining an Openstack using kolla-ansible (ussuri version). We noticed that the 4 neutron agents on compute nodes: neutron-l3-agent, neutron-metadata-agent, neutron-openvswitch-agent, neutron-dhcp-agent are all using the same neutron.conf config file, but we are wondering if they actually use [database] or is it redundant ? If no, is it safe to remove the [database] section from the neutron.conf for these agents? Best regards, ========================================================= Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et susceptibles de contenir des informations couvertes par le secret professionnel. Ce message est etabli a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme falsifie. ========================================================= This message and any attachments (the "message") are confidential, intended solely for the addresses, and may contain legally privileged information. Any unauthorized use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. =========================================================

2 1

[all][elections][ptl][tc] Combined PTL/TC bugbear cycle Election Season
by Ian Y. Choi 31 Jan '23

31 Jan '23

Election details: https://governance.openstack.org/election/ The nomination period officially begins Feb 01, 2023 23:45 UTC. Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. Due to circumstances of timing, PTL and TC elections for the coming cycle will run concurrently; deadlines for their nomination and voting activities are synchronized but will still use separate ballots. Please note, if only one candidate is nominated as PTL for a project team during the PTL nomination period, that candidate will win by acclaim, and there will be no poll. There will only be a poll if there is more than one candidate stepping forward for a project team's PTL position. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you which to discuss in private please email any of the election officials[1] so that we may address your concerns. Thank you, [1] https://governance.openstack.org/election/#election-officials

1 1

[cinder][requirements] python-cinderclient Yoga gate broken due to rtslib-fb
by Rajat Dhasmana 30 Jan '23

30 Jan '23

Hello, Currently python-cinderclient yoga gate is broken because *python-cinderclient-functional-py39* job is failing. Upon looking into the logs, I found the *cinder-rtstool delete *command failing[1]. Jan 16 07:58:14.935519 np0032740756 cinder-volume[115744]: ERROR cinder.volume.targets.lio Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf cinder-rtstool delete iqn.2010-10.org.openstack:volume-095ce534-8ef7-45c8-867c-f6d4fbc2b02d Jan 16 07:58:14.935519 np0032740756 cinder-volume[115744]: ERROR cinder.volume.targets.lio Exit code: 1 Jan 16 07:58:14.935519 np0032740756 cinder-volume[115744]: ERROR cinder.volume.targets.lio Stdout: '' Looking further into the traceback, this seems to be the main issue. line 215, in _gen_attached_luns\n for tpgt_dir in listdir(tpgts_base):\nNotADirectoryError: [Errno 20] Not a directory: \'/sys/kernel/config/target/iscsi/cpus_allowed_list\'\n' I found a similar (not exact) error in thread[2] to which there was a reply that it was fixed[3]. The fix is included in version 2.1.75[4] but the version pinned in upper constraints for yoga is 2.1.74[5]. I've tested the version bump in these DNM patches[6][7] and it works. A quick code search reveals that cinder is the only project actively using this lib[8]. My question for the requirements team is, is it OK to bump the requirement to allow cinderclient yoga gate to pass since it's blocking backports? [1] https://zuul.opendev.org/t/openstack/build/a282bfbb6b0a4148a69694db6ab7eb69… [2] https://www.spinics.net/lists/linux-scsi/msg172264.html [3] https://www.spinics.net/lists/linux-scsi/msg172265.html [4] https://github.com/open-iscsi/rtslib-fb/commit/8d2543c4da62e962661011fea5b1… [5] https://github.com/openstack/requirements/blob/stable/yoga/upper-constraint… [6] https://review.opendev.org/c/openstack/python-cinderclient/+/870513 [7] https://review.opendev.org/c/openstack/requirements/+/870714 [8] https://codesearch.opendev.org/?q=rtslib-fb&i=nope&literal=nope&files=&excl… Thanks Rajat Dhasmana

2 2

[Keystone | python-openstackclient] Fedartion with OAuth2.0/OIDC
by Niklas Schwarz 30 Jan '23

30 Jan '23

Hey there, I'm currently investigating the features of openstack federated identity and oauth2/oidc with keycloak as an identity provider. Following the documentation [1] I have successfully deployed a setup where it is possible to login via the horizion board using the login of keycloak. As defined in the documentation I'm using apache2 with the mod_auth_openidc module. So far so good... If I try to access the api via the openstack-cli using the following configuration ``` OS_AUTH_URL=https://<openstack-ip>/identity/v3 OS_AUTH_TYPE=v3oidcpassword OS_IDENTITY_PROVIDER=keycloak OS_PROTOCOL=openid OS_USERNAME=<keycloak-user> OS_PASSWORD=<keycloak-password> OS_PROJECT=test OS_OPENID_SCOPE='openid email profile' OS_DISCOVERY_ENDPOINT=https:// <keycloak-ip>/realms/<realm>/.well-known/openid-configuration OS_ACCESS_TOKEN_TYPE=access_token OS_CLIENT_ID=<client-id> OS_CLIENT_SECRET=<client-secret> ``` the http-status-code of the server is 500. Inspecting the logs , I found the problem in the mod_auth_openidc modul which expects a content-type of application/x-www-form-urlencoded. Is there any way to change the content-type the openstack-cli from json to urlencoded or am I missing a step in the configuration or something else? Thanks in advanced Niklas [1] https://docs.openstack.org/keystone/zed/admin/federation/configure_federati…

1 0