Bug 1388524 - [backport] (3.3) Failed to "oc new-app --search" at the offline environment disconnected to the Internet
Summary: [backport] (3.3) Failed to "oc new-app --search" at the offline environment d...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: oc
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.3.1
Assignee: Martin Milata
QA Contact: Dongbo Yan
Depends On: 1378647 1388522
Blocks: 1267746
TreeView+ depends on / blocked
Reported: 2016-10-25 14:48 UTC by Eric Rich
Modified: 2020-01-17 16:05 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When using oc new-app --search in environment where OpenShift could not reach Docker Hub oc new-app --search failed for any query. OpenShift now prints a warning and continues with what was found in other sources.
Clone Of: 1388522
Last Closed: 2016-12-07 20:58:47 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2915 0 normal SHIPPED_LIVE Important: atomic-openshift security and bug fix update 2016-12-08 01:58:10 UTC

Comment 1 Martin Milata 2016-10-27 17:51:42 UTC
Opened pull request: https://github.com/openshift/ose/pull/436

Comment 4 Dongbo Yan 2016-11-30 05:13:18 UTC
When the rpm build completed will verify this issue.

Comment 7 Dongbo Yan 2016-12-02 08:41:18 UTC
openshift v3.3.1.7
kubernetes v1.3.0+52492b4
etcd 2.3.0+git

Actual result:
# oc new-app --search docker.io/mariadb
W1202 03:39:48.722181   25221 dockerimagelookup.go:211] Docker registry lookup failed: Internal error occurred: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Docker images (oc new-app --docker-image=<docker-image> [--code=<source>])
  Registry: docker.io
  Tags:     latest

Comment 9 errata-xmlrpc 2016-12-07 20:58:47 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.


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