Bug 1328823 - Support Nested Satellite Host Groups during Provisioning
Summary: Support Nested Satellite Host Groups during Provisioning
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: Brandon Dunne
QA Contact: Jan Krocil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 11:15 UTC by Maxim Burgerhout
Modified: 2016-06-29 15:51 UTC (History)
5 users (show)

Fixed In Version: 5.6.0.5
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 15:51:30 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)
Deduplicated host groups that are not nested properly (69.12 KB, image/png)
2016-04-20 11:15 UTC, Maxim Burgerhout
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description Maxim Burgerhout 2016-04-20 11:15:37 UTC
Created attachment 1149039 [details]
Deduplicated host groups that are not nested properly

Description of problem:
When provisioning a configured system (CFME connected with Satellite 6.1), I get to select a host group for the system on the 'catalog' tab.

The host groups I use in Satellite 6 are nested (InfraTest/RHEL7-Plain, where RHEL7-Plain is a host group nested in the InfraTest host group).

On the catalog tab, CFME shows a flat list of hostgroups, and seems to deduplicate host groups with the same names but with different parent host groups. On the /provider_foreman/explorer page, host group nested is shown fine.

As an example: I have two RHEL7-Plain host groups. One nested in InfraTest, one nested in a host group called Production.

On the 'catalog' tab during the 'provision a configured system' action, CFME shows only one of these, and I'm not even sure which one it shows. Judging by the order, it's probably the Production one, btw, but that's not the point ;)

Please implement visible, nested host groups on the "catalog" tab during the "provision configured system" action in CFME configuration management.

Version-Release number of selected component (if applicable):
5.5.3.4.

How reproducible:


Steps to Reproduce:
1. Setup nested host groups in Satellite, create two host groups with the same name that are children of different parents
2. In CFME try and provision a configured system
3. Go to Catalog tab

Actual results:
Host groups are shown as a flat list, only one of the children will show (see screenshot).

Expected results:
Host groups are shown with their full name, with nesting visible, so that I can pick the right one.

Additional info:

Comment 3 CFME Bot 2016-04-26 12:35:37 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/554b47deac3fb24011bd7468ffb7d6540b45a05a

commit 554b47deac3fb24011bd7468ffb7d6540b45a05a
Author:     Brandon Dunne <bdunne>
AuthorDate: Mon Apr 25 15:26:24 2016 -0400
Commit:     Brandon Dunne <bdunne>
CommitDate: Mon Apr 25 15:26:24 2016 -0400

    Use description to show full path to the ConfigurationProfile
    
    In provisioning dialogs, the full path to the ConfigurationProfile
    is much more useful in the drop-down selection.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1328823

 .../providers/foreman/configuration_manager/provision_workflow.rb | 2 +-
 .../foreman/configuration_manager/provision_workflow_spec.rb      | 8 +++-----
 2 files changed, 4 insertions(+), 6 deletions(-)

Comment 5 Jan Krocil 2016-05-27 22:29:26 UTC
Verified fixed in 5.6.08-rc1 - 5.6.0.8-rc1.20160524155303_f2a5a50.

Host groups in the Catalog tab now contain full path (parent host groups).

Comment 7 errata-xmlrpc 2016-06-29 15:51:30 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1348


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