Bug 459811

Summary: Request to include em64t arch support
Product: [Retired] Red Hat Network Reporter: Pradeep Kilambi <pkilambi>
Component: RHN/BackendAssignee: Sebastian Skracic <sskracic>
Status: CLOSED CURRENTRELEASE QA Contact: venkat <vambati>
Severity: medium Docs Contact:
Priority: medium    
Version: RHN StableCC: acase, bugzilla, erobertstad, flakrat, ggainey, juanino, jwilleford, kabbott, knox, peterd, rhn-bugs, tao, weqaar.janjua
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: US=4854
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-14 13:42:11 UTC Type: ---
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: 453832, 642708    
Attachments:
Description Flags
em64t none

Description Pradeep Kilambi 2008-08-22 15:41:14 UTC
Description of problem:

RHN currently doesn't support em64t arch. This is causing package profile syncs to fail with em64t arch package clients. We jus need to make sure the db treats em64t as a valid arch and we should be good. Should be a easy fix.

Thanks,

Comment 2 Clifford Perry 2009-02-20 22:18:55 UTC
*** Bug 453832 has been marked as a duplicate of this bug. ***

Comment 3 Mike Hanby 2009-07-09 21:29:46 UTC
Has there been any work around identified for this issue?

I have many systems that have the following Intel compiler packages installed, and all of them are failing to update from the satellite because they are unable to complete an 'up2date --package' or equivalent:

intel-iidbe101015-10.1.015-1
intel-icce101015-10.1.015-1
intel-iforte101015-10.1.015-1
intel-mkl100014-10.0p-014
intel-isubhe101015-10.1.015-1

Unfortunately the compilers are used regularly and can't be removed. Also, I can't seem to find the "rhn user story: 42956" listed above, the link is dead and searching doesn't find anything.

This is with
up2date-4.8.1-33.el4

Hoping someone has a workaround. Thanks

Comment 5 Weqaar A. Janjua 2009-09-16 14:46:58 UTC
EM64T is just a variant of X86_64, you seem to have ICC (Intel C Compiler) for EM64T (specific) installed, see output from:

rpm -qa --qf "%{n}-%{arch}\n"|grep em64t

The right way to go about is to edit the file: 
“/usr/share/rhn/up2date_client/rpmUtils.py” 

Insert the line, in first few import statements:

import platform

Edit line 159 of that file to include the un-recognized architecture (you won't find RPMs for EM64T) - for remove “arch” rpm TAG from package list, in our case “em64t”:

if arch != platform.machine():
    pkg_list.append([name, version, release, epoch])
elif arch:
    pkg_list.append([name, version, release, epoch, arch])

(take care of the correct indentation, its Python!)

Note that this may be overriden with the update to this file.

Comment 11 Sebastian Skracic 2010-10-14 10:40:48 UTC
dbchange provided in cc2e23582be4fe3218ea986988942644850be8e2.

Comment 12 Sebastian Skracic 2010-10-14 11:25:05 UTC
dbchange successfully applied to webdev.

Comment 14 Sebastian Skracic 2010-10-20 13:14:19 UTC
The rest of the dbchange is in 70b6ba9d6af2bb96cd04d6356820c9f174dd44ef, also available on webdev.

Comment 15 venkat 2010-10-20 18:42:35 UTC
Created attachment 454640 [details]
em64t

emt64t

Comment 16 venkat 2010-10-20 18:44:04 UTC
verified in webdev with the following system : voola.fjs-0-06.10202010

and the attchment shows the package with em64t architecture.

Comment 17 Karl Abbott 2011-01-13 13:39:31 UTC
venkat,

When will this change go live?

Karl

Comment 18 venkat 2011-01-14 13:41:11 UTC
it went out as part of 5.2.6 release