cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "frank zhang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-3453) UCS:API: List Blades after decommissioning a blade, listUcsBlades API returns wrong number of total blades
Date Fri, 19 Jul 2013 23:08:49 GMT

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

frank zhang resolved CLOUDSTACK-3453.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.2.0
    
> UCS:API: List Blades after decommissioning a blade, listUcsBlades API returns wrong number
of total blades
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3453
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3453
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, UCS
>    Affects Versions: 4.2.0
>         Environment: Master with UCS and Baremetal
>            Reporter: Parth Jagirdar
>            Assignee: frank zhang
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> If a user decommissions a blade from UCS Chassis; List BLades still returns the previos
number of blades.
> Assuming this is due to data being fetched from MS DB rather then polling UCS for latest
Blade information and status.
> We need to update the DB with latest information regarding total number of blades and
their status. 
> To reproduce: disconnect a blade physically from chassis.
> Re register the UCS Manager to CS.
> Issue a listUcsBlade API.
> Also note that re-registering of UCS should not be required. A dynamic polling of Blades
and other relevant info should be supported. And Cs DB should be updated accordingly.

--
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