Bug 1343681

Summary:	imagestream tags that follow another tag have the wrong value
Product:	OpenShift Online	Reporter:	Ben Parees <bparees>
Component:	Image Registry	Assignee:	Maciej Szulik <maszulik>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.x	CC:	aos-bugs, dakini, maszulik, vdinh, xtian
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1355779 (view as bug list)		Environment:
Last Closed:	2016-10-04 13:07:03 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:
Embargoed:
Bug Depends On:
Bug Blocks:	1355779

Description Ben Parees 2016-06-07 16:37:39 UTC

Description of problem:
online has two nodejs tags defined: 0.10 and latest

the latest tag follows the 0.10 tag, but has a different image id value, as seen here, after import-images is run:
https://gist.github.com/bparees/12a6a6b25a3ea93e87690d69ababfa3a

the values should be the same (the 0.10 value is the correct one).

Comment 1 Maciej Szulik 2016-06-09 18:52:20 UTC

Fixed in https://github.com/openshift/origin/pull/9258

Comment 2 openshift-github-bot 2016-06-15 18:47:54 UTC

Commits pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/6dd1c697715d04e9e4b7ba6741a4b40c0673eec1
Bug 1343681 - Fix tagsChanged logic

https://github.com/openshift/origin/commit/30c509f7c19528145eaaaccc9ae3bbb15bfe1026
Merge pull request #9258 from soltysh/bug1343681

Merged by openshift-bot

Comment 3 mdong 2016-06-21 07:53:59 UTC

Verified against dev-preview-stg

Comment 4 Vu Dinh 2016-07-11 21:31:26 UTC

Hi Ming,

Can you provide a bit of details how did you verify this issue again dev-preview-stg cluster? As far as I recall, this issue requires a master upgrade in order to fix the issue and this code fix only exists on OSE 3.3.0+ while the master on STG cluster is atomic-openshift-master-3.2.1.3-1.git.0.dfa4ad6.el7.x86_64 (OSE 3.2.1) which shouldn't have the fix.

Thanks in advance,
Vu

Comment 5 mdong 2016-07-12 08:58:51 UTC

(In reply to Vu Dinh from comment #4)
> Hi Ming,
> 
> Can you provide a bit of details how did you verify this issue again
> dev-preview-stg cluster? As far as I recall, this issue requires a master
> upgrade in order to fix the issue and this code fix only exists on OSE
> 3.3.0+ while the master on STG cluster is
> atomic-openshift-master-3.2.1.3-1.git.0.dfa4ad6.el7.x86_64 (OSE 3.2.1) which
> shouldn't have the fix.
> 
> Thanks in advance,
> Vu

I use this command: #oc get is/nodejs -n openshift -o yaml, then check image id to verify this bug.