R2.0 to R2.1 upgrade: vrouter failed to come up after upgrade
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.1 |
Fix Committed
|
Critical
|
Shweta Naik | |||
Trunk |
Fix Committed
|
Critical
|
Shweta Naik |
Bug Description
I did a upgrade from R2.0 (ubuntu 12.04 icehouse) to R2.10 (build 23). I have multimode setup with 2 computes.
After the vrouter upgrade when the reboot was issued on both the computes, one of the compute failed to come up.
I am not able to do ssh using the mgmt ip. Logged in via the console, contrail-status shows ‘contrail-
From the console I am not able to ping the default Gw . I see in dropstats Discards count increasing.
I tried to restart the discovery service and then restarted the supervisor-vrouter, but didn’t help.
From the upgrade log this is the time stamp when reboot was issued,
2015-02-03 18:18:11:342351: [root@10.84.14.35] Executing task 'compute_reboot'
2015-02-03 18:18:11:537787: [root@10.84.14.36] Executing task ‘compute_reboot'
But in 10.84.14.35 (this is the compute with the issue) in syslog I see vrouter soft reset before this time stamp, at Feb 3, 18:18:08
Also I see some errors in agent log when its trying to add the route.
Upgrade logs are at root@10.
Another compute node in the cluster is up and running. (10.84.14.36)
I had hit this issue some time back also during upgrade(not sure from which release), but when I did reboot from console vrouter came up fine and in rerun I didn’t hit this issue again.
I am hitting this issue intermittently. Could you please take a look, I have the setup in failed state.
summary: |
- R2.0 to R2.1 upgrade: grouter failed to come up after upgrade + R2.0 to R2.1 upgrade: vrouter failed to come up after upgrade |
tags: | added: blocker |
information type: | Proprietary → Public |
From: Anand H Krishnan <email address hidden>
Date: Wednesday, February 4, 2015 at 10:06 PM
To: Shweta Naik <email address hidden>, Praveen K V <email address hidden>, Hari Prasad Killi <email address hidden>
Cc: Ashish Ranjan <email address hidden>, Raj Reddy <email address hidden>, Megh Bhatt <email address hidden>, Rajagopalan Sivaramakrishnan <email address hidden>
Subject: Re: R2.1 vrouter failed to come up after upgrade
Hi,
I just looked into the setup. The default vrf routes have not been populated
and hence vrouter is dropping the packet. Somebody from agent team needs
to look at the problem. I have stopped agent for now and hence direct access
to the box is possible.
Thanks,
Anand