Bug 22698

Summary:	up2date does not function on Sparc
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <luc.girardin>
Component:	up2date	Assignee:	Preston Brown <pbrown>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jay Turner <jturner>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.2	CC:	benl, gafton, notting, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	sparc64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-07-10 15:12:38 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:

Description Need Real Name 2000-12-21 22:49:46 UTC

up2date 2.1.7 on a sparc64-based machine reports the following error:
There was a fatal error communicating with the server. The message was:
Invalid Architechture and OS release combination.

Comment 1 Bill Nottingham 2000-12-22 05:22:32 UTC

Try running 'sparc32 up2date'; does that work?

Comment 2 Need Real Name 2000-12-22 07:11:37 UTC

No, running up2date through sparc32 results exactly in the same problem.

Comment 3 Preston Brown 2000-12-27 21:54:49 UTC

Cristian:  Please enable sparc and sparc64 for Red Hat Linux 6.2 ASAP.

Comment 4 Cristian Gafton 2001-02-20 01:33:49 UTC

Assigned QA to jturner

Comment 5 Preston Brown 2001-02-26 23:43:50 UTC

fixed.

Comment 6 Need Real Name 2001-02-27 08:29:59 UTC

up2date does still not function on sparc64 architecture. up2date continuously complains with the usual "Invalid Architechture and OS release 
combination" error message.

Comment 7 Ben Levenson 2001-07-10 00:37:34 UTC

Reopening....
up2date-2.5.4-0.6.x
up2date-gnome-2.5.4-0.6.x

up2date still broken on sparc64:
   ERROR: Invalid Architecture and OS release combination
   INFO: Release 6.2 on sparc64

FWIW, verified behavior w/ sparc32 and --nox....

Comment 8 Ben Levenson 2001-07-10 00:52:38 UTC

Here are the entire contents of /var/log/up2date:

[Mon Jul  9 20:35:00 2001] up2date Adding /usr/share/rhn/RPM-GPG-KEY to keyring
[Mon Jul  9 20:35:00 2001] up2date /usr/bin/gpg --import
/usr/share/rhn/RPM-GPG-KEY >/dev/null 2>&1
[Mon Jul  9 20:35:00 2001] up2date Opening rpmdb in /var/lib/rpm/ with option 0
[Mon Jul  9 20:35:00 2001] up2date getAvailablePackageList from network
[Mon Jul  9 20:38:07 2001] up2date Opening rpmdb in /var/lib/rpm/ with option 0
[Mon Jul  9 20:38:07 2001] up2date getAvailablePackageList from network
[Mon Jul  9 20:40:32 2001] up2date Opening rpmdb in /var/lib/rpm/ with option 0
[Mon Jul  9 20:40:32 2001] up2date getAvailablePackageList from network
[Mon Jul  9 20:42:03 2001] up2date Opening rpmdb in /var/lib/rpm/ with option 0
[Mon Jul  9 20:42:03 2001] up2date getAvailablePackageList from network

Don't know if this helps, but here is some info from
/etc/sysconfig/rhn/systemid:
...
<member>
<name>description</name>
<value><string>6.2 running on sparc64</string></value>
</member>
<member>
<name>os_release</name>
<value><string>6.2</string></value>
</member>
<member>
<name>architecture</name>
<value><string>sparc64</string></value>
</member>
...
<member>
<name>operating_system</name>
<value><string>Red Hat Linux</string></value>
</member>
<member>
<name>profile_name</name>
<value><string>ultra2.test.redhat.com</string></value>
</member>

Comment 9 Ben Levenson 2001-07-10 15:12:32 UTC

Fixed. 
I guess this is technically the wrong component. Should be
filed against product Red Hat Network not Red Hat Linux...
Server-side issue...