Bug 1322339 - needn't pull ose and node images for rpm upgrade
Summary: needn't pull ose and node images for rpm upgrade
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Brenton Leanhardt
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-30 10:36 UTC by Anping Li
Modified: 2017-08-25 15:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-25 15:51:53 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Anping Li 2016-03-30 10:36:20 UTC 
Description of problem:
Upgrade pull openshift3/ose and openshift3/node during upgrade on the rpm environment. These packages are useless for rpm installation. 


Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.0.67

How reproducible:
always

Steps to Reproduce:
1. install ose 3.1 using rpm installation
2. ansible-playbook -i config/oserpm /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_1_to_v3_2/upgrade.yml | tee upgrade.log
3. check the upgrade.logs

Actual results:
openshift3/ose and openshift3/node were pulled during upgrade

Expected results:


Additional info:
Comment 1 Brenton Leanhardt 2016-03-30 12:18:07 UTC 
I definitely know it's not strictly necessary but for now I'm doing this for simplicity's sake.  My hope is to solve the problem of pulling images from authenticated registries and the remove this code entirely.
Note You need to log in before you can comment on or make changes to this bug.