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 EEA1A200C22 for ; Tue, 21 Feb 2017 08:18:53 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id ED5DB160B3E; Tue, 21 Feb 2017 07:18:53 +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 42BC8160B68 for ; Tue, 21 Feb 2017 08:18:53 +0100 (CET) Received: (qmail 51651 invoked by uid 500); 21 Feb 2017 07:18:49 -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 51642 invoked by uid 500); 21 Feb 2017 07:18:49 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 51639 invoked by uid 99); 21 Feb 2017 07:18:49 -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; Tue, 21 Feb 2017 07:18:49 +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 03698C1AB6 for ; Tue, 21 Feb 2017 07:18:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.799 X-Spam-Level: * X-Spam-Status: No, score=1.799 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id GjqCJPRi-FSu for ; Tue, 21 Feb 2017 07:18:48 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 263C55F2C5 for ; Tue, 21 Feb 2017 07:18:48 +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 CB54BE091A for ; Tue, 21 Feb 2017 07:18:44 +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 34EB02412B for ; Tue, 21 Feb 2017 07:18:44 +0000 (UTC) Date: Tue, 21 Feb 2017 07:18:44 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-9610) Disabled Host Keeps Being up status after unmanaging cluster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 21 Feb 2017 07:18:54 -0000 [ https://issues.apache.org/jira/browse/CLOUDSTACK-9610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875500#comment-15875500 ] ASF GitHub Bot commented on CLOUDSTACK-9610: -------------------------------------------- Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1779 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. > Disabled Host Keeps Being up status after unmanaging cluster > ------------------------------------------------------------- > > Key: CLOUDSTACK-9610 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9610 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: UI > Reporter: Priyank Parihar > Assignee: Priyank Parihar > > ENVIRONMENT > ===================== > XenServer Version : 6.2 > ISSUE > ================== > Disabled Host Keeps Being 'UP' status after unmanging cluster > Repro. steps followed > ================== > Disabled Host from UI. > Unmanaged the cluster which the host was in. > Still can see the Host showing 'UP' in UI > Expected Behavior > =============== > After disabling the host and un-managing the cluster, the host should appear in "disconnected" state and not UP state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)