Bug 1463598 - [3.3]Docker should be updated to allowable version when upgrade docker
[3.3]Docker should be updated to allowable version when upgrade docker
Status: CLOSED WONTFIX
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
3.3.1
Unspecified Unspecified
medium Severity medium
: ---
: 3.3.1
Assigned To: Scott Dodson
Anping Li
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-21 05:49 EDT by liujia
Modified: 2017-08-21 22:41 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-21 08:42:36 EDT
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)

  None (edit)
Description liujia 2017-06-21 05:49:20 EDT
Description of problem:
Run docker upgrade playbook to upgrade docker-1.10 to the max allowable version, upgrade succeed with docker was upgrade to docker-1.12. But for ocp3.3, we should protect docker's version is compatible with product version. So ansible playbook should handle docker-excluder before upgrade docker just like upgrade ocp.

Version-Release number of selected component (if applicable):
atomic-openshift-utils-3.3.97-1.git.0.0cbc4a5.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. Install ocp3.3 with docker-1.10.
2. No docker-excluder installed or docker-excluder was disabled.
3. Upgrade docker
# ansible-playbook -i hosts /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/docker/upgrade.yml

Actual results:
Docker was updated to latest 1.12.

Expected results:
Docker should be updated to max allowable version.

Additional info:
Comment 2 liujia 2017-08-21 22:41:58 EDT
I think,customer may have small chance to run docker upgrade playbook independently, so I think wonfix is acceptable for this bug.

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