Bug 1321877

Summary: Beaker only accepts i386 as arch.
Product: [Retired] Beaker Reporter: Gowrishankar Rajaiyan <grajaiya>
Component: generalAssignee: beaker-dev-list
Status: CLOSED WONTFIX QA Contact: tools-bugs <tools-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: developCC: dcallagh, mjia, rjoost
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-29 23:55:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Gowrishankar Rajaiyan 2016-03-29 10:04:40 UTC 
Description of problem: Beaker does not accept i686 as architecture and only accepts i386.


Version-Release number of selected component (if applicable):
beaker-client-22.2-1.el7sed.noarch

How reproducible: Always


Steps to Reproduce:
1. Try provisioning a system with --arch as i686
2.
3.

Actual results: No matches found for i686 arch.


Expected results: Should match with i386 systems.


Additional info:
This is important for CI since the brew task repos have i686 in their repo URL and we are unable to use the arch variable from the CI message.
Comment 1 Dan Callaghan 2016-03-29 23:55:48 UTC 
The 32-bit Intel x86 ISA is called "i386" in Beaker, which matches the name of the architecture as it appears in the RHEL and Fedora tree metadata as well.

Nowadays RPMs will have i686 instead of i386, to indicate that they were compiled targetting the Pentium Pro extensions, but that distinction isn't really meaningful to Beaker. We don't want people to have to say "this system supports i386, i586, i686, ..." plus all the other variations that have been used over the years.

This is similar to POWER where the ISA is called "ppc64" in Beaker and in tree metadata, there's no attempt to distinguish between all the POWER versions in the architecture string itself.

If you have a script that needs to deal with "i686" because it's looking at package architectures, just hardcode a mapping back to "i386" which is the architecture you want to actually install.