Bug 1018648 - Make $katello_org in node-installer a CLI parameter
Summary: Make $katello_org in node-installer a CLI parameter
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-14 04:33 UTC by Mike McCune
Modified: 2014-01-27 14:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-16 19:11:38 UTC
Target Upstream Version:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.