[devstack] keystone service fails to start after reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Tao Li | ||
devstack |
Fix Released
|
Undecided
|
Kirill Zaitsev |
Bug Description
Enviroment
OS: CentOS7.2
I deployed the devstack environment successfully in CentOS system. After rebooting the CentOS system, the keystone service could not be started. The uwsgi raised exception as follows.
Apr 23 22:38:53 devstack.
Apr 23 22:42:46 devstack.
Apr 23 22:42:46 devstack.
Apr 23 22:42:46 devstack.
Apr 23 22:42:46 devstack.
Apr 23 22:42:46 devstack.
Apr 23 22:42:46 devstack.
Apr 23 22:42:46 devstack.
Apr 23 22:42:46 devstack.
Apr 23 22:42:46 devstack.
So i think this is a bug. I tried to create the /var/run/uwsgi directory and chown it stack user. Then it works.
sudo mkdir -p /var/run/uwsgi
sudo chown stack:stack uwsgi
So what do you think that?
Changed in keystone: | |
assignee: | nobody → Tao Li (eric-litao) |
The correct way to do it would be to add a tmpfiles.d config file, that would create the directory at startup. also it's not about keystone, but about devstack