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 1676367 - Satellite 6.3.3 cannot synchronize containers from hub.juniper.net
Summary: Satellite 6.3.3 cannot synchronize containers from hub.juniper.net
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.3.3
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Mirek Długosz
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-12 05:51 UTC by John Apple II
Modified: 2022-03-13 16:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-15 14:57:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot of Juniper repository configuration (32.50 KB, image/png)
2019-02-12 05:51 UTC, John Apple II 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1578188 0 unspecified CLOSED [Satellite 6] Satellite 6.3/6.2.x no longer upload docker image 2021-02-22 00:41:40 UTC

Description John Apple II 2019-02-12 05:51:57 UTC 
Created attachment 1533904 [details]
Screenshot of Juniper repository configuration

Description of problem:

I am working on a RHOSP 13 deployment with Contrail 5.X.  Contrail 5 uses containers from hub.juniper.net, and I have to use the Container functionality in Satellite in this environment.  My lab system was running latest Satellite 6.3.3 upgraded on 10th Feb and synchronization failed with the contrail Container registry.  Specific test container was
https://hub.juniper.net/contrail/contrail-base

The specific Error I received was 

Katello::Errors::PulpError: DKR1008: Could not find registry API at https://hub.juniper.net

I confirmed with an RH engineer who had worked on this before that they could synchronize this repository.  The difference is that they are in NA and they use Satellite 6.4

I compared configurations between the Satellites with them, even testing my credentials on their Satellite 6.4, and the sync worked without issue.  However, it failed on 6.3 with the same error.

I have now upgraded my lab Satellite server to 6.4, and the Juniper container repository synchronizes without error.

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

How reproducible:
Every time

Steps to Reproduce:
1. Use Satellite 6.3
2. Obtain credentials from Juniper for Contrail at their hub.juniper.net container registry
3. Create a product entry for any Contrail container image
4. Setup the repository for that image (contrail-base, for example).
5. Attempt to sync the container.

Actual results:
Katello::Errors::PulpError: DKR1008: Could not find registry API at https://hub.juniper.net


Expected results:
51 containers with tags and labels should be synchronized.

Additional info:
Comment 4 Brendan Shephard 2019-02-13 04:33:35 UTC 
Hey John,


Are you able to try this with Verify SSL set to Yes for that repository?
Comment 5 John Apple II 2019-02-13 04:37:06 UTC 
Hi, Brendan,

  I tried it with Verify SSL on and off and the trailing slash in the URL and not in the URL.  All failed with 6.3.3, where the 6.4.1 Satellite server succeeded on the sync with each of those variations applied:

Here's the results.

SSL on, trailing slash
SSL off, trailing slash
SSL on, no trailing slash
SSL off, no trailing slash

6.3.3: All failed, error in the original report for the contrail-base and contrail-analytics-agent container
6.4.1: succeeded on all 4 tests with the contrail-base and I've now synced the entire container set on 6.4.1.

  Do you want to see the sosreport of the Satellite server with the logs?
Comment 6 John Apple II 2019-02-13 22:48:15 UTC 
I confirmed on a customer site running 6.3.4, this bug exists in the newer version as well.  Same error:

Katello::Errors::PulpError: DKR1008: Could not find registry API at https://hub.juniper.net
Comment 7 John Apple II 2019-02-14 01:06:48 UTC 
Appears that this may be related:
https://bugzilla.redhat.com/show_bug.cgi?id=1578188
Note You need to log in before you can comment on or make changes to this bug.