Fully updated debian trixie
Pluss added in /etc/apt/sources.list
deb http://trixie-flamingo.debian.net/debian trixie-flamingo-backports main
deb http://trixie-flamingo.debian.net/debian trixie-flamingo-backports-
nochange
# debconf-set-selections game
# apt-get install openstack-cloud-identity
.....
keystone --keystone-group keystone'...
Running: su keystone -s /bin/sh -c 'keystone-manage credential_setup --
keystone-user keystone --keystone-group keystone'...
Synchronizing state of keystone.service with SysV service script with /
usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable keystone
Created symlink '/etc/systemd/system/multi-user.target.wants/
keystone.service' → '/usr/lib/systemd/system/keystone.service'.
Sleeping 10 seconds to make sure the keystone daemon is up and running:
10...9...8...7...6...5...4...3...2...1...0
===> Bootstraping tenants with 'keystone-manage bootstrap':
Now doing: su keystone -s /bin/sh -c 'keystone-manage bootstrap --
bootstrap-role-name admin --bootstrap-service-name keystone --bootstrap-
region-id regionOne --bootstrap-admin-url http://192.168.1.17:5000 --
bootstrap-public-url http://192.168.1.17:5000 --bootstrap-internal-url
http://192.168.1.17:5000'
===> Editing bootstraped tenants and adding default roles
Fixing-up: admin-project-desc Failed to discover available identity
versions when contacting http://192.168.1.17:5000/v3/. Attempting to
parse version from URL.
Unable to establish connection to http://192.168.1.17:5000/v3/auth/
tokens: HTTPConnectionPool(host='192.168.1.17', port=5000): Max retries
exceeded with url: /v3/auth/tokens (Caused by
NewConnectionError('<urllib3.connection.HTTPConnection object at
0x7f7d52707390>: Failed to establish a new connection: [Errno 111]
Connection refused'))
dpkg: error processing package keystone (--configure):
installed keystone package post-installation script subprocess
returned error exit status 1
dpkg: dependency problems prevent configuration of openstack-cloud-
identity:
openstack-cloud-identity depends on keystone; however:
Package keystone is not configured yet.
-------------------
# journalctl -xeu keystone
Sep 18 13:41:03 kvm7 systemd[1]: keystone.service: Dependency
After=keystone.service is dropped.
Sep 18 13:41:04 kvm7 systemd[1]: keystone.service: Dependency
After=keystone.service is dropped.
Sep 18 13:41:04 kvm7 systemd[1]: Started keystone.service - OpenStack
Keystone API (keystone).
Subject: A start job for unit keystone.service has finished successfully
Defined-By: systemd
Support: https://www.debian.org/support
A start job for unit keystone.service has finished successfully.
The job identifier is 2825.
Sep 18 13:41:05 kvm7 systemd[1]: keystone.service: Deactivated
successfully.
Subject: Unit succeeded
Defined-By: systemd
Support: https://www.debian.org/support
The unit keystone.service has successfully entered the 'dead' state.
-------------------
/etc/init.d/keystone
appr line 35 the service exited because the file
/usr/bin/keystone-wsgi-public is not found
if [ -n "${UWSGI_PORT}" ] && [ -n "${UWSGI_INI_PATH}" ] && [ -n
"${UWSGI_INI_APP}" ] ; then
if ! [ -f "${UWSGI_INI_APP}" ] ; then
exit 0
fi
------------------
Forcing to use the keystone package from trixie-epoxy and it works
Patching setup.cfg to add back the two files and flamingo keystone works
again.
Assumes this is NOT the correct way to do it, but my knowledge fails.
------------------
# This release note explains why
https://opendev.org/openstack/keystone/src/
commit/82c80dccf6c2e74e27b90f5204de6da1fc6bd76d/releasenotes/notes/
remove-wsgi-scripts-615b97ee4d6e0de2.yaml
upgrade:
- |
The WSGI scripts, ``keystone-wsgi-admin`` and ``keystone-wsgi-
public``,
have been removed. Deployment tooling should instead reference the
Python
module paths for the service, ``keystone.wsgi.api``, if their
chosen WSGI
server supports this (gunicorn, uWSGI) or implement a ``.wsgi`` script
themselves if not (mod_wsgi).
------------------
mvh
Svein-Erik