When invoking a start or stop action on a instance via API, it does not reflected in CloudForms 4 UI however it performed desired action on cloud side.
Created attachment 1103901[details]
Issue description with screenshots
Description of problem:
When invoking a start or stop action on a instance via API, it does not reflect in CloudForms 4 UI however desired action is performed on cloud side.
Version-Release number of selected component (if applicable):
CFME 4
How reproducible:
Always
Steps to Reproduce:
- ‘start’ the instance via API which is there in the OpenStack/AWS ec2 provider.
Actual results:
1. On Openstack UI: showing Power state as Running
2. On CFME UI: Showing power state as ‘off’
Expected results:
It should show the Power state as 'On' on CFME UI as well.
Additional info:
1. After doing 'Refresh Relationships and Power States', instance is showing as 'On' on CFME 4 UI.
2. A single VM refresh action is not there in the API atm
3. I think for openstack provider, the event monitoring and detection is very limited.
Hi Tim,
I see this issue from UI as well:
1. I started the instance from Openstack UI and it is in running state but on CFME UI Power State is OFF.
2. After doing a manual refresh, it is showing as ON.
Regards,
Nikhil Gupta
Verified that the power state is reflected in the UI without the need to do 'Refresh Relationships and Power States' when the action was invoked via REST API.
Created attachment 1103901 [details] Issue description with screenshots Description of problem: When invoking a start or stop action on a instance via API, it does not reflect in CloudForms 4 UI however desired action is performed on cloud side. Version-Release number of selected component (if applicable): CFME 4 How reproducible: Always Steps to Reproduce: - ‘start’ the instance via API which is there in the OpenStack/AWS ec2 provider. Actual results: 1. On Openstack UI: showing Power state as Running 2. On CFME UI: Showing power state as ‘off’ Expected results: It should show the Power state as 'On' on CFME UI as well. Additional info: 1. After doing 'Refresh Relationships and Power States', instance is showing as 'On' on CFME 4 UI. 2. A single VM refresh action is not there in the API atm 3. I think for openstack provider, the event monitoring and detection is very limited.