[CLOUDSTACK-8668] VR does not start in basic zone since ip address are not being configured on it

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 4.6.0
• Fix Version/s: 4.6.0
• Component/s: Network Controller
• Security Level: Public (Anyone can view this level - this is the default.)
• Environment: Latest build from ACS master
• Assignee: Kishan
• Reporter: Sanjeev N
• Created: 24/Jul/15 06:33
• Updated: 30/Jul/15 06:07
• Resolved: 28/Jul/15 12:16

Description

VR does not start in basic zone since ip address are not being configured on it

Steps to reproduce:
================
1.Bring up CS in basic zone with xen server cluster
2.Try to deploy one guest vm using default cent os template

Expected Result:
==============
VR should come up as part of vm deployment and vm deployment should be successfull

Actual Result:
============
VR creation failed since the IP addresses not are getting assigned to VR's guest and link local interfaces.

Observations:
===========
1.During vr boot time, cloud-early-config ran successfully and VR console output showed that ping to gateway was successful. However, after VR boot we don't see any ip addresses on the VRs guest and link local ip address.
2. If we run cloud-early-config manually from VR , ip addresses will be assigned and persistent.

Impact:
=====
VM deployments will fail since VR remains in stopped state.