Description of problem: Openshift-web-console-pods after upgrading the cluster from 3.9.14 to 3.9.25 shows v3.9.14 as the OCP version which is incorrect. OpenShift Master: v3.9.25 Kubernetes Master: v1.9.1+a0ce1bc657 OpenShift Web Console: v3.9.14 oc describe pod webconsole-c9cf7f469-9lt72|grep Image: Image: registry.access.redhat.com/openshift3/ose-web-console:v3.9.25 But inside the container the RPM looks to be still 3.9.14 $ oc rsh webconsole-c9cf7f469-9lt72 rpm -q atomic-openshift-web-console atomic-openshift-web-console-3.9.14-1.git.229.04c20c2.el7.x86_64 Version-Release number of selected component (if applicable): OpenShift Master: v3.9.25 How reproducible: Steps to Reproduce: 1.Install a OCP cluster of version v3.9.25 or upgrade the cluster from OCP v3.9.14 to v3.9.25 2. Get the web-console pods up and running, 3. Run the command 'oc rsh webconsole-c9cf7f469-9lt72 rpm -q atomic-openshift-web-console' Actual results: Openshift web-console pods shows the wrong version. Expected results: Openshift web-console pods should show the new and updated version of the cluster. Additional info: From the container catalog it seems that v3.9.25-1 and v3.9.25 are both using 'atomic-openshift-web-console-3.9.14-1.git.229.04c20c2.el7.x86_64' as the web-console package. https://access.redhat.com/containers/?tab=package-list#/registry.access.redhat.com/openshift3/ose-web-console/images/v3.9.25-1
confirmed $ docker run registry.access.redhat.com/openshift3/ose-web-console:v3.9.25 rpm -q atomic-openshift-web-console atomic-openshift-web-console-3.9.14-1.git.229.04c20c2.el7.x86_64 *** This bug has been marked as a duplicate of bug 1574682 ***