cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9251) error while change instance offering to custom offering
Date Mon, 11 Apr 2016 19:07:25 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15235752#comment-15235752
] 

ASF GitHub Bot commented on CLOUDSTACK-9251:
--------------------------------------------

Github user swill commented on the pull request:

    https://github.com/apache/cloudstack/pull/1363#issuecomment-208504591
  
    So my understand is there was a FindBugs issue originally.  In the process of fixing the
issue, some logic was changed to introduce an issue.  This commit is to revert to the original
code that had the FindBugs issue.  I guess it is a lesser of two evils.  If this goes in,
I think we should do what @DaanHoogland suggested and up the number of findbugs to account
for the known findbug issues in this commit.  This way we are not spammed with findbugs issues
and if other commits have findbugs issues, we are correctly notified.  Does that make sense?


> error while change instance offering to custom offering
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-9251
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9251
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>    Affects Versions: 4.7.0, 4.7.1
>         Environment: ACS 4.7.1 -  https://dist.apache.org/repos/dist/dev/cloudstack/4.7.1/
>            Reporter: Tomasz Zieba
>
> Changing compute offering to custom offering end with:
> Step to reproduce:
> 1. Create and run new instance with offering eg. 1 core / 1GB
> 2. Create Custom Offering eg 2 core / 2 GB
> 3. Stop the instance
> 4. Try to change offering of the instance
> 5. Error: Invalid cpu cores value, specify a value between 1 and 2147483647



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

Mime
View raw message