Bug 1539566 - After upgrade non-ha 3.7 env to 3.9, version info on web console doesn't update automatically.
Summary: After upgrade non-ha 3.7 env to 3.9, version info on web console doesn't upda...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.9.0
Assignee: Samuel Padgett
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-29 08:23 UTC by Yanping Zhang
Modified: 2018-03-27 09:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-05 12:57:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.9 RPM Release Advisory 2018-03-28 18:06:38 UTC

Description Yanping Zhang 2018-01-29 08:23:59 UTC
Description of problem:
After upgrade non-ha 3.7 env to 3.9, check openshift version on web console, it shows 3.8 version. After restart master service, OpenShift Web Console version shows v3.9.0-0.31.0.0, but the openshift master version on web console is still 3.8. Then delete web pod, after new web pod running, the openshift master version shows 3.9.

Version-Release number of selected component (if applicable):
v3.7.27 -> v3.9.0-0.31.0
ansible-2.4.2.0-2.el7.noarch
openshift-ansible-3.9.0-0.31.0.git.0.e0a0ad8.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.Upgrade non-ha 3.7 env to 3.9 in two phases(upgrade_control_plane + upgrade_nodes). Check version info on about page.
2. Restart master service, then check version info on about page again.
# systemctl restart atomic-openshift-master-api.service
3. Redeploy web pod.(Delete the web pod, a new web pod becomes running), check version info on about page again.

Actual results:
1.It show 3.8 version:
OpenShift Master:
    v3.8.32
Kubernetes Master:
    v1.8.5+440f8d36da 

2.It show 3.8 master version and 3.9 web console version:
OpenShift Master:
v3.8.32
Kubernetes Master:
v1.8.5+440f8d36da
OpenShift Web Console:
v3.9.0-0.31.0.0

3.Master version becomes 3.9 now:
OpenShift Master:
v3.9.0-0.31.0
Kubernetes Master:
v1.9.1+a0ce1bc657
OpenShift Web Console:
v3.9.0-0.31.0.0

Expected results:
1.The version info on about page should be correct after upgrade, no need to restart master service and redeploy web pod.

Additional info:

Comment 2 openshift-github-bot 2018-01-30 20:14:35 UTC
Commits pushed to master at https://github.com/openshift/origin-web-console

https://github.com/openshift/origin-web-console/commit/e5f23ed1d54610db3e94bf2ecc5eb2c0bdcd6e31
Bug 1539566 - Request server version on about page load

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1539566

https://github.com/openshift/origin-web-console/commit/c2e22bb7ea0e4d36d2b61277fdaef7efe73e5c5d
Merge pull request #2734 from spadgett/version

Automatic merge from submit-queue.

Bug 1539566 - Request server version on about page load

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1539566

/assign @jwforres

Comment 4 Yanping Zhang 2018-02-05 10:07:51 UTC
After upgrade from OCP 3.7.27 to OCP 3.9, and restart master service(https://bugzilla.redhat.com/show_bug.cgi?id=1512382), then check version on web console, now openshift master version is updated on about page automatically, no need to delete web pod to get new version.
The bug has been fixed, so move it to Verified.


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