Bug 1333464

Summary:	QCI Development Environment Requires PR235 for foreman_discovery to be cherry-picked.
Product:	Red Hat Satellite	Reporter:	John Matthews <jmatthew>
Component:	Discovery Plugin	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED ERRATA	QA Contact:	Roman Plevka <rplevka>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	cwelton, dgao, jmatthew, jmontleo, mmccune, rplevka
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/12362
Whiteboard:
Fixed In Version:	rubygem-hammer_cli_foreman-0.5.1.7-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:10:27 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:
Bug Depends On:
Bug Blocks:	1212602

Description John Matthews 2016-05-05 15:03:03 UTC

Description of problem:

We are running a development environment of Satellite 6.2.
When provisioning we hit:
  
   NameError: uninitialized constant PowerService

Issue has been fixed in upstream PR:
   https://github.com/theforeman/foreman_discovery/pull/235


We are asking for this commit to be cherry-picked downstream into Satellite 6.2.

Comment 2 Corey Welton 2016-05-05 15:59:18 UTC

Need specific repro scenario

Comment 5 Lukas Zapletal 2016-05-06 07:47:46 UTC

Interesting, why this happened only in dev environment? I think it had to do something with class reloading...

Comment 6 Lukas Zapletal 2016-05-13 07:08:33 UTC

QA note: This is development environment issue, just verify discovery works as expected.

Comment 7 Roman Plevka 2016-05-30 16:40:36 UTC

VERIFIED
on sat 6.2.0 beta (GA13.1)

The change doesn't seem to have any negative effect on the discovery functionality, I was able to discover a host with no problems.

Comment 8 Bryan Kearney 2016-07-27 11:10:27 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:1501