Bug 1654165 - Service not showing VMs belong to
Summary: Service not showing VMs belong to
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.10.0
Assignee: Greg McCullough
QA Contact: Niyaz Akhtar Ansari
Red Hat CloudForms Documentation
Depends On:
Blocks: 1655773 1660603
TreeView+ depends on / blocked
Reported: 2018-11-28 07:42 UTC by Gellert Kis
Modified: 2019-02-26 06:55 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1655773 1660603 (view as bug list)
Last Closed: 2019-02-12 16:50:35 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:

Attachments (Terms of Use)

Comment 2 Allen W 2018-11-29 18:13:59 UTC
Hi Gellert, can we get a machine exhibiting this issue?

Comment 3 Allen W 2018-11-29 18:16:53 UTC
Woops I should read more clearly, thanks to your original post! This looks like a classic ui issue (from looking at the screenshots) is that correct?

Comment 7 Tina Fitzgerald 2018-11-30 13:50:10 UTC
We've identified this to be a service resource linking issue, and are working on a fix.

Comment 8 Tina Fitzgerald 2018-11-30 15:37:39 UTC
This issue is resolved with the following PR:

Comment 11 Tina Fitzgerald 2018-12-17 20:23:29 UTC
Adding 5.8.z flag per conversation with Dennis.

Comment 13 Tina Fitzgerald 2019-01-04 16:07:55 UTC
Correction to comment 8. The following PR resolves the reported issue:

Comment 15 Tina Fitzgerald 2019-01-24 15:57:41 UTC
Hi Niyaz,

Provisioning Service bundles with the affected code causes the underlying resources(VMs) to not be properly displayed when viewing the provisioned Service.

1. Create a Service Bundle, containing 2 service items, each of which will provision a single VM. (VMware for instance)
2. Order the Service bundle.
3. View the Service. There will likely be only a single VM displayed, instead of the 2 expected VMs.

Let me know if you have any questions.


Note You need to log in before you can comment on or make changes to this bug.