Bug 1399372

Summary: Syncing protected images fails with NOT FOUND
Product: Red Hat Satellite Reporter: Johan Swensson <jswensso>
Component: Content ManagementAssignee: Tom McKay <tomckay>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.4CC: bbuckingham, hshukla, jcallaha, ktordeur, mmccune, nshaik, pdwyer, shbharad, tomckay
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-22 13:21:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Johan Swensson 2016-11-28 22:05:19 UTC 
Description of problem:
When syncing protected docker images such as registry.access.redhat.com/rhmap42/fh-mbaas the sync status fails with: "Could not fetch repository rhmap42/fh-mbaas from registry https://registry.access.redhat.com - NOT FOUND"

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

How reproducible:
Every time

Steps to Reproduce:
1. Make sure to have a manifest with a mobile SKU, MCT3363 should do
2. Upload the manifest
3. hammer product create --name 'RHMAP Docker images' --organization "Default Organization"
3. hammer repository create --name "rhmap42/mbaas" --organization "Default Organization" --content-type docker --url "https://registry.access.redhat.com" --docker-upstream-name "rhmap42/mbaas" --product "RHMAP Docker images"

Actual results:
2016-11-28 23:01:36 [foreman-tasks/action] [E] DKR1007: Could not fetch repository rhmap42/fh-mbaas from registry https://registry.access.redhat.com - NOT FOUND (Katello::Errors::PulpError)


Expected results:
Should succeed.
Comment 5 Tom McKay 2017-04-21 13:07:32 UTC 
Created redmine issue http://projects.theforeman.org/issues/19346 from this bug