Red Hat Bugzilla – Bug 1127397
Running the installer a second time with no proxy values creates an invalid config
Last modified: 2017-02-23 16:07:58 EST
Description of problem: If you run katello-installer with proxy settings, it saves them to /etc/pulp/server/plugins.conf.d/yum_importer.json. Then if you run "katello-installer --reset" but no proxy, it creates an invalid config and you hit: The configuration parameter <proxy_port> must be set to a positive integer, but is currently set to <>. Version-Release number of selected component (if applicable): 6.0.4 How reproducible: Always Steps to Reproduce: 1. Run katello-installer with proxy values. Confirm they're in /etc/pulp/server/plugins.conf.d/yum_importer.json. 2. Run katello-installer --reset 3. Go into your app and publish a content view Actual results: You get an error in pulp: The configuration parameter <proxy_port> must be set to a positive integer, but is currently set to <>. Expected results: Successful publish. Additional info:
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.
Also, it looks like puppet_importer.json and iso_importer.json have the same problem too I think.
This issue has been addressed upstream here - https://github.com/Katello/katello-installer/pull/84
Verified on: Satellite-6.1.0-RHEL-7-20150331.1 Steps to verify: 1. Installed Satellite pointing to an external squid proxy on port 3128. 2. Imported a manifest 3. Enabled "Red Hat Enterprise Virtualization Agents for RHEL 6 Server RPMs x86_64 6Server" Red Hat repository and synced it. 4. Ran the installer one more time but without any proxy option 5. Enabled "Red Hat Enterprise Linux 7 Server - RH Common RPMs x86_64 7Server" Red Hat repository and synced it.
This bug is slated to be released with Satellite 6.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592