This is the verification that I ran through: 1) juju run --application keystone "sudo test -f /etc/cron.d/keystone- token-flush && echo 'Exists'" --format=yaml
2) Commented /etc/cron.d/keystone-token-flush 3) Killed all the mysql threads *) SELECT trx_mysql_thread_id as ID, trx_id, trx_query, trx_started, trx_state FROM information_schema.innodb_trx WHERE trx_state = "RUNNING" AND trx_query LIKE "DELETE FROM token%" ORDER BY trx_started; *) KILL thread_id; *) KILL CONNECTION thread_id; 4) Manually run the token_flush command *) sudo -H -u keystone bash -c "/usr/bin/keystone-manage token_flush > /tmp/token-flush.log" After running this, provide me the the following details as attachments into this case. (Please connect to the database using the before mentioned method). 5) Re-enable the cronjob, and perform the following queries on the database to check if there were any locks or stuck transactions. SHOW open tables WHERE In_use > 0; SELECT * FROM information_schema.innodb_locks; SELECT * FROM information_schema.innodb_trx ORDER BY trx_started; SHOW ENGINE innodb status; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649616 Title: Keystone Token Flush job does not complete in HA deployed environment To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1649616/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
