Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 29 Dec 2016 11:27:58 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13031077.1483006903000.612896.1483010878369@Atlassian.JIRA>
In-Reply-To: <JIRA.13031077.1483006903000@Atlassian.JIRA>
References: <JIRA.13031077.1483006903000@Atlassian.JIRA> <JIRA.13031077.1483006903540@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9716) baremetal:rvr:vm deployment
 gets stuck in starting state (waiting for notification)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 29 Dec 2016 11:28:00 -0000


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

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

GitHub user rashmidixit opened a pull request:

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

    Change of network to rvr for baremetal caused vm deployment to get stuck

    Refer to [CLOUDSTACK-9716](https://issues.apache.org/jira/browse/CLOUDSTACK-9716) for more details

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

    $ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9716

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

    https://github.com/apache/cloudstack/pull/1877.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 #1877
    
----
commit 855080745d1d4f43b105852fc2d213c39a967786
Author: Rashmi Dixit <rashmi_dixit@persistent.co.in>
Date:   2016-04-05T10:37:31Z

    CLOUDSTACK-9716 - bareemtal:rvr:vm deployment state stuck in stating state(waiting for notification)
    Reviewed-by Harikrishna P
    
    Conflicts:
    	systemvm/patches/debian/config/etc/rc.local

commit b6bbaee8bec7a378f2541ffdce20e1b4b41ad54c
Author: rashmidixit <rashmi_dixit@persistent.co.in>
Date:   2016-07-06T04:56:21Z

    CLOUDSTACK-9716 bareemtal:rvr:vm deployement state stuck in starting state(waiting for notification)
    Reviewed-by Hari P

----


> 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.4#6332)