Bug 1391931

Summary:	please make sure that 7.2 EUS ppc64le repository doesn't have dist-tag collisions which would result into consumption of older update
Product:	Red Hat Enterprise Linux 7	Reporter:	Lubos Kocman <lkocman>
Component:	ksh	Assignee:	Siteshwar Vashisht <svashisht>
Status:	CLOSED ERRATA	QA Contact:	Jan Kepler <jkejda>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.2	CC:	isenfeld, jkejda, kdudka, release-test-team-automation
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	ksh-20120801-34.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1391930
Clones:	1421198 1421201 (view as bug list)		Environment:
Last Closed:	2017-08-01 16:26:55 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:	1391930
Bug Blocks:	1421198, 1421201

Description Lubos Kocman 2016-11-04 12:24:21 UTC

Individually cloning original tracker bug for affected components

+++ This bug was initially created as a clone of Bug #1391930 +++

Description of problem:

Hello team

Brano found an issue with ksh. What happened is that we've released "update" of ksh in 7.2 GA (pushed from compose) while there was already nvr with higher version !BUT dist-tag which is < than el7. Which prevents customers from automatically update build with highest version.


I highly recommend to bump these builds and make sure that customer can install lastest update. And releas eus errata fixing these issues. Other releases does not seem to be affected.

This most likely happened because of missing "version bump" after ppc64le merge.

ksh-20120801-22.ael7b_1.3.ppc64le.rpm
ksh-20120801-22.el7_1.2.ppc64le.rpm

Lubos

Comment 6 Kamil Dudka 2017-02-13 07:37:06 UTC

Is this a duplicate of bug #1391930?

Comment 8 errata-xmlrpc 2017-08-01 16:26:55 UTC

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.

https://access.redhat.com/errata/RHBA-2017:1936