Ask Your Question
0

MIrantis 8 fuel node fail to deploy

asked 2016-06-21 09:31:21 -0600

Gabriel Peral gravatar image

updated 2016-06-21 10:50:36 -0600

Hello! I've been trying to deploy fuel Mirantis 8.0 for several days but i always have the same mistake, I deploy from the ISO of the web page and I only set up the fuelmenu changing the eth0 configuration (in order to get access to the fuel web UI through my own network) and the eth1 (for PXE), I also change the hostname and the ntp and dns server, the problem comes when the deployment finish, if I type the dockerctl list -l command I have this output:

root@fuel ~]# dockerctl list -l
Name Image Status Full container name
nginx fuel/nginx_8.0              Stopped          fuel-core-8.0-nginx
rabbitmq fuel/rabbitmq_8.0    Stopped           fuel-core-8.0-rabbitmq
astute fuel/astute_8.0           Not created      fuel-core-8.0-astute
rsync fuel/rsync_8.0             Not created      fuel-core-8.0-rsync
keystone fuel/keystone_8.0   Not created     fuel-core-8.0-keystone
postgres fuel/postgres_8.0    Stopped          fuel-core-8.0-postgres
rsyslog fuel/rsyslog_8.0        Not created     fuel-core-8.0-rsyslog
nailgun fuel/nailgun_8.0         Not created    fuel-core-8.0-nailgun
cobbler fuel/cobbler_8.0         Not created      fuel-core-8.0-cobbler
ostf fuel/ostf_8.0                    Not created     fuel-core-8.0-ostf
mcollective fuel/mcollective_8.0 Not created   fuel-core-8.0-mcollective

It seems that the deploy doesn't deploy the containers in the right way, I've also tried to run the bootstrap_admin_node.sh command but the output shows me some warnings:

Notice: /Stage[main]/Docker::Systemd/Docker::Systemd::Config[rabbitmq]/Service[docker-rabbitmq]: Dependency Exec[container0check] has failures: true
Warning: /Stage[main]/Docker::Systemd/Docker::Systemd::Config[rabbitmq]/Service[docker-rabbitmq]: Skipping because of failed dependencies
Notice: /Stage[main]/Docker::Systemd/Docker::Systemd::Config[mcollective]/Service[docker-mcollective]: Dependency Exec[container0check] has failures: true
Warning: /Stage[main]/Docker::Systemd/Docker::Systemd::Config[mcollective]/Service[docker-mcollective]: Skipping because of failed dependencies
Notice: /Stage[main]/Docker::Systemd/Docker::Systemd::Config[keystone]/Service[docker-keystone]: Dependency Exec[container0check] has failures: true
Warning: /Stage[main]/Docker::Systemd/Docker::Systemd::Config[keystone]/Service[docker-keystone]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Exec[sync_deployment_tasks]: Dependency Exec[container0check] has failures: true
Warning: /Stage[main]/Main/Exec[sync_deployment_tasks]: Skipping because of failed dependencies
Debug: Finishing transaction 32958420
Debug: Storing state
Debug: Stored state in 0.13 seconds
Notice: Finished catalog run in 412.93 seconds
Debug: Using settings: adding file resource 'rrddir': 'File[/var/lib/puppet/rrd]{:path=>"/var/lib/puppet/rrd", :mode=>"750", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Finishing transaction 33997900
Debug: Received report to process from fuel.domain.tld.localdomain.es
Debug: Evicting cache entry for environment 'production'
Debug: Caching environment 'production' (ttl = 0 sec)
Debug: Processing report from fuel.domain.tld.localdomain.es with processor Puppet::Reports::Store
ERROR: Fuel node deployment FAILED! Check /var/log/puppet/bootstrap_admin_node.log for details

I've only pasted a few lines, but there are a lot of warnings, the problems seems to be in the way that Fuel deploy the docker containers,

Any suggestions, I've been stacked in this step for days and I am not able to deploy the OpenStack environment if I can ... (more)

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2016-06-22 02:41:31 -0600

Gabriel Peral gravatar image

updated 2016-06-22 02:42:15 -0600

hkominos --> Sorry, I thought I put the environment, I am "trying" to deploy an OpenStack environment using Mirantis 8 over three vms in a vwmware enviroment, I mean, it is not an Openstack + ESXi environment, it's over kvm (because Mirantis will deploy centos and ubuntu) but the vms are created in vmware. I use the manual installation way, and the problem comes with the fuel node, which only need to configure the interfaces for PXE and web UI, (besides DNS server, admin password, etc). I read the manual and saw several tutorials and I think I'm doing right, the problem is with the way that Miranits deploy the containers.

I destroyed the cointainers and started again, but this appears as output:

checking with command "shell_container postgres PGPASSWORD=T1mk8j6s /usr/bin/psql -h 10.20.40.153 -U "nailgun" "nailgun" -c '\copyright' 2>&1 1>/dev/null"
psql: could not connect to server: Connection refused
    Is the server running on host "10.20.40.153" and accepting
    TCP/IP connections on port 5432?
try number 1
return code is 2
psql: could not connect to server: Connection refused
    Is the server running on host "10.20.40.153" and accepting
    TCP/IP connections on port 5432?
try number 2
return code is 2
checking with command "! shell_container postgres pgrep puppet"
postgres is ready.
feb90025749111fee846f156a0b02f55197be5c30c82f2148fadd73d650238a6
DEBU[0000] End of CmdRun(), Waiting for hijack to finish. 
checking container rabbitmq
checking with command "curl -f -L -i  -u "naily:iyb661K9" http://10.20.40.153:15672/api/nodes  1>/dev/null 2>&1"
try number 1
return code is 7
try number 2
return code is 7
try number 3
return code is 7
try number 4

I reach the 10.20.40.153 5432 trough telent and the port is LISTEN on all addresses, and the number of tries is increasing.

Could be a bug on the Mirantis image??

edit flag offensive delete link more

Comments

Update: I tried to start the docker containers one by one and it seems that it worked, all the containers are up and running, and now i can reach the web UI. Thank all of you for your help. :)

Gabriel Peral gravatar imageGabriel Peral ( 2016-06-22 03:27:09 -0600 )edit
0

answered 2016-06-21 11:10:49 -0600

hkominos gravatar image

1) you are not specifying if you are deploying on local host with the scripts or its real infrastructure. that is really important. 2) I am assuming that you have already read and understood all the manuals.so Try destroying all traces of the containers and rebuilding them and lets see what happens https://docs.mirantis.com/openstack/f...

edit flag offensive delete link more

Comments

hkominos >> Though installing properly as per mirantis docx via script or manual build, it throwing same error, like service failed to start, i have restarted manually many times, but no luck. if rebuild also will throw same problem

Maestropandy gravatar imageMaestropandy ( 2016-06-22 01:00:29 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-06-21 09:31:21 -0600

Seen: 924 times

Last updated: Jun 22 '16