Bug 607112 - bkr workflow-simple has no client and server sepcification for arch option
Summary: bkr workflow-simple has no client and server sepcification for arch option
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Community
Component: command line   
(Show other bugs)
Version: 0.5
Hardware: All
OS: Linux
low
medium vote
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-23 09:26 UTC by Aleš Mareček
Modified: 2012-10-04 04:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-10-04 04:17:31 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Aleš Mareček 2010-06-23 09:26:50 UTC
Description of problem:
There is no option for using specific architectures for client and server. Let say we need to test problem on s390x on server side with all architectures on clients' sides. bkr workflow-simple has only --arch option for both.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
  
Actual results:
only --arch option for both

Expected results:
--clientarch and --serverarch (or something like this)

Additional info:
It could be also nice to have comma-separated architectures like --serverarch=i386,x86_64,... instead of --serverarch=i386 --serverarch=x86_64 but I didn't see concept and don't know that --arch --arch ... is wanted.

Comment 1 Dan Callaghan 2012-10-04 04:17:31 UTC
I think this is solved by workflow-tomorrow.


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