Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
+++ This bug was initially created as a clone of Bug #976435 +++
Description of problem:
When syncing puppet content, katello needs a global proxy configuration similar to yum syncing.
--- Additional comment from Michael Hrivnak on 2013-06-21 11:16:21 EDT ---
I think we'll accomplish this by using nectar for puppet syncs.
--- Additional comment from Randy Barlow on 2013-09-05 15:37:37 EDT ---
I believe that Jason has submitted a pull request to use Nectar for Puppet syncs, and so given Mike's comment this may be ready to be marked POST?
--- Additional comment from Michael Hrivnak on 2013-09-11 14:37:08 EDT ---
We just need to make sure that the puppet importer has a config file somewhere similar to the yum importer. As long as it exists and we can verify that nectar config values in that file are used by the importer, this RFE should be done.
--- Additional comment from Barnaby Court on 2013-09-26 08:45:18 EDT ---
Pull Requests:
https://github.com/pulp/pulp/pull/634https://github.com/pulp/pulp_rpm/pull/339https://github.com/pulp/pulp_puppet/pull/75
--- Additional comment from Jeff Ortel on 2013-09-26 16:54:15 EDT ---
build: 2.3.0-0.16.alpha
--- Additional comment from Preethi Thomas on 2013-10-07 09:26:50 EDT ---
verified
[root@pulp-v2-server ~]# rpm -qa pulp-server
pulp-server-2.3.0-0.17.beta.el6.noarch
[root@pulp-v2-server ~]#
[root@pulp-v2-server ~]# pulp-admin puppet repo create --repo-id puppet-repo --feed http://forge.puppetlabs.com --queries stdlib,mysql --proxy-host http://pulp-proxy.usersys.redhat.com --proxy-port 3128
Successfully created repository [puppet-repo]
[root@pulp-v2-server ~]# pulp-admin puppet repo sync run --repo-id puppet-repo
+----------------------------------------------------------------------+
Synchronizing Repository [puppet-repo]
+----------------------------------------------------------------------+
This command may be exited by pressing ctrl+c without affecting the actual
operation on the server.
Downloading metadata...
[==================================================] 100%
Metadata Query: 2/2 items
... completed
Downloading new modules...
[==================================================] 100%
Module: 38/38 items
... completed
Publishing modules...
[==================================================] 100%
Module: 38/38 items
... completed
Generating repository metadata...
[-]
... completed
Publishing repository over HTTP...
... completed
Publishing repository over HTTPS...
... skipped
From nectar.log
2013-10-07 09:20:54,349 urllib3.connectionpool:INFO: Starting new HTTP connection (1): pulp-proxy.usersys.redhat.com
2013-10-07 09:20:54,351 urllib3.connectionpool:INFO: Starting new HTTP connection (1): pulp-proxy.usersys.redhat.com
Retrieving content via unauthenticated proxy seems to work.
However, bug #1021662 indicates that authenticated proxy is not presently working. This is similar to what I'm seeing in katello, as well.
Will mark this verified, insofar as ncsa auth goes for squid. digest_pw method fails, and I'll write that up as a separate bz.
pulp-server-2.3.0-0.26.beta.el6sat.noarch
Satellite-6.0.2-RHEL-6-20131101.0