Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 16 Oct 2014 21:51:37 +0000 (UTC)
From: "Jessica Wang (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12748728.1413495740000.281839.1413496297169@Atlassian.JIRA>
In-Reply-To: <JIRA.12748728.1413495740000@Atlassian.JIRA>
References: <JIRA.12748728.1413495740000@Atlassian.JIRA>
 <JIRA.12748728.1413495740203@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-7744) Changing Service Offering
 incorretly shows "Instance Scaled Up" even if offering scaled down
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jessica Wang updated CLOUDSTACK-7744:
-------------------------------------
    Fix Version/s: 4.5.0

> Changing Service Offering incorretly shows "Instance Scaled Up" even if offering scaled down
> --------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7744
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7744
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>            Reporter: Jessica Wang
>            Assignee: Jessica Wang
>             Fix For: 4.5.0
>
>
> 1. Create a VM Instance; then make sure it is powered off.
>  2. View the VM Instance details, then press the "Change Service Offering" button.
>  3. Select a new service offering then press "OK".
> Expected: The notification should be generic, e.g. "Change Service Offering".
>  Actual: The resulting notification shown upon completion is "Instance Scaled Up", even if the new service offering is smaller/weaker than what the VM previously had. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)