Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1395380 - [3.3] ocp version of 'cluster up' will instantiate centos-based community images
[3.3] ocp version of 'cluster up' will instantiate centos-based community images
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Command Line Interface (Show other bugs)
3.4.0
All All
unspecified Severity medium
: ---
: ---
Assigned To: Corey Daley
Wenjing Zheng
:
Depends On:
Blocks: 1419784
  Show dependency treegraph
 
Reported: 2016-11-15 15:50 EST by Cesar Wong
Modified: 2017-02-07 10:19 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, running `oc cluster up` using OCP binaries would pull images from the Origin community rather than using OCP images. This has been changed to use OCP images.
Story Points: ---
Clone Of:
: 1419784 (view as bug list)
Environment:
Last Closed: 2017-01-26 15:42:25 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0199 normal SHIPPED_LIVE OpenShift Container Platform 3.3.1.11 and 3.2.1.23 bug fix update 2017-01-26 20:41:56 EST

  None (edit)
Description Cesar Wong 2016-11-15 15:50:39 EST
Description of problem:
The enterprise version of cluster up should instantiate RHEL-based image streams by default. It is currently instantiating centos-based image streams.

Version-Release number of selected component (if applicable):
v3.4

How reproducible:
Always

Steps to Reproduce:
1. Run 'oc cluster up' with OCP version of binary
2. Inspect image streams created with 'oc get is -n openshift'

Actual results:
Images are centos-based images

Expected results:
Images are RHEL-based images
Comment 1 Cesar Wong 2017-01-04 09:40:35 EST
Corey, sending this one your way. We need to change which imagestreams we import when running in OCP
Comment 2 Corey Daley 2017-01-04 12:05:04 EST
Submitted the following pull requests to resolve this issue in 3.3, 3.4, and 3.5

https://github.com/openshift/ose/pull/526
https://github.com/openshift/ose/pull/527
https://github.com/openshift/ose/pull/528
Comment 3 Corey Daley 2017-01-19 11:44:40 EST
All 3 pull requests have been merged, moving to QA
Comment 4 Dongbo Yan 2017-01-20 01:20:12 EST
Verified

$oc cluster up --image="brew-.../openshift3/ose"  --version="v3.3"
$oc cluster up --image="brew-.../openshift3/ose"  --version="v3.4"
$oc cluster up --image="brew-.../openshift3/ose"  --version="v3.5"

All images are RHEL-based images in imagestream
Comment 6 errata-xmlrpc 2017-01-26 15:42:25 EST
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/RHBA-2017:0199
Comment 7 Steve Kuznetsov 2017-02-07 10:19:48 EST
Once we pick up the ldflag change [1] in the OSE rebase we will need to provide the correct envars [2] during the build and we should be good here.

[1] https://github.com/openshift/origin/pull/12758/commits/5237fda6a1f1fc0ca770ac04071e07ab30b8de2a
[2] OS_IMAGE_PREFIX=openshift3/ose
    OS_BUILD_LDFLAGS_DEFAULT_IMAGE_STREAMS=rhel7

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