Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1018648

Summary: Make $katello_org in node-installer a CLI parameter
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: InstallationAssignee: Justin Sherrill <jsherril>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.2CC: cwelton, inecas
Target Milestone: UnspecifiedKeywords: 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: 2013-10-16 19:11:38 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 Mike McCune 2013-10-14 04:33:58 UTC 
When doing node-installs the users are stuck with the hard coded "Katello Infrastructure" org to create the node + key RPMs. 

This makes it difficult if you want to utilize an existing Org that has content or not rely on this pre-determined name.
Comment 2 Justin Sherrill 2013-10-16 19:08:25 UTC 
So this is actually not needed, as this is already possible with:

a) On katello server:

  node-certs-generate  --katello-org="ACME_Corporation" --child-fqdn="node.evel"  --katello-user='admin' --katello-password='admin'

b) On new node:


subscription-manager register --org "ACME_Corporation" --activationkey node-installer

 node-install --parent-fqdn master.example.com


I will update the documentation in the node-installer git repo with this tip.
Comment 3 Justin Sherrill 2013-10-16 19:09:49 UTC 
small omission: 

command in a)  should have
     --katello-activation-key="node-installer"
on the end
Comment 4 Ivan Necas 2013-10-17 07:35:48 UTC 
@justin yes, if the --katello-activation-key is not provided, it does not create it. Also, other params for the repos with certs are available. see --help for more