Bug 1371505

Summary:	Life Cycle Environment and Content View information is not inherited from host group if we create a host using hammer
Product:	Red Hat Satellite	Reporter:	anerurka
Component:	Hammer - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	bbuckingham, jcallaha
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 17:57:15 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:

Description anerurka 2016-08-30 11:35:36 UTC

Description of problem:

Life Cycle Environment and Content View information is not inherited from host group if we create a host using hammer

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

Satellite Server v.6.2.1

How reproducible:


Steps to Reproduce:

1. Create a Host Group on Satellite Server v.6.2.1

2. now try create a host using hammer specifying the above host group.

Example:

hammer> host create --name test-5 --hostgroup-id <> --location-id <> --organization-id <> --compute-attributes="cpus=2" --compute-resource='<>' --domain-id <> --ip='xxx.xxx.xxx.xx' --architecture-id <> --operatingsystem='RedHat 7.2' --root-password='<>' --partition-table-id <> --medium-id <>

Actual results:

- When the Host is created Life Cycle Environment and Content View are not inherited from Host Group

Expected results:

- When the Host is created Life Cycle Environment and Content View should be inherited from Host Group

Additional info:

Comment 2 Bryan Kearney 2018-09-04 17:57:15 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.