Description of problem: When configuring (deployment=headpin) with a custom answer file, specified org_name is _not_ configured. Version-Release number of selected component (if applicable): katello-headpin-all-0.1.116-2.el6.noarch Steps to Reproduce: 1. cp default-answer-file /tmp/answer-file and edit. Specify custom user_name, user_pass, and org_name. 2. katello-configure --deployment=headpin --answer-file=/tmp/answer-file 3. Navigate to http://[servername]/headpin Actual results: ACME_Corporation is installed / configured v. the specified org_name. Expected results: Specified org_name should be the only org installed / configured.
Further investigation, turns out that org_name went into the Description field of ACME_Corporation.
A scenario: katello-configure --deployment=headpin --org-name Garik-n-co works fine with preparing default org: Garik-n-co will try the other one (taking value from answer file).
# REOPEN so the option with providing --org-name in the cli installer - WORKS the one in answer_file - NOT --- katello-configure --deployment=headpin --answer-file=/tmp/answer-file <snip> # Katello initial Organization (default: ACME_Corporation) org_name = GarikOrg </snip> checked against packages: --- katello-headpin-all-0.1.129-1.el6.noarch katello-configure-0.1.58-1.el6.noarch
Is anybody working on this one? It's on my name. If not, I will start working on it tomorrow.
It would be much easier to implement this in ImageFactory, but I am not sure if this is technically possible. Categories are maybe not visible to yum. https://bugzilla.redhat.com/show_bug.cgi?id=788560
I think this was the wrong bz :)
Damn, sorry, discard C-10.
Race condition when executing puppet in headpin deployment. commit 5e4fe62863eb6b5d2bc7b9727668106aae50f39f