Comment 16 for bug 1714150

Revision history for this message
Sandip Dey (sandipd) wrote :

Build:vcenter o16.04 4.0.1.0-52

The bug is not completely fixed.Wrong entry in /etc/hosts still causing the issue

Hi Sachin

Looks like its part of of preconfig. Same thing is done for ubuntu14.04 ,but this issue seems to not there.

Let me know if I need to raise a new bug or update the existing bug.

Regards
Sandip

oot@nodei27:/var/log/contrail# grep -r 'hosts' *
install_logs/install_2017_09_23__09_33_22.log:Enabling conf other-vhosts-access-log.
install_logs/install_2017_09_23__09_33_22.log:Updating /etc/hosts.allow, adding "sendmail: all".
install_logs/install_2017_09_23__09_33_22.log:Please edit /etc/hosts.allow and check the rules location to
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:40:11,055: preconfig.py:228:exec_cmd: INFO] [10.204.217.139]: grep puppet /etc/hosts | grep -v "^[ ]*#"
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:40:11,055: preconfig.py:229:exec_cmd: DEBUG] [10.204.217.139]: grep puppet /etc/hosts | grep -v "^[ ]*#" && echo 001902803704605506407308209100
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:40:11,126: preconfig.py:228:exec_cmd: INFO] [10.204.217.139]: sed -i 's/10.204.217.158 puppet/10.204.217.139 puppet/g' /etc/hosts
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:40:11,127: preconfig.py:229:exec_cmd: DEBUG] [10.204.217.139]: sed -i 's/10.204.217.158 puppet/10.204.217.139 puppet/g' /etc/hosts && echo 001902803704605506407308209100
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:40:11,221: preconfig.py:228:exec_cmd: INFO] [10.204.217.139]: grep nodei27 /etc/hosts | grep -v "^[ ]*#"
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:40:11,222: preconfig.py:229:exec_cmd: DEBUG] [10.204.217.139]: grep nodei27 /etc/hosts | grep -v "^[ ]*#" && echo 001902803704605506407308209100
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:44:17,585: preconfig.py:228:exec_cmd: INFO] [10.204.217.144]: grep puppet /etc/hosts | grep -v "^[ ]*#"
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:44:17,586: preconfig.py:229:exec_cmd: DEBUG] [10.204.217.144]: grep puppet /etc/hosts | grep -v "^[ ]*#" && echo 001902803704605506407308209100
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:44:17,658: preconfig.py:228:exec_cmd: INFO] [10.204.217.144]: sed -i 's/10.204.217.158 puppet/10.204.217.139 puppet/g' /etc/hosts
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:44:17,659: preconfig.py:229:exec_cmd: DEBUG] [10.204.217.144]: sed -i 's/10.204.217.158 puppet/10.204.217.139 puppet/g' /etc/hosts && echo 001902803704605506407308209100
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:44:17,817: preconfig.py:228:exec_cmd: INFO] [10.204.217.144]: grep nodei32 /etc/hosts | grep -v "^[ ]*#"
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:44:17,817: preconfig.py:229:exec_cmd: DEBUG] [10.204.217.144]: grep nodei32 /etc/hosts | grep -v "^[ ]*#" && echo 001902803704605506407308209100
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:50:26,379: preconfig.py:228:exec_cmd: INFO] [10.204.217.140]: grep puppet /etc/hosts | grep -v "^[ ]*#"
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:50:26,379: preconfig.py:229:exec_cmd: DEBUG] [10.204.217.140]: grep puppet /etc/hosts | grep -v "^[ ]*#" && echo 001902803704605506407308209100
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:50:26,427: preconfig.py:228:exec_cmd: INFO] [10.204.217.140]: sed -i 's/10.204.217.158 puppet/10.204.217.139 puppet/g' /etc/hosts
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:50:26,427: preconfig.py:229:exec_cmd: DEBUG] [10.204.217.140]: sed -i 's/10.204.217.158 puppet/10.204.217.139 puppet/g' /etc/hosts && echo 001902803704605506407308209100
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:50:26,563: preconfig.py:228:exec_cmd: INFO] [10.204.217.140]: grep nodei28 /etc/hosts | grep -v "^[ ]*#"
sm_provisioning/2017_09_23__09_33_22/preconfig.log:[2017-09-23 09:50:26,564: preconfig.py:229:exec_cmd: DEBUG] [10.204.217.140]: grep nodei28 /etc/hosts | grep -v "^[ ]*#" && echo 001902803704605506407308209100

Hi Abhay

Wrong entry in /etc/hosts caused wrong rabbitmq config.This is a smlite provisioned setup after re-image.

Regards
Sandip

# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
127.0.0.1 localhost.englab.juniper.net localhost
10.204.217.139 nodei27.englab.juniper.net nodei27
10.204.217.139 puppet >>>>>>>>>>>
127.0.0.1 nodei27
10.204.217.139 nodei27
10.204.217.144 nodei32
10.204.217.140 nodei28
10.204.217.204 nodei35-compute-vm
10.204.217.229 nodei36-compute-vm

From: Sandip Dey <email address hidden>
Date: Sunday, September 24, 2017 at 8:15 AM
To: Ignatious Johnson <email address hidden>, Jeba Paulaiyan <email address hidden>, Sachchidanand Vaidya <email address hidden>, Yuvaraja Mariappan <email address hidden>
Cc: Sudheendra Rao <email address hidden>, Sachin Bansal <email address hidden>
Subject: Re: Routing instance not getting created in vcenter setup

Hi Ignatius

I started with re-imaging the setup.What could be the reason that the /etc/hosts went wrong.
I had not done anything manually.Its smlite run provisioning.

Regards
Sandip

From: Ignatious Johnson <email address hidden>
Date: Sunday, September 24, 2017 at 8:12 AM
To: Sandip Dey <email address hidden>, Jeba Paulaiyan <email address hidden>, Sachchidanand Vaidya <email address hidden>, Yuvaraja Mariappan <email address hidden>
Cc: Sudheendra Rao <email address hidden>, Sachin Bansal <email address hidden>
Subject: Re: Routing instance not getting created in vcenter setup

I see that the rabbitmq configuration is incorrect as below.

{cluster_nodes, {['rabbit@puppet','rabbit@nodei32','rabbit@nodei28'], disc}}

This is due to the reason that the /etc/hosts has a wrong entry for nodei27.

Thanks,
Ignatious

From: Sandip Dey <email address hidden>
Date: Saturday, September 23, 2017 at 2:33 AM
To: Jeba Paulaiyan <email address hidden>, Sachchidanand Vaidya <email address hidden>, Yuvaraja Mariappan <email address hidden>, Ignatious Johnson <email address hidden>
Cc: Sudheendra Rao <email address hidden>
Subject: Re: Routing instance not getting created in vcenter setup

Logs
===

root@nodei28:~# docker exec -it controller bash
root@nodei28(controller):/# rabbitmqctl cluster_status
Cluster status of node rabbit@nodei28 ...
[{nodes,[{disc,[rabbit@nodei28,rabbit@nodei32]}]},
 {running_nodes,[rabbit@nodei32,rabbit@nodei28]},
 {cluster_name,<<"<email address hidden>">>},
 {partitions,[]}]

root@nodei27(controller):/# rabbitmqctl cluster_status
Cluster status of node rabbit@nodei27 ...
[{nodes,[{disc,[rabbit@nodei27]}]},
 {running_nodes,[rabbit@nodei27]},
 {cluster_name,<<"<email address hidden>">>},
 {partitions,[]}]

From: Sandip Dey <email address hidden>
Date: Saturday, September 23, 2017 at 3:01 PM
To: Jeba Paulaiyan <email address hidden>, Sachchidanand Vaidya <email address hidden>, Yuvaraja Mariappan <email address hidden>, Ignatious Johnson <email address hidden>
Cc: Sudheendra Rao <email address hidden>
Subject: Re: Routing instance not getting created in vcenter setup

Hi ignatious

I still see the problem in 16.04 4.0.1.0-52 vcenter only setup.

Verified that your commit for this bug https://bugs.launchpad.net/juniperopenstack/+bug/1714150 present in internal-ansible code.

Please take a look at my setup.

 env.roledefs = {
        'all': [host1, host2,host3, host4, host5],
        'cfgm': [host1, host2,host3],
        'webui': [host1, host2,host3],
        'control': [host1, host2,host3],
        'collector': [host1,host2,host3],
        'database': [host1,host2,host3],
        'compute': [host4, host5],
        'build': [host_build]
    }
env.hostnames = {
    'all': ['nodei27', 'nodei28' ,'nodei32', 'nodei35-compute-vm', 'nodei36-compute-vm']
}

Regards
Sandip