[
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kishan Kavala updated CLOUDSTACK-8668:
--------------------------------------
Comment: was deleted
(was: Yes Wilder "VR started successfully ". But port 3922 is not open. Once I
add iptables rule to allow 3922, MS is able to program rules.
I'm looking at CLOUDSTACK-8683, but might take a while for me to find the root
cause.)
> VR does not start in basic zone since ip address are not being configured on
> it
> -------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8668
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.6.0
> Environment: Latest build from ACS master
> Reporter: Sanjeev N
> Assignee: Wilder Rodrigues
> Priority: Blocker
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
