You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Jessica Wang (JIRA)" <ji...@apache.org> on 2013/09/16 23:03:51 UTC
[jira] [Resolved] (CLOUDSTACK-4687) after disassociate UCS profile,
UI still show profile path even response object has empty path
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jessica Wang resolved CLOUDSTACK-4687.
--------------------------------------
Resolution: Fixed
> after disassociate UCS profile, UI still show profile path even response object has empty path
> ----------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4687
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4687
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: UI
> Reporter: Jessica Wang
> Assignee: Jessica Wang
> Attachments: Capture.PNG
>
>
> This is a clone of
> http://bugs-ccp.citrix.com/browse/CS-18232
> --------------------------------------------------------------------------------------------------------------------------------------------
> see below API response, there is no profiledn, but after API return, UI still shows profile as attachment
>
> however, if we refresh UI, the profile gone
> {
> "queryasyncjobresultresponse": {
> "accountid": "835fb2d5-0b76-11e3-9350-f4f3e49b5dfe",
> "userid": "835fc0e5-0b76-11e3-9350-f4f3e49b5dfe",
> "cmd": "org.apache.cloudstack.api.DisassociateUcsProfileCmd",
> "jobstatus": 1,
> "jobprocstatus": 0,
> "jobresultcode": 0,
> "jobresulttype": "object",
> "jobresult": {
> "ucsblade": {
> "id": "f8d08575-7a1c-4f79-a588-d129c38bcc4f",
> "ucsmanagerid": "0d87c1a6-5664-425c-9024-2ddd9605d260",
> "bladedn": "sys/chassis-1/blade-1"
> }
> },
> "created": "2013-09-13T22:17:29-0700",
> "jobid": "2c3698a8-39ac-43e6-8ade-86eb2d3726a0"
> }
> }
--
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