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 B0FA4200C2C for ; Fri, 3 Mar 2017 10:45:55 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id AF9ED160B6D; Fri, 3 Mar 2017 09:45:55 +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 0DA59160B57 for ; Fri, 3 Mar 2017 10:45:54 +0100 (CET) Received: (qmail 26255 invoked by uid 500); 3 Mar 2017 09:45:54 -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 26246 invoked by uid 500); 3 Mar 2017 09:45:54 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 26243 invoked by uid 99); 3 Mar 2017 09:45:54 -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; Fri, 03 Mar 2017 09:45:54 +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 C8778C2283 for ; Fri, 3 Mar 2017 09:45:53 +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-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 4H71cP6JTv1g for ; Fri, 3 Mar 2017 09:45:53 +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 9799C5FAE0 for ; Fri, 3 Mar 2017 09:45:47 +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 99885E0054 for ; Fri, 3 Mar 2017 09:45: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 572C021D62 for ; Fri, 3 Mar 2017 09:45:45 +0000 (UTC) Date: Fri, 3 Mar 2017 09:45:45 +0000 (UTC) From: "Priyank Parihar (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-9605) Disabled Host Keeps Being up status after unmanging cluster MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 03 Mar 2017 09:45:55 -0000 [ https://issues.apache.org/jira/browse/CLOUDSTACK-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Priyank Parihar updated CLOUDSTACK-9605: ---------------------------------------- Description: Steps to reproduce are as follow --> Disabled Host from UI. Unmanaged the cluster which the host was in. Still host appears in UP state in UI. Ideally Hosts should appear in "disconnected" state. was: Steps to reproduce are as follow --> Disabled Host from UI. Unmanaged the cluster which the host was in. Still host appears in UP state in UI. Ideally Host should not be shown in UP state, after disabling it and unmanaging the cluster. > Disabled Host Keeps Being up status after unmanging cluster > ----------------------------------------------------------- > > Key: CLOUDSTACK-9605 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9605 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Environment: XenServer Version : 6.2 > Reporter: Priyank Parihar > Assignee: Priyank Parihar > > Steps to reproduce are as follow --> > Disabled Host from UI. > Unmanaged the cluster which the host was in. > Still host appears in UP state in UI. > Ideally Hosts should appear in "disconnected" state. -- This message was sent by Atlassian JIRA (v6.3.15#6346)