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 8AEE7200D57 for ; Mon, 11 Dec 2017 17:20:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 897BD160C13; Mon, 11 Dec 2017 16:20:05 +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 D03D8160C10 for ; Mon, 11 Dec 2017 17:20:04 +0100 (CET) Received: (qmail 65834 invoked by uid 500); 11 Dec 2017 16:20:04 -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 65792 invoked by uid 500); 11 Dec 2017 16:20:03 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 65783 invoked by uid 99); 11 Dec 2017 16:20:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Dec 2017 16:20:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 8BA9A1A0875 for ; Mon, 11 Dec 2017 16:20:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Xs2E9VJzTyf9 for ; Mon, 11 Dec 2017 16:20:01 +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 5D3185F5D2 for ; Mon, 11 Dec 2017 16:20:01 +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 C8FECE0635 for ; Mon, 11 Dec 2017 16:20:00 +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 5ADB7212FA for ; Mon, 11 Dec 2017 16:20:00 +0000 (UTC) Date: Mon, 11 Dec 2017 16:20:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-10157) Wrong notification while migration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 11 Dec 2017 16:20:05 -0000 [ https://issues.apache.org/jira/browse/CLOUDSTACK-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286120#comment-16286120 ] ASF GitHub Bot commented on CLOUDSTACK-10157: --------------------------------------------- rhtyd commented on issue #2337: CLOUDSTACK-10157: Wrong notification while migration. URL: https://github.com/apache/cloudstack/pull/2337#issuecomment-350774179 LGTM, simple NPE check. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org > Wrong notification while migration > ---------------------------------- > > Key: CLOUDSTACK-10157 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10157 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: API > Affects Versions: 4.11.0.0 > Reporter: Nitin Kumar Maharana > Labels: GPU > Fix For: 4.11.0.0 > > > RETRO STEPS: > 1. Had three hosts in one cluster, two of them with GPU cards NVIDIA GRID K1 and K2 and one normal host. > 2. Deployed a VM with K2 vgpu. > 3. Stopped the VM and tried starting it on a different host. (Expected it to fail as there is only one host supporting that particular vgpu type) > 4. The log showed it as failed operation, VM remained in the stopped state, yet the notification showed "Start Instance" as successful and no error message was displayed. -- This message was sent by Atlassian JIRA (v6.4.14#64029)