cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9716) baremetal:rvr:vm deployment gets stuck in starting state (waiting for notification)
Date Wed, 01 Mar 2017 05:07:45 GMT

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

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

Github user priyankparihar commented on a diff in the pull request:

    https://github.com/apache/cloudstack/pull/1877#discussion_r103611552
  
    --- Diff: systemvm/patches/debian/config/etc/rc.local ---
    @@ -42,11 +42,12 @@ then
        echo 1000000 > /proc/sys/net/nf_conntrack_max
     fi
     
    -if [ "$router" != "" ]
    -then
    -    python /opt/cloud/bin/baremetal-vr.py &
    +
    +if [ "$router" != "" ]; then
    +  python /opt/cloud/bin/baremetal-vr.py &
    --- End diff --
    
    @rashmidixit what is the purpose of introducing this change ?


> baremetal:rvr:vm deployment gets stuck in starting state (waiting for notification)
> -----------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9716
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9716
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Baremetal
>    Affects Versions: 4.5.0, 4.6.0, 4.7.0, 4.8.0, 4.9.0
>            Reporter: Rashmi Dixit
>            Assignee: Rashmi Dixit
>            Priority: Critical
>             Fix For: 4.9.1.0
>
>
> In normal network, vm deployment is successful (got notification properly). When we change
existing the network offering to rvr for the baremetal network then vm deployment gets stuck
in starting state(it has created 2 router and oxe booted properly but still waiting for notification)
> 1.create baremetal network
> 2.deploy a vm with above network.
> 3.destroy the vm
> 4.create another network offering based on RVR+barmetal
> 5.change network offering from normal to rvr barmetal 
> 6. deploy a vm
> actual results:
> vm deployement stuck in starting state(it has created 2 router both master and backup
and vm got pxe booted properly but CS still waiting for notification due to that vm state
still showing in starting state)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message