[
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14645688#comment-14645688
]
ASF GitHub Bot commented on CLOUDSTACK-8668:
--------------------------------------------
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/627#issuecomment-125878438
Nice catch, @kishankavala !
I checked the history of the file and found out that the changes for VPC
router and normal router were added in the commit
13b7ca1b3fc3d3c44d677307a59a5205b6c881bb
The extra iff you added, for the dhcpsrvr case, will do it.
Do you want to create a new PR for that one? I can test it as well. Since
it's touching only dhcpsrvr (used for basic zones) I'm not expecting problemas
with VPC routers or other routers used for advanced zones.
Cheers,
Wilder
> 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: Kishan Kavala
> Priority: Blocker
> Fix For: 4.6.0
>
>
> 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)
