Bug 971465 - Creating the Public Key Infrastructure Files - Creates log file owned by root. Creating the Public Key Infrastructure Files - Creates log file owne...
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Installation_and_Configuration_Guide (Show other bugs)
Unspecified Unspecified
high Severity high
: ---
: 3.0
Assigned To: Stephen Gordon
: Documentation
Depends On:
  Show dependency treegraph
Reported: 2013-06-06 11:15 EDT by Stephen Gordon
Modified: 2013-07-01 16:25 EDT (History)
0 users

See Also:
Fixed In Version: Red_Hat_OpenStack-Installation_and_Configuration_Guide-3-en-US-3-17
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-01 16:25:01 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stephen Gordon 2013-06-06 11:15:34 EDT
Document URL: 


Section Number and Name: Creating the Public Key Infrastructure Files

Describe the issue: 

keystone-manage pki_setup is run as root. This results in the /var/log/keystone/keystone.log being created and owned by root. As a result when the openstack-keystone service is started it comes up as OK but silently fails in he background:

[root@localhost ~]# service openstack-keystone start
Starting keystone:                                         [  OK  ]
[root@localhost ~]# service openstack-keystone status
keystone dead but pid file exists
[root@localhost ~]# tail /var/log/keystone/keystone.log 
[root@localhost ~]# 

This isn't immediately apparent to the user until the attempt to create the service:

# keystone service-create --name=keystone --type=identity \
>         --description="Keystone Identity Service" 
[Errno 111] Connection refused

Suggestions for improvement: 

Run keystone-manager pki_setup as the keystone user:

su keystone -s /bin/sh -c "keystone-manage pki_setup --keystone-user=keystone --keystone-group=keystone"


Remove /var/log/keystone/keystone.log or change ownership to keystone user.

Note You need to log in before you can comment on or make changes to this bug.