Bug 1393449

Summary: Auto provisioned hosts do not inherit realm settings
Product: Red Hat Satellite Reporter: Maxim Burgerhout <mburgerh>
Component: ProvisioningAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.3CC: inecas, lzap
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-09 15:26:32 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:
Attachments:
Description Flags
Auto provisioned, discovered host variables
none
'Normally' provisioned host none

Description Maxim Burgerhout 2016-11-09 15:06:07 UTC
Created attachment 1218969 [details]
Auto provisioned, discovered host variables

Description of problem:
When I boot up a new system with the discovery iso, setup a discovery rule and auto provision the system, it does not inherit the realm settings. 

Included two screenshots indicate differences in variables between a 'normally' provisioned system, and a system that was auto provisioned through discovery.

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

How reproducible:


Steps to Reproduce:
1. Setup system to boot from (remastered) discovery iso
2. setup autoprovision rule to deploy systems into existing hostgroup w/ realm settings
3. auto provision system

Actual results:
Systems provisions without REALM

Expected results:
System provisions with REALM

Additional info:

Comment 1 Maxim Burgerhout 2016-11-09 15:06:29 UTC
Created attachment 1218970 [details]
'Normally' provisioned host

Comment 2 Lukas Zapletal 2016-11-09 15:26:32 UTC
Hello, this is dupe of:

https://bugzilla.redhat.com/show_bug.cgi?id=1367136

*** This bug has been marked as a duplicate of bug 1367136 ***