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

2024-04-30 Thread James Page
OK - marking as invalid then! ** Changed in: keystone (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064117 Title: keystone/noble,now

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

2024-04-30 Thread Johan Bosch
I think i narrowed it down, it seems it was my galera cluster that was a bit out of wack, sorry for the false alarm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064117 Title: keystone/noble,now

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

2024-04-29 Thread Johan Bosch
Yea that looks alot better then mine. il try to have some time tomorrow and i nuke the cluster and make a clean install and do things in a bit of a diffrent order i think -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

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

2024-04-29 Thread James Page
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