Bug 1539252 - Failed to push image to OCP internal image registry on EC2
Summary: Failed to push image to OCP internal image registry on EC2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.9.0
Assignee: Ben Parees
QA Contact: Weihua Meng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-27 10:13 UTC by Weihua Meng
Modified: 2018-06-27 18:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-06-27 18:01:30 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2013 None None None 2018-06-27 18:01:53 UTC

Description Weihua Meng 2018-01-27 10:13:28 UTC
Description of problem:
Failed to push image to OCP internal image registry on EC2
this works fine on openstack.

Version-Release number of selected component (if applicable):
openshift v3.9.0-0.30.0
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.8

How reproducible:
Always

Steps to Reproduce:
1. set OCP cluster on EC2 with openshift_registry_backend_storage=ebs
2. new-project and new-app
# oc new-app nodejs-mongodb-example
3. oc logs -f bc/nodejs-mongodb-example
4. oc get all

Actual results:
3. 
Pushing image docker-registry.default.svc:5000/wmeng/nodejs-mongodb-example:latest ...
Registry server Address: 
Registry server User Name: serviceaccount
Registry server Email: serviceaccount@example.org
Registry server Password: <<non-empty>>
error: build error: Failed to push image: Get https://docker-registry.default.svc:5000/v1/_ping: http: server gave HTTP response to HTTPS client

4.
# oc get all
NAME                                       REVISION   DESIRED   CURRENT   TRIGGERED BY
deploymentconfigs/mongodb                  1          1         1         config,image(mongodb:3.2)
deploymentconfigs/nodejs-mongodb-example   0          1         0         config,image(nodejs-mongodb-example:latest)

NAME                                  TYPE      FROM      LATEST
buildconfigs/nodejs-mongodb-example   Source    Git       1

NAME                              TYPE      FROM          STATUS                               STARTED         DURATION
builds/nodejs-mongodb-example-1   Source    Git@ef1b71a   Failed (PushImageToRegistryFailed)   4 minutes ago   1m26s

NAME                                  DOCKER REPO                                                     TAGS      UPDATED
imagestreams/nodejs-mongodb-example   docker-registry.default.svc:5000/wmeng/nodejs-mongodb-example             

NAME                            HOST/PORT                                                   PATH      SERVICES                 PORT      TERMINATION   WILDCARD
routes/nodejs-mongodb-example   nodejs-mongodb-example-wmeng.apps.0127-asd.qe.rhcloud.com             nodejs-mongodb-example   <all>                   None

NAME                                READY     STATUS    RESTARTS   AGE
po/mongodb-1-8b6k4                  1/1       Running   0          4m
po/nodejs-mongodb-example-1-build   0/1       Error     0          4m

NAME           DESIRED   CURRENT   READY     AGE
rc/mongodb-1   1         1         1         4m

Expected results:
po/nodejs-mongodb-example-1-build   0/1       Completed   0
po/nodejs-mongodb-example-2-c7wgz   1/1       Running     0

Comment 2 Ben Parees 2018-01-27 16:58:37 UTC
error: build error: Failed to push image: Get https://docker-registry.default.svc:5000/v1/_ping: http: server gave HTTP response to HTTPS client


your docker daemon is not setup w/ docker-registry.default.svc:5000 marked as an insecure registry.

Comment 5 errata-xmlrpc 2018-06-27 18:01:30 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-2018:2013


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