Rather than add a new arch, if arch is "none" we should consider manually switching it to be our standard "noarch". We hardcode "noarch" in a few places in the code when we are talking about a arch-independent package. So we might want to just replace "none" with noarch before querying/inserting in RHQ_ARCHITECTURE.

I don't think handling this as a noarch (see sub-bug) is the correct thing to do -- noarch means something specific, i.e., a package that is arch-agnostic. A return of "(none"), however is indicative that the rpm provides nothing for the arch value.  I think if we were to file  rpms that return an arch as "(none)" from the rpm output as noarch, it might cause other issues down the road. 

A possible solution down the road might be to dynamically generate all arch types that exist on a system, rather than store a static list of them in the RHQ_ARCHITECTURE table. Something like

`rpm -qa --queryformat "%{ARCH}\n"|sort|uniq`

...would return a list of all arches that exist on any given system.  We could then store these in a db record for each inventoried system. Alternately, we could continually populate RHQ_ARCHITECTURE  with this data as more arches are discovered. This would keep us from necessarily having to update the table with one-offs any time a new arch is discovered, and would keep us from throwing errors if something unexpected comes our way.

This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2084

Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug

making sure we're not missing any bugs in rhq_triage

Charles, this one's on you per prioritization of platform plugin-related issues.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days