Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1496372

Summary: [quick installer][3.7] No 3.7 upgrade entry in quick installer
Product: OpenShift Container Platform Reporter: liujia <jiajliu>
Component: Cluster Version OperatorAssignee: Scott Dodson <sdodson>
Status: CLOSED ERRATA QA Contact: liujia <jiajliu>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.7.0CC: aos-bugs, jokerman, mmccomas, sdodson, wmeng
Target Milestone: ---Keywords: Reopened
Target Release: 3.7.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openshift-ansible-3.7.9-1.git.35.36453c1.el7 Doc Type: Enhancement
Doc Text:
The quick installer now supports both major and minor upgrades to OCP 3.7.
Story Points: ---
Clone Of:
: 1525225 (view as bug list) Environment:
Last Closed: 2017-12-12 20:32:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1525225    

Description liujia 2017-09-27 08:30:34 UTC
Description of problem:
Run atomic-openshift-installer to upgrade ocp 3.6 to 3.7 with default installer.cfg.yml. But there is no 3.7 upgrade choice.

# atomic-openshift-installer upgrade

        This tool will help you upgrade your existing OpenShift installation.
        Currently running: openshift-enterprise 3.6

(1) Update to latest 3.6

Choose an option from above:

Version-Release number of the following components:
atomic-openshift-utils-3.7.0-0.128.0.git.0.89dcad2.el7.noarch
openshift-ansible-3.7.0-0.128.0.git.0.89dcad2.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Trigger upgrade with atomic-openshift-installer
2.
3.

Actual results:
No 3.7 upgrade entry in quick installer.

Expected results:
There should be a entry to choose 3.7 for 3.7 quick installer.

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 Scott Dodson 2017-10-11 15:24:22 UTC
We intend to remove the quick installer in 3.7.

Comment 2 liujia 2017-11-28 01:46:27 UTC
@Scott

It seems that quick installer should be supported in v3.7. QE think it should be the same for install and upgrade. Then, for this bug, maybe we need a hot fix asap.

Comment 3 Scott Dodson 2017-11-28 02:32:10 UTC
I believe the changes in https://github.com/openshift/openshift-ansible/pull/6274 should've addressed the upgrade as well. I'll work on verifying that.

Comment 4 Scott Dodson 2017-11-28 03:59:04 UTC
The previously referenced PR did not add upgrade support, I've added that here 

https://github.com/openshift/openshift-ansible/pull/6285

Comment 6 liujia 2017-11-28 08:08:18 UTC
Version:
atomic-openshift-utils-3.7.9-1.git.36.60dc0ea.el7.noarch

Steps:
1. Trigger upgrade with atomic-openshift-installer

# atomic-openshift-installer upgrade

        This tool will help you upgrade your existing OpenShift installation.
        Currently running: openshift-enterprise 3.6

(1) Update to latest 3.6
(2) Upgrade to next release: 3.7

Upgrade succeed.

Comment 7 liujia 2017-11-29 08:30:37 UTC
@Scott

Just find a missing issue about the choice.

1. Trigger upgrade with atomic-openshift-installer.

# atomic-openshift-installer upgrade

        This tool will help you upgrade your existing OpenShift installation.
        Currently running: openshift-enterprise 3.6

(1) Update to latest 3.6
(2) Upgrade to next release: 3.7


The choices were not correct. 3.7 installer can only upgrade to 3.7 but not 3.6. 

(1) Update to latest 3.7


Assign back.

Comment 9 Scott Dodson 2017-11-29 13:56:13 UTC
(In reply to liujia from comment #7)
> @Scott
> 
> Just find a missing issue about the choice.
> 
> 1. Trigger upgrade with atomic-openshift-installer.
> 
> # atomic-openshift-installer upgrade
> 
>         This tool will help you upgrade your existing OpenShift installation.
>         Currently running: openshift-enterprise 3.6
> 
> (1) Update to latest 3.6
> (2) Upgrade to next release: 3.7
> 
> 
> The choices were not correct. 3.7 installer can only upgrade to 3.7 but not
> 3.6. 
> 
> (1) Update to latest 3.7
> 
> 
> Assign back.

We can remove the entry, but it should in fact work just fine to upgrade to the latest 3.6 errata using these playbooks.

Comment 10 Scott Dodson 2017-12-12 20:32:15 UTC
The original bug here has been fixed. The fact that the 3.7 quick installer also allows you to upgrade to the latest 3.6 errata is a separate bug and I've cloned this.