cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitin Mehta (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-3605) ASF 4.1 to 4.2 Upgrade: "display_offering" value of default and System disk/service offerings are different on an Upgraded Setup
Date Thu, 18 Jul 2013 09:42:48 GMT

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

Nitin Mehta resolved CLOUDSTACK-3605.
-------------------------------------

    Resolution: Fixed
    
> ASF 4.1 to 4.2 Upgrade: "display_offering" value of default and System disk/service offerings
are different on an Upgraded Setup
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3605
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3605
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Chandan Purushothama
>            Assignee: Nitin Mehta
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> On a 4.2 Setup:
> mysql> select id,name,display_offering from disk_offering;
> +----+------------------------------------------+------------------+
> | id | name                                     | display_offering |
> +----+------------------------------------------+------------------+
> |  1 | Small Instance                           |                0 |
> |  2 | Medium Instance                          |                0 |
> |  3 | Small                                    |                0 |
> |  4 | Medium                                   |                0 |
> |  5 | Large                                    |                0 |
> |  6 | Custom                                   |                0 |
> |  7 | System Offering For Software Router      |                0 |
> |  8 | System Offering For Elastic LB VM        |                0 |
> |  9 | System Offering For Secondary Storage VM |                0 |
> | 10 | System Offering For Internal LB VM       |                0 |
> | 11 | System Offering For Console Proxy        |                0 |
> +----+------------------------------------------+------------------+
> 11 rows in set (0.00 sec)
> On an Upgraded 4.2 Setup:
> mysql>  select id,name,display_offering from disk_offering;
> +----+------------------------------------------+------------------+
> | id | name                                     | display_offering |
> +----+------------------------------------------+------------------+
> |  1 | Small Instance                           |                1 |
> |  2 | Medium Instance                          |                1 |
> |  3 | Small                                    |                1 |
> |  4 | Medium                                   |                1 |
> |  5 | Large                                    |                1 |
> |  6 | Custom                                   |                1 |
> |  7 | System Offering For Software Router      |                1 |
> |  8 | System Offering For Elastic LB VM        |                1 |
> |  9 | System Offering For Secondary Storage VM |                1 |
> | 10 | System Offering For Console Proxy        |                1 |
> | 11 | System Offering For Internal LB VM       |                0 |
> +----+------------------------------------------+------------------+
> 11 rows in set (0.00 sec)
> Since I am unaware of the expanse of the issue's effect, I increased the priority to
Critical

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message