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 1147049 - Passing empty values to katello-installer proxy settings creates invalid JSON
Summary: Passing empty values to katello-installer proxy settings creates invalid JSON
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Corey Welton
URL:
Whiteboard:
: 1278085 (view as bug list)
Depends On:
Blocks: 1132363
TreeView+ depends on / blocked
 
Reported: 2014-09-26 16:52 UTC by David Gurtner
Modified: 2019-09-25 20:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:22:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1031001 0 unspecified CLOSED Invalid pulp yum_importer.json can be written with missing --proxy-* arguments 2021-02-22 00:41:40 UTC
Red Hat Knowledge Base (Solution) 2201011 0 None None None 2016-03-16 13:11:46 UTC
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Internal Links: 1031001

Description David Gurtner 2014-09-26 16:52:54 UTC 
Description of problem:

Running katello-installer --katello-proxy-port="" generates broken Pulp Plugins files under /etc/pulp/server/plugins.conf.d/{yum,puppet,iso}_importer.json

The Files will contain the following line:

"proxy_port": ,

instead of 

"proxy_port": "",

This prevents celeryd workers from starting.

Version-Release number of selected component (if applicable):


How reproducible:

always


Steps to Reproduce:
1. katello-installer --katello-proxy-port="" --katello-proxy-url=""

Actual results:

/etc/pulp/server/plugins.conf.d/{yum,puppet,iso}_importer.json

Contain the line

"proxy_port": ,


Expected results:

"proxy_port": NULL,


Additional info:

Removing the values from answer file or passing NULL works.
Comment 1 RHEL Program Management 2014-09-26 17:03:19 UTC 
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.
Comment 3 Eric Helms 2014-11-04 21:03:50 UTC 
This issue has been fully addressed by - https://github.com/Katello/katello-installer/pull/84
Comment 6 Elyézer Rezende 2015-04-06 19:32:10 UTC 
Failed on: Satellite-6.1.0-RHEL-7-20150331.1

Steps:

1. Run katello-installer --katello-proxy-port="" --katello-proxy-url=""
2. Checked the config files

# cat /etc/pulp/server/plugins.conf.d/{yum,puppet,iso}_importer.json
{
    "proxy_host": "",

    "proxy_port": ,

    "proxy_username": "",
    "proxy_password": ""
}
{
    "proxy_host": "",

    "proxy_port": ,

    "proxy_username": "",
    "proxy_password": ""
}
{
    "proxy_host": "",

    "proxy_port": ,

    "proxy_username": "",
    "proxy_password": ""
}
Comment 8 errata-xmlrpc 2015-08-12 05:17:25 UTC 
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
Comment 9 sthirugn@redhat.com 2015-08-14 20:46:20 UTC 
Accidentally closed with 6.1.1 errata
Comment 10 Brad Buckingham 2015-11-16 21:47:25 UTC 
*** Bug 1278085 has been marked as a duplicate of this bug. ***
Comment 11 Corey Welton 2016-06-24 14:54:00 UTC 
POSSIBLY Verified in Snap 16:

[root@rhsm-qe-3 ~]# cat /etc/pulp/server/plugins.conf.d/{yum,puppet,iso}_importer.json
{
    
    "proxy_host": null,
    
    
    "proxy_port": null,
    
        "proxy_username": "admin",
    
        "proxy_password": "password"
    
}
{
    
    "proxy_host": null,
    
    
    "proxy_port": null,
    
        "proxy_username": "admin",
    
        "proxy_password": "password"
    
}
{
    
    "proxy_host": null,
    
    
    "proxy_port": null,
    
        "proxy_username": "admin",
    
        "proxy_password": "password"
    
}


Should we be clearing username/password  if proxy settings themselves are cleared?
Comment 12 Corey Welton 2016-06-24 14:55:25 UTC 
To clarify, does having user/password set affect things if there are no values otherwise for host and port?
Comment 13 Corey Welton 2016-06-24 15:33:19 UTC 
Tested and even if the user/passwd remain, sync continues to work.

That said, there is no reason I can think of to keep user/passwd around if proxy and port are gone.  Will write up a separate RFE for removal.
Comment 15 Bryan Kearney 2016-07-27 11:22:39 UTC 
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/RHBA-2016:1501
Note You need to log in before you can comment on or make changes to this bug.