Description of problem: As noted in https://bugzilla.redhat.com/show_bug.cgi?id=1093224#c5 , bkr machine-test (and other workflow commands) have a --machine and a --hostrequire switch. Now, if you specify both these, the job gets the following in <hostRequires> (for example): <hostRequires> <hostlabcontroller op="=" value="testlc.labcontroller"/> <hostname op="=" value="test.system"/> </hostRequires> This doesn't make a lot of sense, and we should just use the hostname specified by --machine and ignore the --hostrequire. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: The job XML only has : <hostRequires> <hostname op="=" value="test.system"/> </hostRequires> Additional info:
http://gerrit.beaker-project.org/#/c/3064/
Beaker 0.17.0 has been released.
Note that bug 1234323 came up with a valid case where --machine and --systype are both needed (contrary to the assumptions we made in this bug) so we will remove this code for ignoring the extra filter options.