Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1361609

Summary: Yum changes arch of package if repository becomes out of sync
Product: Red Hat Enterprise Linux 7 Reporter: Terry Bowling <tbowling>
Component: yumAssignee: Michal Domonkos <mdomonko>
Status: CLOSED ERRATA QA Contact: Eva Mrakova <emrakova>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: dconsoli, emrakova, james.antill, mdomonko, pkovar, prsharma, vmukhame
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Fixed In Version: yum-3.4.3-156.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 15:05:56 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:
Bug Depends On:    
Bug Blocks: 1420851, 1465896, 1466368    
Description Flags
testrepo.repo none

Description Terry Bowling 2016-07-29 13:49:03 UTC
Description of problem:

yum is not honoring the preferred hardware architecture when updating packages.  For example, repository containing:

	Package  Arch   Version     Repository
	dummy.x86_64     1-1        testrepo
	dummy.i686       1-2        testrepo

Yum will install dummy-1-2.i686 because the version is newer, even though the x86_64 version is already installed.

This is true even when /etc/yum.conf has the following directives set:


It is understood that it is bad form to have the package versions/arch out of sync like this.  However, the concern is that in the event that a problem occurred and the repository *accidentally* became out of sync, the expectation is that yum should fail to warn of the issue rather than simply change arch of many packages potentially causing a disruption of service.

	# yum update dummy.x86_64
	testrepo       | 2.9 kB  00:00:00     
	Resolving Dependencies
	--> Running transaction check
	---> Package dummy.x86_64 0:1-1 will be updated
	---> Package dummy.i686 0:1-2 will be an update
	--> Finished Dependency Resolution
	Dependencies Resolved
	 Package            Arch              Version          Repository             Size
	 dummy              i686              1-2              testrepo              1.5 k
	Transaction Summary
	Upgrade  1 Package

Version-Release number of selected component (if applicable):

	RHEL 7.2

How reproducible:

Steps to Reproduce:
1.  yum install -y createrepo httpd

2.  systemctl start httpd

3.  Copy attached rpms (dummy-1-1.x86_64.rpm  dummy-1-2.i686.rpm) 
	to /var/www/html/testrepo

4.  Copy attached testrepo.repo into /etc/yum.repo.d/

5.  Add the following directives to /etc/yum.conf

6.  confirm the test repo configured
	yum repolist 

7.  confirm both packages available from repo
	yum list dummy

8.  Install dummy.  Note that it installs lower versioned, x86_64 package
	yum install dummy

9.  Update dummy.  Note that it installs the higher versioned, i686 package,
    even though x86_64 might be specified.

	yum update dummy.x86_64

Actual results:
Yum upgrades to dummy-1-2.i686.rpm, honoring the version number over the architecture.

Expected results:
	Yum, with the directives configured, would either generate an error or simply 
	not update the package since the $arch is different.
	dummy-1-1.x86_64.rpm would remain installed.

Additional info:

Comment 1 Terry Bowling 2016-07-29 13:51:43 UTC
Created attachment 1185564 [details]

Comment 2 Terry Bowling 2016-07-29 13:52:22 UTC
Created attachment 1185565 [details]

Comment 3 Terry Bowling 2016-07-29 13:54:13 UTC
Created attachment 1185566 [details]

Comment 4 Terry Bowling 2016-11-16 15:51:14 UTC
Note the follow BZs are possibly somewhat related, all involving the upgrades and new i686 (32 bit) version of OpenJDK.

bz1395397 - Bug: In-place upgrade installs wrong version of OpenJDK
bz1388520 - installing java-1.8.0-openjdk.i686 installs incorrect x86_64 dependencies
bz1361609 - Yum changes arch of package if repository becomes out of sync with 32bit OpenJDK

Comment 12 Valentina Mukhamedzhanova 2017-03-15 14:31:25 UTC
*** Bug 1428716 has been marked as a duplicate of this bug. ***

Comment 23 errata-xmlrpc 2018-04-10 15:05:56 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.