You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Parth Jagirdar (JIRA)" <ji...@apache.org> on 2013/07/10 19:33:48 UTC
[jira] [Updated] (CLOUDSTACK-3453) UCS:API: List Blades after
decommissioning a blade, listUcsBlades API returns wrong number of total
blades
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Parth Jagirdar updated CLOUDSTACK-3453:
---------------------------------------
Summary: UCS:API: List Blades after decommissioning a blade, listUcsBlades API returns wrong number of total blades (was: UCS:API: List Blades after decommission a blade listUcsBlades API returns wrong number of total blades)
> 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
> Priority: Critical
>
> 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