Bug 1219614

Summary:	Unable to provision a newly discovered foreman host
Product:	Red Hat CloudForms Management Engine	Reporter:	Keenan Brock <kbrock>
Component:	Provisioning	Assignee:	Keenan Brock <kbrock>
Status:	CLOSED ERRATA	QA Contact:	Jan Krocil <jkrocil>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.4.0	CC:	dmacpher, jhardy, kbrock, obarenbo
Target Milestone:	GA
Target Release:	5.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-16 13:02:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Keenan Brock 2015-05-07 19:18:14 UTC

Description of problem:
I'm testing out the Foreman integration on the CFME 5.4-16 beta
appliance so we can document it but I'm running into an issue when
trying to provision bare metal. I was wondering if you could point me
in the right direction.

I can not detect new bare metal hosts found through Foreman's Discovery
service

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

5.4 development build

How reproducible:

always

Steps to Reproduce:
1. add a host to foreman, or clear the hostgroup in an existing host
2. provider refresh in cfme
3. the host will not display in the configuration profile view
4. the host will display in the configuration system view
5. the detail view for this host will fail

Actual results:


Expected results:

Able to easily find a newly discovered host
Able to view the information on that host in the detail view
Able to provision it with a new hostgroup (configuration profile)

Additional info:

Comment 2 CFME Bot 2015-05-07 22:45:57 UTC

New commit detected on manageiq/master:
https://github.com/ManageIQ/manageiq/commit/04d3518732888081f7139435bf1467524bc14a32

commit 04d3518732888081f7139435bf1467524bc14a32
Author:     Keenan Brock <kbrock>
AuthorDate: Thu May 7 12:32:00 2015 -0400
Commit:     Keenan Brock <kbrock>
CommitDate: Thu May 7 16:36:07 2015 -0400

    Add ConfiguredSystem configuration profile column
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1219614

 vmdb/app/models/configured_system.rb     | 2 ++
 vmdb/product/views/ConfiguredSystem.yaml | 3 +++
 2 files changed, 5 insertions(+)

Comment 3 CFME Bot 2015-05-07 22:46:00 UTC

New commit detected on manageiq/master:
https://github.com/ManageIQ/manageiq/commit/7ffbf0c58736e91bafccd7073ec1b69591af4187

commit 7ffbf0c58736e91bafccd7073ec1b69591af4187
Author:     Keenan Brock <kbrock>
AuthorDate: Thu May 7 12:32:41 2015 -0400
Commit:     Keenan Brock <kbrock>
CommitDate: Thu May 7 16:36:08 2015 -0400

    Foreman configured systems work with nil profiles
    
    Don't display an image for a nil profile
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1219614

 vmdb/app/helpers/provider_foreman_helper.rb | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

Comment 5 Jan Krocil 2015-06-04 20:27:27 UTC

Verified fixed in 5.4.0.4 - (5.4.0.4.20150528174021_88cc76c).

Configured systems with no hostgroup can be accessed in the "Configured Systems" subsection and provisioned with any available hostgroup.

Comment 7 errata-xmlrpc 2015-06-16 13:02:00 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://rhn.redhat.com/errata/RHBA-2015-1100.html