Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1328950 - In Containerized Cluster, openvswitch Not Being Upgraded to 3.2
In Containerized Cluster, openvswitch Not Being Upgraded to 3.2
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
3.2.0
Unspecified Unspecified
high Severity high
: ---
: 3.2.1
Assigned To: Devan Goodwin
Anping Li
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-20 13:25 EDT by Devan Goodwin
Modified: 2016-06-27 11:04 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-06-27 11:04:18 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1344 normal SHIPPED_LIVE Red Hat OpenShift Enterprise atomic-openshift-utils bug fix update 2016-06-27 15:03:23 EDT

  None (edit)
Description Devan Goodwin 2016-04-20 13:25:43 EDT
Description of problem:

When upgrading a 3.1 cluster on Atomic, openvswitch remains running 3.1.1.6.

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

Using latest openshift-ansible master, roughly around openshift-ansible-3.0.81-1


How reproducible:

Seems 100%.


Steps to Reproduce:
1. Install a 3.1 cluster on Atomic in AWS.
2. Enabled a 3.2 repository via some means.
3. Upgrade with inventory setting "openshift_image_tag=v3.2.0.14" or equivalent.

Actual results:

bash-4.2# docker ps
CONTAINER ID        IMAGE                             COMMAND                  CREATED             STATUS              PORTS               NAMES
bb08c35ec36a        openshift3/ose:v3.2.0.14          "/usr/bin/openshift s"   13 minutes ago      Up 13 minutes                           atomic-openshift-master
916f0defcc72        openshift3/node:v3.2.0.14         "/usr/local/bin/origi"   14 minutes ago      Up 14 minutes                           atomic-openshift-node
3aad1b559a52        openshift3/openvswitch:v3.1.1.6   "/usr/local/bin/ovs-r"   About an hour ago   Up About an hour                        openvswitch



Expected results:

The openvswitch container should also have been upgraded to a 3.2 version.


Additional info:

I don't think it is related, but I was using an image_tag lower than the latest 3.2 one available when this occurred. (it happened multiple times)
Comment 1 Devan Goodwin 2016-04-21 15:41:49 EDT
This may only surface if you specify openshift_image_tag=v3.1.1.6 for the initial install, which might point to a cached system fact issue.
Comment 2 Anping Li 2016-04-22 04:16:18 EDT
It seems  that is a duplicated bug with https://bugzilla.redhat.com/show_bug.cgi?id=1328950. the difference is that the latest version is v3.1.1.6 in this testing.
Comment 3 Anping Li 2016-04-22 04:18:22 EDT
(In reply to Anping Li from comment #2)
> It seems  that is a duplicated bug with
> https://bugzilla.redhat.com/show_bug.cgi?id=1328950. the difference is that
> the latest version is v3.1.1.6 in this testing.

Sorry, a copy error.
Another bug is https://bugzilla.redhat.com/show_bug.cgi?id=1326642
Comment 4 Devan Goodwin 2016-05-11 11:03:54 EDT
Fix pending here: https://github.com/openshift/openshift-ansible/pull/1859

I'm going to try to get someone to look at it today.
Comment 7 Anping Li 2016-06-08 04:24:15 EDT
Verified and pass, The openvswitch was tag as correct version after upgrade.
Comment 9 errata-xmlrpc 2016-06-27 11:04:18 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/RHBA-2016:1344

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