Bug 1284013 - Ansible upgrade from 3.0.2 -> 3.1 fails due to deployment_type = enterprise
Summary: Ansible upgrade from 3.0.2 -> 3.1 fails due to deployment_type = enterprise
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-20 14:32 UTC by Matthew Davis
Modified: 2015-11-21 21:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-21 21:54:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Matthew Davis 2015-11-20 14:32:04 UTC
Description of problem:

In the 3.0 docs, deployment_type is set to 'enterprise'. However in 3.1, the ansible upgrade scripts expect deployment_type to be either origin or openshift-enterprise.

3.0 Ansible Install Doc - https://access.redhat.com/documentation/en/openshift-enterprise/3.0/installation-and-configuration/chapter-2-installing#advanced-installation

3.1 Ansible Install Doc - https://access.redhat.com/documentation/en/openshift-enterprise/3.1/installation-and-configuration/chapter-2-installing#advanced-installation


How reproducible:
Everytime


Suggestion: Include 'enterprise' in the ansible upgrade playbook.

Comment 1 Matthew Davis 2015-11-20 14:33:02 UTC
Suggestion should have read:

Include 'enterprise' as an allowed deployment_type in the ansible upgrade playbook.

Comment 2 Scott Dodson 2015-11-20 14:56:43 UTC
The switch from enterprise to 'openshift-enterprise' is mandatory when upgrading from 3.0 to 3.1 due to the significant change to how we deliver the product.

I've added an entry to the documentation mentioning that change is required when you use ansible directly.

https://github.com/openshift/openshift-docs/pull/1236


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