Bug 535382 (RHQ-2084)

Summary: missing the "none" architecture
Product: [Other] RHQ Project Reporter: John Mazzitelli <mazz>
Component: DatabaseAssignee: RHQ Project Maintainer <rhq-maint>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: cwelton, jshaughn
Target Milestone: ---Keywords: SubBug
Target Release: ---Flags: cwelton: needinfo? (ccrouch)
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-2084
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-06 16:31:22 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 535381, 565628    

Description John Mazzitelli 2009-05-12 19:25:00 EDT
need to add to the dbsetup/dbupgrade scripts a new row in the RHQ_ARCHITECTURE table - the "none" architecture.
Comment 1 John Mazzitelli 2009-05-13 02:44:57 EDT
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.
Comment 2 Corey Welton 2009-08-14 15:49:27 EDT
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.

Comment 3 Red Hat Bugzilla 2009-11-10 15:57:26 EST
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2084
Comment 4 wes hayutin 2010-02-16 11:57:49 EST
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

new = Tracking + FutureFeature + SubBug
Comment 5 wes hayutin 2010-02-16 12:02:43 EST
making sure we're not missing any bugs in rhq_triage
Comment 6 Corey Welton 2010-08-25 11:54:49 EDT
Charles, this one's on you per prioritization of platform plugin-related issues.