[Bug 2064117] Re: keystone/noble, now 2:25.0.0-0ubuntu1 keystone -manage db_sync

Mon Apr 29 14:54:38 UTC 2024

Hi Johan

I'm not able to reproduce your problem; in my setup I've configured
mysql with a keystone database, username and password for access, and
then configured this in /etc/keystone/keystone.conf

I then ran the db_sync command to setup the database, created the fernet
keys and then successfully bootstrapped the deployment.

2024-04-29 14:48:45.073 12333 INFO alembic.runtime.migration [-] Context impl MySQLImpl.
2024-04-29 14:48:45.073 12333 INFO alembic.runtime.migration [-] Will assume non-transactional DDL.
2024-04-29 14:48:45.093 12333 INFO alembic.runtime.migration [-] Running upgrade  -> 27e647c0fad4, Initial version.
2024-04-29 14:48:45.939 12333 INFO alembic.runtime.migration [-] Running upgrade 27e647c0fad4 -> 29e87d24a316, Initial no-op Yoga expand migration.
2024-04-29 14:48:45.940 12333 INFO alembic.runtime.migration [-] Running upgrade 29e87d24a316 -> b4f8b3f584e0, Fix incorrect constraints.
2024-04-29 14:48:45.951 12333 INFO alembic.runtime.migration [-] Running upgrade b4f8b3f584e0 -> 11c3b243b4cb, Remove service_provider.relay_state_prefix server default.
2024-04-29 14:48:45.957 12333 INFO alembic.runtime.migration [-] Running upgrade 11c3b243b4cb -> 47147121, Add Identity Federation attribute mapping schema version.
2024-04-29 14:48:45.967 12333 INFO alembic.runtime.migration [-] Running upgrade 27e647c0fad4 -> e25ffa003242, Initial no-op Yoga contract migration.
2024-04-29 14:48:45.967 12333 INFO alembic.runtime.migration [-] Running upgrade e25ffa003242 -> 99de3849d860, Fix incorrect constraints.
2024-04-29 14:48:45.983 12333 INFO alembic.runtime.migration [-] Running upgrade 99de3849d860 -> c88cdce8f248, Remove duplicate constraints.
2024-04-29 14:49:26.124 13264 INFO keystone.common.fernet_utils [-] Created a new temporary key: /etc/keystone/fernet-keys/0.tmp
2024-04-29 14:49:26.125 13264 INFO keystone.common.fernet_utils [-] Become a valid new key: /etc/keystone/fernet-keys/0
2024-04-29 14:49:26.125 13264 INFO keystone.common.fernet_utils [-] Starting key rotation with 1 key files: ['/etc/keystone/fernet-keys/0']
2024-04-29 14:49:26.125 13264 INFO keystone.common.fernet_utils [-] Created a new temporary key: /etc/keystone/fernet-keys/0.tmp
2024-04-29 14:49:26.125 13264 INFO keystone.common.fernet_utils [-] Current primary key is: 0
2024-04-29 14:49:26.126 13264 INFO keystone.common.fernet_utils [-] Next primary key will be: 1
2024-04-29 14:49:26.126 13264 INFO keystone.common.fernet_utils [-] Promoted key 0 to be the primary: 1
2024-04-29 14:49:26.126 13264 INFO keystone.common.fernet_utils [-] Become a valid new key: /etc/keystone/fernet-keys/0
2024-04-29 14:49:36.731 13449 INFO keystone.common.utils [-] /etc/keystone/credential-keys/ does not appear to exist; attempting to create it
2024-04-29 14:49:36.732 13449 INFO keystone.common.fernet_utils [-] Created a new temporary key: /etc/keystone/credential-keys/0.tmp
2024-04-29 14:49:36.732 13449 INFO keystone.common.fernet_utils [-] Become a valid new key: /etc/keystone/credential-keys/0
2024-04-29 14:49:36.732 13449 INFO keystone.common.fernet_utils [-] Starting key rotation with 1 key files: ['/etc/keystone/credential-keys/0']
2024-04-29 14:49:36.732 13449 INFO keystone.common.fernet_utils [-] Created a new temporary key: /etc/keystone/credential-keys/0.tmp
2024-04-29 14:49:36.732 13449 INFO keystone.common.fernet_utils [-] Current primary key is: 0
2024-04-29 14:49:36.734 13449 INFO keystone.common.fernet_utils [-] Next primary key will be: 1
2024-04-29 14:49:36.734 13449 INFO keystone.common.fernet_utils [-] Promoted key 0 to be the primary: 1
2024-04-29 14:49:36.734 13449 INFO keystone.common.fernet_utils [-] Become a valid new key: /etc/keystone/credential-keys/0
2024-04-29 14:50:52.731 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created domain default
2024-04-29 14:50:52.755 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created project admin
2024-04-29 14:50:52.766 14749 WARNING keystone.common.password_hashing [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Truncating password to algorithm specific maximum length 72 characters.: keystone.exception.UserNotFound: Could not find user: admin.
2024-04-29 14:50:52.956 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created user admin
2024-04-29 14:50:52.962 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created role reader
2024-04-29 14:50:52.966 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created role member
2024-04-29 14:50:52.973 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created implied role where 70b64bb530a847ed9b3828f5db9b9071 implies 7542f73afffe4045878d16e33b5dbd1f
2024-04-29 14:50:52.978 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created role manager
2024-04-29 14:50:52.983 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created implied role where 7334cc0348a644d596199171daef93eb implies 70b64bb530a847ed9b3828f5db9b9071
2024-04-29 14:50:52.986 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created role admin
2024-04-29 14:50:52.991 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created implied role where ca5da711bb3f4fd184cb28f8f5e9e201 implies 7334cc0348a644d596199171daef93eb
2024-04-29 14:50:52.997 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created role service
2024-04-29 14:50:53.006 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Granted role admin on project admin to user admin.
2024-04-29 14:50:53.011 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Granted role admin on the system to user admin.
2024-04-29 14:50:53.015 14749 WARNING py.warnings [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] /usr/lib/python3/dist-packages/pycadf/identifier.py:71: UserWarning: Invalid uuid: RegionOne. To ensure interoperability, identifiers should be a valid uuid.
  warnings.warn(('Invalid uuid: %s. To ensure interoperability, '

2024-04-29 14:50:53.016 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created region RegionOne
2024-04-29 14:50:53.026 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created public endpoint http://localhost:5000/v3/
2024-04-29 14:50:53.032 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created internal endpoint http://localhost:5000/v3/
2024-04-29 14:50:53.037 14749 INFO keystone.cmd.bootstrap [None req-14f75b10-bd92-4eb7-a3cb-27f79bc6570e - - - - - -] Created admin endpoint http://localhost:5000/v3/

** Changed in: keystone (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/2064117

Title:
  keystone/noble,now 2:25.0.0-0ubuntu1 keystone -manage db_sync

Status in keystone package in Ubuntu:
  Incomplete

Bug description:
  Fresh ubuntu 24.04 install when running
  su -s /bin/sh -c "keystone-manage db_sync " keystone

  This ends up in /var/log/apache2/keystone.log

  2024-04-29 12:47:10.184549   File "/usr/lib/python3/dist-packages/pymysql/protocol.py", line 221, in raise_for_error
  2024-04-29 12:47:10.184554     err.raise_mysql_exception(self._data)
  2024-04-29 12:47:10.184572   File "/usr/lib/python3/dist-packages/pymysql/err.py", line 143, in raise_mysql_exception
  2024-04-29 12:47:10.184577     raise errorclass(errno, errval)
  2024-04-29 12:47:10.184629 sqlalchemy.exc.ProgrammingError: (pymysql.err.ProgrammingError) (1146, "Table 'keystone.project' doesn't exist")
  2024-04-29 12:47:10.184634 [SQL: SELECT project.id AS project_id, project.name AS project_name, project.domain_id AS project_domain_id, project.description AS project_description, project.enabled AS project_enabled, project.extra AS project_extra, project.parent_id AS project_parent_id, project.is_domain AS project_is_domain
  2024-04-29 12:47:10.184640 FROM project
  2024-04-29 12:47:10.184644 WHERE project.name = %(name_1)s AND project.domain_id = %(domain_id_1)s]
  2024-04-29 12:47:10.184648 [parameters: {'name_1': 'Default', 'domain_id_1': '<<keystone.domain.root>>'}]

  after dbsync is run the project table does exist so i think things are just done in wrong order, result is that keystone dosnt work afterwards though

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/2064117/+subscriptions