Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3498B200C38 for ; Wed, 1 Mar 2017 04:54:49 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 332F7160B7E; Wed, 1 Mar 2017 03:54:49 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 7AD79160B7C for ; Wed, 1 Mar 2017 04:54:48 +0100 (CET) Received: (qmail 7203 invoked by uid 500); 1 Mar 2017 03:54:47 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 7194 invoked by uid 500); 1 Mar 2017 03:54:47 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 7191 invoked by uid 99); 1 Mar 2017 03:54:47 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Mar 2017 03:54:47 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1C01EC6AB9 for ; Wed, 1 Mar 2017 03:54:47 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.451 X-Spam-Level: * X-Spam-Status: No, score=1.451 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id X_hMH-1hnuzi for ; Wed, 1 Mar 2017 03:54:46 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3E3305F23A for ; Wed, 1 Mar 2017 03:54:46 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B13D9E060F for ; Wed, 1 Mar 2017 03:54:45 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4D7102415C for ; Wed, 1 Mar 2017 03:54:45 +0000 (UTC) Date: Wed, 1 Mar 2017 03:54:45 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 01 Mar 2017 03:54:49 -0000 [ https://issues.apache.org/jira/browse/CLOUDSTACK-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889455#comment-15889455 ] ASF GitHub Bot commented on CLOUDSTACK-9716: -------------------------------------------- Github user rashmidixit commented on the issue: https://github.com/apache/cloudstack/pull/1877 @harikrishna-patnala, @sadhugit Can you please review? > 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)