On Wed, Apr 29, 2015 at 07:11:12PM +0200, Arash Kaffamanesh wrote:
Hi,
I tried to install rdo-manager (virtual environment) and was able to ssh
into the
instack vm and run:
[stack@instack ~]$ instack-install-undercloud
The installation aborts with:
........
Notice:
/Stage[main]/Nova::Cert/Nova::Generic_service[cert]/Service[nova-cert]:
Triggered 'refresh' from 3 events
Notice:
/Stage[main]/Neutron::Agents::Ml2::Ovs/Service[neutron-ovs-agent-service]/ensure:
ensure changed 'stopped' to 'running'
Notice: Finished catalog run in 625.05 seconds
+ rc=6
+ set -e
+ echo 'puppet apply exited with exit code 6'
puppet apply exited with exit code 6
+ '[' 6 '!=' 2 -a 6 '!=' 0 ']'
+ exit 6
[stack@instack ~]$ [2015-04-29 16:43:38,404] (os-refresh-config) [ERROR]
during configure phase. [Command '['dib-run-parts',
'/usr/libexec/os-refresh-config/configure.d']' returned non-zero exit
status 6]
[2015-04-29 16:43:38,405] (os-refresh-config) [ERROR] Aborting...
^C
The red warning and errors during the instack-install-undercloud run are
attached.
Any ideas?
It looks the rabbitmq puppet module failed to download rabbitmqadmin from the
local rabbitmq server. The curl command exited with code 7, which means:
7 Failed to connect to host.
Can you look up ealier in the log (~/.instack/install-undercloud.log) to see if
there were any problems starting rabbitmq-server? Also check the logs under
/var/log/rabbitmq and:
sudo systemctl status rabbitmq-server
There were some problems reported earlier last week about rabbitmq failing to
start and it seemed related to not having a fqdn hostname set. I haven't had a
chance to dig into that deeper yet, but it could be related to what you're
seeing here.
Thanks!
Arash
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
--
-- James Slagle
--