Bug 1369377 - Shouldn't include v3_2 upgrade playbook in openshift-ansible-playbooks-3.3.x
Summary: Shouldn't include v3_2 upgrade playbook in openshift-ansible-playbooks-3.3.x
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Devan Goodwin
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-23 09:09 UTC by Anping Li
Modified: 2017-08-24 20:48 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-24 20:48:23 UTC
Target Upstream Version:

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

Description Anping Li 2016-08-23 09:09:53 UTC 
Description of problem:
The v3_2 upgrade playbook should be moved from openshift-ansible-playbooks-3.3.x

Version-Release number of selected component (if applicable):
openshift-ansible-playbooks-3.3.13

How reproducible:
always

Steps to Reproduce:
1. install atomic-openshift-utils-3.3.13
2. ls /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_2
README.md  upgrade.retry  upgrade.yml



Actual results:

ls /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_2
README.md  upgrade.retry  upgrade.yml


Expected results:
No v3_2 upgrade playbook in openshift-ansible-3.3.x

Additional info:
Comment 1 Devan Goodwin 2016-08-23 12:09:04 UTC 
Bumping to UpcomingRelease.
Note You need to log in before you can comment on or make changes to this bug.