Bug 1624705 - Provider details page not updated
Summary: Provider details page not updated
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.10.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.10.z
Assignee: Brian McLaughlin
QA Contact: Vatsal Parekh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-03 06:27 UTC by Vatsal Parekh
Modified: 2019-08-27 06:53 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-27 06:53:52 UTC
Category: ---
Cloudforms Team: KubeVirt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot of summary view (151.36 KB, image/png)
2018-09-03 06:27 UTC, Vatsal Parekh 		no flags Details
screenshot of dashboard view (95.44 KB, image/png)
2018-09-03 06:31 UTC, Vatsal Parekh 		no flags Details
View All

Description Vatsal Parekh 2018-09-03 06:27:50 UTC 
Created attachment 1480443 [details]
screenshot of summary view

Description of problem:
After the template sync issue solved, I am able to see the VM & templates in `infra->virtual machines` page, but the provider details page is not updated with the template and vm details (check the screenshots attached)

Version-Release number of selected component (if applicable):
Version 5.10.0.14.20180831154906_2f9a1dd

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Vatsal Parekh 2018-09-03 06:31:13 UTC 
Created attachment 1480444 [details]
screenshot of dashboard view

Dashboard view is showing the details, but with the red cross
Comment 3 Piotr Kliczewski 2018-09-03 07:20:44 UTC 
Please provide the logs.
Comment 5 Piotr Kliczewski 2018-09-03 10:09:04 UTC 
Based on provided logs I do not see any explicit issue. This could be regression after bug #1610772. Ladislav do you know what could cause this issue?
Note You need to log in before you can comment on or make changes to this bug.