Bug 1369769 - cluster registry pull through logic is not respecting that value mentioned in ADD_REGISTRY of /etc/sysconfig/docker
Summary: cluster registry pull through logic is not respecting that value mentioned in...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 3.2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Maciej Szulik
QA Contact: Wei Sun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-24 11:40 UTC by Miheer Salunke
Modified: 2019-12-16 06:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-03 14:58:06 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Miheer Salunke 2016-08-24 11:40:49 UTC
Description of problem:

Pulling of rhel7 image fails during oc new-app creation process with the error as per attached new-app-debug.log while using the attached Dockerfile.

 Adding 
FROM registry.access.redhat.com/rhel7 
has fixed the issue.

Earlier it was only 
FROM rhel7 


But in the /etc/sysconfig/docker the ADD_REGISTRY='--add-registry registry.access.redhat.com' is already set and even then the registry is not getting considered for pulling the RHEL 7 image.

I think the cluster registry pull through logic is not respecting that value.
For now  the workaround is just specify it explicitly in their FROM

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

How reproducible:
Always.



Actual results:


Expected results:


Additional info:

Comment 8 Maciej Szulik 2017-01-03 14:58:06 UTC
Based on [1] I'm closing this as won't fix. There are at least two possible workarounds, which are recommended more than the requested fix:
1. create image stream 
2. specify full pullspec

[1] https://github.com/openshift/origin/pull/10637#issuecomment-242406054


Note You need to log in before you can comment on or make changes to this bug.