agent node unreachable after ansible provisioning

Bug #1667583 reported by Vedamurthy Joshi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
Fix Committed
Critical
Nitish Krishna Kaveri

Bug Description

R4.0 Build 3041

On a setup with 2 compute nodes, after ansible provisioning, both the compute nodes had become unreachable.
The default gateway was missing on the node. (vhost0 was up)
I noticed that inside the container, /etc/network/interfaces referred to interfaces.d/*, but nothing was in interfaces.d/

While the nodes were reachable once i manually configured the default route, after reboot , the agent containers were not started at all (vrouter module was not loaded)

Last few lines of provisioning log :

TASK [openstack/compute : Create /etc/contrail/ctrl-details] *******************
skipping: [10.204.217.197]
skipping: [10.204.217.198]

TASK [openstack/compute : Configure nova] **************************************
skipping: [10.204.217.197]
skipping: [10.204.217.198]

TASK [openstack/compute : Configure neutron credentials in nova.conf to fix configuration problem by above command] ***
skipping: [10.204.217.197] => (item={'key': u'project_name', 'value': u'services'})
skipping: [10.204.217.197] => (item={'key': u'password', 'value': u'admin'})
skipping: [10.204.217.198] => (item={'key': u'project_name', 'value': u'services'})
skipping: [10.204.217.197] => (item={'key': u'auth_url', 'value': u'http://10.204.217.194:35357/'})
skipping: [10.204.217.197] => (item={'key': u'admin_tenant_name', 'value': u'services'})
skipping: [10.204.217.198] => (item={'key': u'password', 'value': u'admin'})
skipping: [10.204.217.198] => (item={'key': u'auth_url', 'value': u'http://10.204.217.194:35357/'})
skipping: [10.204.217.198] => (item={'key': u'admin_tenant_name', 'value': u'services'})

TASK [openstack/compute : Configure oslo rabbit hosts in nova.conf to fix configuration problem by compute-server-setup] ***
skipping: [10.204.217.197] => (item={'key': u'rabbit_hosts', 'value': u'10.204.217.194:5672'})
skipping: [10.204.217.198] => (item={'key': u'rabbit_hosts', 'value': u'10.204.217.194:5672'})

TASK [openstack/compute : Copy vrouter-port-control from agent container to compute] ***
skipping: [10.204.217.197]
skipping: [10.204.217.198]

TASK [openstack/compute : Configure qemu] **************************************
skipping: [10.204.217.197]
skipping: [10.204.217.198]

PLAY RECAP *********************************************************************
10.204.217.194 : ok=50 changed=24 unreachable=0 failed=0
10.204.217.197 : ok=57 changed=26 unreachable=0 failed=0
10.204.217.198 : ok=57 changed=24 unreachable=0 failed=0

[root@ansible-runner playbooks]#

Changed in juniperopenstack:
milestone: none → r4.0
Changed in juniperopenstack:
assignee: Ramprakash R (ramprakash) → Nitish Krishna Kaveri (nitishk)
Revision history for this message
Harish Kumar (hkumarmk) wrote : Re: [Bug 1667583] Re: agent node unreachable after ansible provisioning
Download full text (3.5 KiB)

If you use agent container, then this behavior is fixed after 3041 official
build triggered with PR https://github.com/Juniper/contrail-ansible/pull/346

On Thu, Feb 23, 2017 at 11:47 PM, Ramprakash R <email address hidden>
wrote:

> ** Changed in: juniperopenstack
> Assignee: Ramprakash R (ramprakash) => Nitish Krishna Kaveri (nitishk)
>
> --
> You received this bug notification because you are a member of Contrail
> Systems engineering, which is subscribed to Juniper Openstack.
> https://bugs.launchpad.net/bugs/1667583
>
> Title:
> agent node unreachable after ansible provisioning
>
> Status in Juniper Openstack:
> New
>
> Bug description:
> R4.0 Build 3041
>
> On a setup with 2 compute nodes, after ansible provisioning, both the
> compute nodes had become unreachable.
> The default gateway was missing on the node. (vhost0 was up)
> I noticed that inside the container, /etc/network/interfaces referred to
> interfaces.d/*, but nothing was in interfaces.d/
>
> While the nodes were reachable once i manually configured the default
> route, after reboot , the agent containers were not started at all
> (vrouter module was not loaded)
>
> Last few lines of provisioning log :
>
>
> TASK [openstack/compute : Create /etc/contrail/ctrl-details]
> *******************
> skipping: [10.204.217.197]
> skipping: [10.204.217.198]
>
> TASK [openstack/compute : Configure nova] ******************************
> ********
> skipping: [10.204.217.197]
> skipping: [10.204.217.198]
>
> TASK [openstack/compute : Configure neutron credentials in nova.conf to
> fix configuration problem by above command] ***
> skipping: [10.204.217.197] => (item={'key': u'project_name', 'value':
> u'services'})
> skipping: [10.204.217.197] => (item={'key': u'password', 'value':
> u'admin'})
> skipping: [10.204.217.198] => (item={'key': u'project_name', 'value':
> u'services'})
> skipping: [10.204.217.197] => (item={'key': u'auth_url', 'value': u'
> http://10.204.217.194:35357/'})
> skipping: [10.204.217.197] => (item={'key': u'admin_tenant_name',
> 'value': u'services'})
> skipping: [10.204.217.198] => (item={'key': u'password', 'value':
> u'admin'})
> skipping: [10.204.217.198] => (item={'key': u'auth_url', 'value': u'
> http://10.204.217.194:35357/'})
> skipping: [10.204.217.198] => (item={'key': u'admin_tenant_name',
> 'value': u'services'})
>
> TASK [openstack/compute : Configure oslo rabbit hosts in nova.conf to
> fix configuration problem by compute-server-setup] ***
> skipping: [10.204.217.197] => (item={'key': u'rabbit_hosts', 'value':
> u'10.204.217.194:5672'})
> skipping: [10.204.217.198] => (item={'key': u'rabbit_hosts', 'value':
> u'10.204.217.194:5672'})
>
> TASK [openstack/compute : Copy vrouter-port-control from agent container
> to compute] ***
> skipping: [10.204.217.197]
> skipping: [10.204.217.198]
>
> TASK [openstack/compute : Configure qemu] ******************************
> ********
> skipping: [10.204.217.197]
> skipping: [10.204.217.198]
>
> PLAY RECAP ************************************************************
> *********
> 10.204.217.194 : ok=50 changed=24 unreach...

Read more...

Changed in juniperopenstack:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.