[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644165#comment-14644165
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8668:
--------------------------------------------

GitHub user kishankavala opened a pull request:

    https://github.com/apache/cloudstack/pull/627

    CLOUDSTACK-8668: VR type in shared network is dhcpsrvr. Ips are being 
removed due to this issue

    - VR IP config is loaded from /var/cache/cloud/cmdline
    - For shared network VR type is "dhcpserver" in /var/cache/cloud/cmdline
    - after VR refactor, merge.py is considering VR types "router" and 
"vpcrouter" only
    -  Fixed by adding dhcpserver VR type
    
    Testing:
    - VR successfully started on shared network. All IPs are configured 
properly.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kishankavala/cloudstack CLOUDSTACK-8668

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/627.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #627
    
----
commit 50a6fa02dabd7df7a78a0541df6e575129e14265
Author: Kishan Kavala <[email protected]>
Date:   2015-07-28T09:45:41Z

    VR type in shared network is dhcpsrvr. Ips are being removed due to this 
issue

----


> 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)

Reply via email to