Comment 4 for bug 1483259
Revision history for this message
| Vladislav Belogrudov (vlad-belogrudov) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
7020100
(Get the code!)
I ran kestone initially and it ran OK but did not create anything due to 'su' problem - some kernels don't allow 'su' inside of a container (also the same can happen during table migration and many other possibilities - lack of space, memory,...). To reinit the service I had to delete user/database and run ansible playbook again.
Status from bootstrapping container is not tracked so far so normal keystones started after the former exited. If status of bootstrapping could be taken into account the problem would not occur.