Bug 1391325 – [3.5] openshift_pkg_version doesn't seem to work

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1391325 - [3.5] openshift_pkg_version doesn't seem to work

Summary:	[3.5] openshift_pkg_version doesn't seem to work

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Upgrade (Show other bugs)
Sub Component:
Version:	3.3.0
Hardware:	Unspecified Unspecified

Priority	high Severity urgent
Target Milestone:	---
Target Release:	3.5.z
Assigned To:	Scott Dodson
QA Contact:	Anping Li
Docs Contact:

URL:
Whiteboard:
Keywords:	NeedsTestCase

Depends On:
Blocks:	1449220 1449221
	Show dependency tree / graph

Reported:	2016-11-03 01:31 EDT by Jaspreet Kaur
Modified:	2017-05-17 13:38 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Because the upgrade playbooks upgraded packages in a serial manner rather than all at once yum dependency resolution would have installed the latest version available in the enabled repos rather than the requested version. The playbooks have been updated to upgrade all packages to the requested version at once which prevents yum from potentially upgrading to the latest version.
Story Points:	---
Clone Of:
Clones:	1449220 1449221 (view as bug list)
Environment:
Last Closed:	2017-05-17 13:38:17 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:1244	normal	SHIPPED_LIVE	Important: ansible and openshift-ansible security and bug fix update	2017-05-25 17:43:49 EDT

Groups: None (edit)

Description Jaspreet Kaur 2016-11-03 01:31:39 EDT

Description of problem: When migrating openshift from 3.2.1.17 to 3.3.0.32 by setting the openshift_pkg_version=-3.3.0.32 using ansible installer :
ansible-playbook -i /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_3/upgrade.yml It still upgrades to v 3.3.0.35

The result after migration + reboot :
[root@cdyi0538 ~]# openshift version
openshift v3.3.0.35
kubernetes v1.3.0+52492b4
etcd 2.3.0+git


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: Migrated to incorrect version


Expected results: It should have helped to migrate to correct version.


Additional info:

Comment 3 Vladislav Walek 2017-04-28 05:26:52 EDT

Hi,
raising the priority of the case, due the bug is causing unwanted/untested release deployed on production systems ( for customer ). Customer is running tests on latest version, but during the time new release is released. 
Thx

Comment 4 Scott Dodson 2017-05-09 08:27:08 EDT

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

Comment 6 Anping Li 2017-05-12 02:32:28 EDT

atomic-openshift-utils-3.5.69-1.git.0.61edbcb.el7.noarch
OCP can be upgraded from v3.4 to v3.5.5.5 when specified openshift_pkg_version=-3.5.5.5
OCP can be upgraded from v3.5.5.6 to v3.5.5.8 when specified openshift_pkg_version=-3.5.5.8.

So move bug  to verified.

Comment 8 errata-xmlrpc 2017-05-17 13:38:17 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:1244

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