Bug 1038624

Summary: Packstack fails to install/start keystone
Product: [Community] RDO Reporter: Richard W.M. Jones <rjones>
Component: openstack-packstackAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WORKSFORME QA Contact: Nir Magnezi <nmagnezi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: aortega, ayoung, derekh, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-15 13:32:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
192.168.0.134_keystone.pp.log
none
openstack-setup.log
none
/var/log/keystone/keystone.log none

Description Richard W.M. Jones 2013-12-05 13:55:16 UTC
Description of problem:

On a fresh Fedora 19 install, keystone fails to either install
or start up (I'm not sure which).

Applying 192.168.0.134_keystone.pp
Applying 192.168.0.134_glance.pp
Applying 192.168.0.134_cinder.pp
                                                                                             [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.0.134_keystone.pp
Error: /Stage[main]/Keystone::Roles::Admin/Keystone_role[_member_]: Could not evaluate: Execution of '/usr/bin/keystone --endpoint http://127.0.0.1:35357/v2.0/ role-list' returned 1: Service Unavailable (HTTP 503)
You will find full trace in log /var/tmp/packstack/20131205-135009-N8YDI8/manifests/192.168.0.134_keystone.pp.log
Please check log file /var/tmp/packstack/20131205-135009-N8YDI8/openstack-setup.log for more information

The log files are attached.

Version-Release number of selected component (if applicable):

openstack-keystone-2013.2-1.fc20.noarch

How reproducible:

100%

Steps to Reproduce:
1. Just run packstack as per documentation.

Comment 1 Richard W.M. Jones 2013-12-05 13:56:10 UTC
Created attachment 833165 [details]
192.168.0.134_keystone.pp.log

Comment 2 Richard W.M. Jones 2013-12-05 13:56:37 UTC
Created attachment 833167 [details]
openstack-setup.log

Comment 3 Richard W.M. Jones 2013-12-05 13:57:11 UTC
Created attachment 833168 [details]
/var/log/keystone/keystone.log

Comment 4 Richard W.M. Jones 2013-12-05 13:57:41 UTC
Note I tried this with and without SELinux enabled.

Comment 5 Richard W.M. Jones 2013-12-05 13:59:39 UTC
Doesn't appear to be a firewall issue, and the daemon is running.

$ ps ax | grep keyst
26826 ?        Ss     0:00 /usr/bin/python /usr/bin/keystone-all --config-file /usr/share/keystone/keystone-dist.conf --config-file /etc/keystone/keystone.conf
31083 pts/1    S+     0:00 grep --color=auto keyst

$ sudo netstat -anp | grep 35357.*LISTEN
tcp        0      0 0.0.0.0:35357           0.0.0.0:*               LISTEN      26826/python

$ telnet 127.0.0.1 35357
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
HELP
<head>
<title>Error response</title>
</head>
<body>
<h1>Error response</h1>
<p>Error code 400.
<p>Message: Bad request syntax ('HELP').
<p>Error code explanation: 400 = Bad request syntax or unsupported method.
</body>
Connection closed by foreign host.

Comment 6 Adam Young 2013-12-11 18:27:04 UTC
The Keystone log shows keystone up and running:

2013-12-05 13:46:19.939 26826 INFO keystone.common.environment.eventlet_server [-] Starting /usr/bin/keystone-all on 0.0.0.0:35357

Which implies that the problem is network based.

It is probably a mistake to have Keystone listen on 0.0.0.0 as that is a wildcard address, and instead it should be based on either 127.0.0.1 if it is only for localhost, or on the actual public IP address of the server.

Comment 7 Richard W.M. Jones 2013-12-12 16:50:27 UTC
For whatever reason, I started again from scratch (fresh Fedora 19
install, packstack) and have now got everything installed and Keystone
is working.

Comment 8 Alvaro Lopez Ortega 2014-01-15 13:32:13 UTC
It seems to be working for everybody now.