Bug 1131641

Summary:	Automatically associate capsule with content host organization
Product:	Red Hat Satellite	Reporter:	Shannon Hughes <shughes>
Component:	Foreman Proxy	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.4	CC:	bbuckingham, bkearney, jsherril, riehecky, xdmoon
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-06 19:07:08 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:	1115190

Description Shannon Hughes 2014-08-19 18:08:07 UTC

Description of problem:

when installing a external/remote capsule it would be reasonable to associate the capsule with the content host organization or allow users to supply org to associate from the capsule installer cli

discussed this request with jsherrill during gss test day

Comment 1 RHEL Program Management 2014-08-19 18:23:13 UTC

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Bryan Kearney 2016-07-08 20:27:13 UTC

Per 6.3 planning, moving out non acked bugs to the backlog

Comment 5 Bryan Kearney 2017-01-06 19:07:08 UTC

This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you belive doing so is an issue, please feel free to re-open and provide additional business information. Thank you.