[Rdo-list] Packstack error
Arash Kaffamanesh
ak at cloudssky.com
Fri Nov 7 10:54:24 UTC 2014
Hi David,
after setting selinux to permissive, the change takes affect after a
reboot, or you can force it without reboot with "setenforce 0".
In general for evaluation it might be recommendable to go with CentOS 7
first.
By the way I wrote this small how to some weeks ago, which could be of help:
http://ow.ly/Clrq5
-Arash
On Fri, Nov 7, 2014 at 11:47 AM, David Ocana <docana at ebi.ac.uk> wrote:
> Hi Arash,
>
> Thanks for the quick reply. Sorry I forgot to mention that the OS is rhel
> 7, and selinux was not set to permisive.I just changed it but I get the
> same error:
>
> # setenforce permissive
> # packstack --allinone
> [...]
> ERROR : Error appeared during Puppet run: 10.8.6.2_keystone.pp
> Error: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]:
> Could not evaluate: Execution of '/usr/bin/keystone --os-endpoint
> http://127.0.0.1:35357/v2.0/ service-list' returned 1: Service
> Unavailable (HTTP 503)
>
> Firewalld is not running
>
> # systemctl status firewalld
> firewalld.service - firewalld - dynamic firewall daemon
> Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled)
> Active: inactive (dead)
>
> I'll keep going with this for a little bit, but If CentOs 7 is working
> I'll probably change the OS and I'll give it a try.
>
> Thanks,
> David
>
> On 07/11/14 10:34, Arash Kaffamanesh wrote:
>
>> David,
>> On which OS are you deploying? CentOS 7?
>> I did the AIO and multi node installation several times on CentOS 7
>> without any problems.
>> By the way, did you set selinux to permissive? Is firewalld running? If
>> yes disable both.
>>
>> -Arash
>>
>>
>> On Fri, Nov 7, 2014 at 11:24 AM, David Ocana <docana at ebi.ac.uk <mailto:
>> docana at ebi.ac.uk>> wrote:
>>
>> Hi everyone,
>>
>> I'm installing the latest juno RDO release and I ran into this
>> problem:
>>
>> # yum -y update
>> # yum install rdo-release-juno-1.noarch.rpm
>> # yum install -y openstack-packstack
>> # packstack --allinone
>> Installing:
>> Clean Up [ DONE ]
>> Setting up ssh keys [ DONE ]
>> Discovering hosts' details [ DONE ]
>> Adding pre install manifest entries [ DONE ]
>> [...]
>> 10.8.6.2_keystone.pp: [ ERROR ]
>> Applying Puppet manifests [ ERROR ]
>>
>> ERROR : Error appeared during Puppet run: 10.8.6.2_keystone.pp
>> Error:
>> /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]:
>> Could not evaluate: Execution of '/usr/bin/keystone --os-endpoint
>> http://127.0.0.1:35357/v2.0/ service-list' returned 1: Service
>> Unavailable (HTTP 503)
>> You will find full trace in log
>> /var/tmp/packstack/20141107-090534-05fJzm/manifests/10.8.
>> 6.2_keystone.pp.log
>> Please check log file
>> /var/tmp/packstack/20141107-090534-05fJzm/openstack-setup.log for
>> more information
>>
>> The service seems to be running because you get a 503 response,
>> but I checked it:
>> -------------------
>> # netstat -putln | grep 35357
>> tcp 0 0 0.0.0.0:35357 <http://0.0.0.0:35357>
>> 0.0.0.0:* LISTEN 24884/python
>>
>> -------------------
>>
>> I checked the file
>> /var/tmp/packstack/20141107-090534-05fJzm/manifests/10.8.
>> 6.2_keystone.pp.log
>> and this is the most relevant:
>> -----------------
>> Notice:
>> /Stage[main]/Keystone/Keystone_config[database/idle_timeout]/ensure:
>> created
>> Notice:
>> /Stage[main]/Keystone/Keystone_config[DEFAULT/verbose]/ensure:
>> created
>> Notice: /Stage[main]/Keystone::Db::Sync/Exec[keystone-manage
>> db_sync]: Triggered 'refresh' from 32 events
>> Notice: /Stage[main]/Keystone/Exec[keystone-manage pki_setup]:
>> Triggered 'refresh' from 31 events
>> Notice: /Stage[main]/Keystone::Service/Service[keystone]/ensure:
>> ensure changed 'stopped' to 'running'
>> Error:
>> /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]:
>> Could not evaluate: Execution of '/usr/bin/keystone --os-endpoint
>> http://127.0.0.1:35357/v2.0/ service-list' returned 1: Service
>> Unavailable (HTTP 503)
>> Error:
>> /Stage[main]/Ceilometer::Keystone::Auth/Keystone_service[ceilometer]:
>> Could not evaluate: Execution of '/usr/bin/keystone --os-endpoint
>> http://127.0.0.1:35357/v2.0/ service-list' returned 1: Service
>> Unavailable (HTTP 503)
>> Error: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]:
>> Could not evaluate: Execution of '/usr/bin/keystone --os-endpoint
>> http://127.0.0.1:35357/v2.0/ tenant-list' returned 1: Service
>> Unavailable (HTTP 503)
>> (from here down it's the same error messages)
>> ------------------
>>
>> Here is keystone.log, no errors, only info and warning messages:
>> -------------------
>> 2014-11-07 10:15:31.995 30006 INFO
>> keystone.openstack.common.service [-] Starting 16 workers
>> 2014-11-07 10:15:31.995 30029 INFO eventlet.wsgi.server [-]
>> (30029) wsgi starting up on http://0.0.0.0:35357/
>> 2014-11-07 10:15:31.997 30006 INFO
>> keystone.openstack.common.service [-] Started child 30030
>> [...]
>> 2014-11-07 10:16:01.881 30494 WARNING
>> keystone.openstack.common.versionutils [-] Deprecated:
>> keystone.token.backends.sql.Token is deprecated as of Juno in
>> favor of keystone.token.persistence.backends.sql.Token and may be
>> removed in Kilo.
>> 2014-11-07 10:16:01.904 30494 INFO
>> keystone.token.persistence.backends.sql [-] Token expiration batch
>> size: 1000
>> 2014-11-07 10:16:01.908 30494 INFO
>> keystone.token.persistence.backends.sql [-] Total expired tokens
>> removed: 0
>> -------------------
>>
>> Has anyone had this problem?
>>
>> Thanks in advance.
>>
>> Cheers,
>> David
>>
>>
>>
>>
>>
>> _______________________________________________
>> Rdo-list mailing list
>> Rdo-list at redhat.com <mailto:Rdo-list at redhat.com>
>> https://www.redhat.com/mailman/listinfo/rdo-list
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20141107/23b8a7cb/attachment.html>
More information about the dev
mailing list