Bug 1574682

Summary: Image with tag "v3.9.25" contains version "3.9.14"
Product: OpenShift Container Platform Reporter: Mauricio Magnani <mmagnani>
Component: Management ConsoleAssignee: Samuel Munilla <smunilla>
Status: CLOSED WONTFIX QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.9.0CC: aos-bugs, jmalde, jokerman, jupierce, mmccomas, smunilla, spadgett, yapei
Target Milestone: ---   
Target Release: 3.9.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-11 18:09:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mauricio Magnani 2018-05-03 20:33:33 UTC
### Description of problem ###

IHAC asking about why the difference between the tag and the RPM version.

He said that's pretty non-intuitive (why wouldn't you version bump the RPM package, even if there wasn't a minor change)?

The docker image is 3.9.25, yet the web console RPM within 3.9.25 image is really 3.9.14.

Version-Release number:


## Steps to Reproduce ##

# openshift version
openshift v3.9.25
kubernetes v1.9.1+a0ce1bc657
etcd 3.2.16

# oc rsh webconsole-c9cf7f469-z9hnn 
sh-4.2$  rpm -qa *console*

Check the package at https://access.redhat.com/containers/?tab=package-list#/registry.access.redhat.com/openshift3/ose-web-console/images/v3.9.25-1

Thanks in advance

Comment 1 Yadan Pei 2018-05-04 02:47:54 UTC
Per https://bugzilla.redhat.com/show_bug.cgi?id=1570581#c1, this should be a special case

Comment 2 Samuel Padgett 2018-05-04 16:08:37 UTC
Justin, can you help us with this?

Comment 3 Seth Jennings 2018-05-07 14:11:30 UTC
*** Bug 1575451 has been marked as a duplicate of this bug. ***

Comment 8 Samuel Munilla 2018-09-11 18:09:18 UTC
While the v3.9.25 image does have the incorrect rpm, we do not have the ability to go back and change already released images.

This issue has been confirmed as corrected in subsequent releases.