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
** Also affects: devstack
Importance: Undecided
Status: New
** Summary changed:
- Start keystone service failed with uwsgi in devstack
+ [devstack] keystone service fails to start after reboot
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1692767
Title:
[devstack] keystone service fails to start after reboot
Status in devstack:
New
Status in OpenStack Identity (keystone):
New
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.localdomain systemd[1]: [email protected]
failed.
Apr 23 22:42:46 devstack.localdomain systemd[1]: Starting Devstack
[email protected]...
Apr 23 22:42:46 devstack.localdomain [email protected][7242]: [uWSGI]
getting INI configuration from /etc/keystone/keystone-uwsgi-public.ini
Apr 23 22:42:46 devstack.localdomain [email protected][7242]:
open("./python_plugin.so"): No such file or directory [core/utils.c line 3686]
Apr 23 22:42:46 devstack.localdomain [email protected][7242]: !!!
UNABLE to load uWSGI plugin: ./python_plugin.so: cannot open shared object
file: No such file or directory !!!
Apr 23 22:42:46 devstack.localdomain [email protected][7242]: ***
Starting uWSGI 2.0.15 (64bit) on [Sun Apr 23 22:42:46 2017] ***
Apr 23 22:42:46 devstack.localdomain systemd[1]: [email protected]:
main process exited, code=exited, status=1/FAILURE
Apr 23 22:42:46 devstack.localdomain systemd[1]: Failed to start Devstack
[email protected].
Apr 23 22:42:46 devstack.localdomain systemd[1]: Unit
[email protected] entered failed state.
Apr 23 22:42:46 devstack.localdomain systemd[1]: [email protected]
failed.
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?
To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1692767/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
