Bug 1302970 - update script does not patch router if name is different from default
update script does not patch router if name is different from default
Product: OpenShift Container Platform
Classification: Red Hat
Component: Upgrade (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Brenton Leanhardt
Anping Li
: 1304943 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2016-01-29 02:51 EST by Evgheni Dereveanchin
Modified: 2016-02-29 07:57 EST (History)
6 users (show)

See Also:
Fixed In Version: openshift-ansible-3.0.40-1.git.1.4385281.el7aos
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-02-29 07:57:36 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Evgheni Dereveanchin 2016-01-29 02:51:24 EST
Description of problem:
The upgrade script is supposed to upgrade pods to latest versions, however names of the pods are hardcoded, so for example if a router is named differently (or there's several routers) it will not get patched.

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

How reproducible:

Steps to Reproduce:
1. install OpenShift Enterprise 3.1.0 and create a router named "r1"
3. deploy a router following the official documentation

the docs say the following:

To create a router if it does not exist:

$ oadm router <router_name> --replicas=<number> \
    --credentials='/etc/origin/master/openshift-router.kubeconfig' \

So the user can choose any name for the router, for example "test_router"

4. follow the upgrade process to 3.1.1


Actual results:
router pod is not updated since the ansible script will only upgrade it if the name is "router"

Expected results:
router updated regardless what its name is.
Alternatively, documentation is provided on how to patch routers manually.

Additional info:

Here's the playbook that does the patching
it's clearly visible that it will only patch the router if the deploymentConfig is named "dc/router"
Comment 1 Brenton Leanhardt 2016-02-02 10:09:43 EST
We definitely need to find a way to upgrade all routers and registries installed by oadm.  My thought it we could perform a query like this:

oc get pods --all-namespaces -l 'router'

...and then update the image spec appropriately.
Comment 2 Scott Dodson 2016-02-02 10:22:25 EST
I think that the approach we should take is to write a module that looks at all of the `oadm registry` or `oadm router` options of our current version of `oadm` then extracts those values if set from the currently defined registry and rotuer. It then re-generates the deployment config and service from the newly generated values and performs an additive only merge of the two and updates the appropriate objects.
Comment 3 Scott Dodson 2016-02-02 11:58:44 EST
Sorry, that's overly complex. It's simpler to, after upgrading the oadm binary, run `oadm router` to generate a default template. Then overwrite that with all values from the current DC and SVC.
Comment 4 Jason DeTiberus 2016-02-03 13:42:40 EST
If we are going to query all namespaces for the router label, we'll have to take care to only update ones that are using our images to avoid breaking a customized router instance.
Comment 5 Brenton Leanhardt 2016-02-08 11:14:33 EST
*** Bug 1304943 has been marked as a duplicate of this bug. ***
Comment 6 Brenton Leanhardt 2016-02-11 13:37:08 EST
This is currently being worked on here:

For QE, this will require a fair amount of testing.  I would suggest the following cases at a minimum:

* 3.0.z -> 3.1.1 upgrade
* 3.0.z -> upgrade using ansible directly and set openshift_pkg_version

Then for both of those scenarios test:

* zero routers
* default router, non-default named router (possibly in non-default namespace) and a "custom" router.  To create the custom router I have been launching another pod and simply giving it the router label.  The idea here is to make sure ansible _only_ updates pods using the haproxy router image from Red Hat
Comment 9 Anping Li 2016-02-15 01:17:50 EST
Verified and pass with atomic-openshift-utils-3.0.40.
Comment 11 errata-xmlrpc 2016-02-29 07:57:36 EST
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.


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