Description of problem: ======================= In the Upstream version of packstack, RHN, Satellite and subscription manager related attributes should not be available. Version-Release number of selected component (if applicable): ============================================================= openstack-packstack-2012.2.3-0.1.dev454.fc18.noarch How reproducible: ================= Steps to Reproduce: =================== 1. Repo baseurl=http://repos.fedorapeople.org/repos/openstack/openstack-folsom/fedora-17/ 2. yum install openstack-packstack 3. packstack --gen-answer-file=ans.txt 4. Redhat Related attributes: Actual results: =============== $ grep -E "CONFIG_RH|CONFIG_SATELLITE" ans.txt | grep -v "#" CONFIG_RH_USER= CONFIG_RH_PW= CONFIG_RH_BETA_REPO=n CONFIG_SATELLITE_URL= CONFIG_SATELLITE_USER= CONFIG_SATELLITE_PW= CONFIG_SATELLITE_AKEY= CONFIG_SATELLITE_CACERT= CONFIG_SATELLITE_PROFILE= CONFIG_SATELLITE_FLAGS= CONFIG_SATELLITE_PROXY= CONFIG_SATELLITE_PROXY_USER= CONFIG_SATELLITE_PROXY_PW= Expected results: ================= No RHN, Satellite and subscription manager related attributes should be avalible.
*** Bug 927645 has been marked as a duplicate of this bug. ***
It's not just having the attributes available in the answer file afterwards. The main packstack installer also asks questions like RHN subscription and similar. Neither should be in upstream packstack otherwise packstack looks like a marketing ploy. :(
Derek? I'm fine with having RHN options in the answer file, and being able to enable RHN subscriptions for hosts post-install, but I agree that this doesn't look good if you're running the installer in interactive mode on Fedora or CentOS. Would it be possible to skip these questions in the interactive install? Justin: If you *are* running on RHEL, then having Packstack manage RHN subscriptions is helpful to the user - I think it's OK to have this here.
Yeah, when running RHEL the questions are appropriate. But IMHO they shouldn't be asked for people running anything else. It's not like it's hard for the scripting to check first. :)
Proposed a simple solution: https://review.openstack.org/25993