[jira] [Updated] (CLOUDSTACK-5391) Change service offering of a stopped vm and then starting it should check host cpu capability
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-5391: Affects Version/s: 4.3.0 > Change service offering of a stopped vm and then starting it should check > host cpu capability > - > > Key: CLOUDSTACK-5391 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5391 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0, 4.3.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.3.0 > > > Change service offering of a stopped vm and then starting it should check > host cpu capability with the new service offering. > Host has 4 physical CPU cores. > Create a service offering of 5 CPU cores and scaled up existing VM with this > service offering. > Similarly for speed. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (CLOUDSTACK-5391) Change service offering of a stopped vm and then starting it should check host cpu capability
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-5391: Priority: Critical (was: Major) > Change service offering of a stopped vm and then starting it should check > host cpu capability > - > > Key: CLOUDSTACK-5391 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5391 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta >Priority: Critical > Fix For: 4.3.0 > > > Change service offering of a stopped vm and then starting it should check > host cpu capability with the new service offering. > Host has 4 physical CPU cores. > Create a service offering of 5 CPU cores and scaled up existing VM with this > service offering. > Similarly for speed. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-5391) Change service offering of a stopped vm and then starting it should check host cpu capability
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-5391: Description: Change service offering of a stopped vm and then starting it should check host cpu capability with the new service offering. Host has 4 physical CPU cores. Create a service offering of 5 CPU cores and scaled up existing VM with this service offering. Similarly for speed. was:Change service offering of a stopped vm and then starting it should check host cpu capability with the new service offering. > Change service offering of a stopped vm and then starting it should check > host cpu capability > - > > Key: CLOUDSTACK-5391 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5391 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta > Fix For: 4.3.0 > > > Change service offering of a stopped vm and then starting it should check > host cpu capability with the new service offering. > Host has 4 physical CPU cores. > Create a service offering of 5 CPU cores and scaled up existing VM with this > service offering. > Similarly for speed. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-5391) Change service offering of a stopped vm and then starting it should check host cpu capability
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-5391: Fix Version/s: 4.3.0 > Change service offering of a stopped vm and then starting it should check > host cpu capability > - > > Key: CLOUDSTACK-5391 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5391 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Nitin Mehta >Assignee: Nitin Mehta > Fix For: 4.3.0 > > > Change service offering of a stopped vm and then starting it should check > host cpu capability with the new service offering. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (CLOUDSTACK-5391) Change service offering of a stopped vm and then starting it should check host cpu capability
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-5391: Affects Version/s: 4.2.0 > Change service offering of a stopped vm and then starting it should check > host cpu capability > - > > Key: CLOUDSTACK-5391 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5391 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.2.0 >Reporter: Nitin Mehta > > Change service offering of a stopped vm and then starting it should check > host cpu capability with the new service offering. -- This message was sent by Atlassian JIRA (v6.1#6144)
