Bug 235214 - throw reasonable xmlrpc fault on invalid arch names
throw reasonable xmlrpc fault on invalid arch names
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Other (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bryan Kearney
Mike Orazi
Depends On:
Blocks: 239809
  Show dependency treegraph
Reported: 2007-04-04 11:46 EDT by James Bowes
Modified: 2013-01-10 04:52 EST (History)
3 users (show)

See Also:
Fixed In Version: 5.0.2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-25 11:15:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description James Bowes 2007-04-04 11:46:32 EDT
~50% of all unhandled exceptions in production coming from python are from us
not having an entry for em64t as a possible package arch. Add it.
Comment 1 James Bowes 2007-04-12 10:50:41 EDT
On second thoughts, dont add it, because it's not valid (its just x86_64)
throw an invalid arch fault or something.
Comment 2 Bret McMillan 2007-05-11 11:40:33 EDT
+1 to throwing a reasonable fault.
Comment 3 James Bowes 2007-05-22 13:23:54 EDT
Ok, so now if you attempt to sync up a package profile with a package that has
an odd arch, we return fault 45.
Comment 4 James Bowes 2007-06-04 10:40:30 EDT
A quick n' dirty way to test this is to append a package with a spurious arch to
your package profile, like:
   pkg_list.append(['foobar', '1', '1', '', 'em64t'])
at line 173 in /usr/share/rhn/up2date_client/rpmUtils.py

Then use rhnreg_ks and note the informative error message.
Comment 6 James Bowes 2007-07-25 11:15:52 EDT
rhn502 released.

Note You need to log in before you can comment on or make changes to this bug.