Red Hat Bugzilla – Bug 946915
can't start openstack-keystone
Last modified: 2015-06-29 21:31:02 EDT
keystone is failing to start, as it can't write to the keystone log file
# ls -l /var/log/keystone/
-rw-r--r--. 1 root root 0 Mar 31 22:54 keystone.log
I'm guessing the file was created with keystone-manage db_sync was run
using grizzly side repo
What's running keystone-manage as root?
openstack-db --init for example does:
runuser -s /bin/sh $APP -c "$APP-manage $db_sync"
the packstack and the puppet modules both use keystone-manage, has something changed this always worked upto now?
If the puppet modules run keystone-manage as root then I don't know how it worked as nothing has changed recently in this regard?
I hit this issue too (on RHEL 6.4) and so did Thomas Oulevey from Cern. More info on rhos-list:
by the looks of it this is being cause by a change in keystone-manage,
specifically this commit
keystone-manage didn't used to create the keystone.log file but now it does
I submitted a update to packstack
(In reply to comment #5)
> I submitted a update to packstack
Is there a build with that?
*** Bug 946887 has been marked as a duplicate of this bug. ***
Not yet, will create the build today.
FYI from dprince
> fixed this issue in the upstream keystone puppet modules here:
*** Bug 981587 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.
More information and reason for this action is here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Hit this bug again on
Version : 2014.1.1
Release : 0.4.dev1018.fc21
during a --allinone install on Fedora 20.
Bug #1080438 might also be related as it is also intermittent and related to something in puppet land setting root permissions sometimes
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.