Bug 1251480
Summary: | "tag" in json doesnt work when used along with distro. | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Gowrishankar Rajaiyan <grajaiya> |
Component: | command line | Assignee: | beaker-dev-list |
Status: | CLOSED NOTABUG | QA Contact: | tools-bugs <tools-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 20 | CC: | grajaiya, mjia |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-14 05:59:46 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: | |
Embargoed: |
Description
Gowrishankar Rajaiyan
2015-08-07 12:28:23 UTC
Sorry, I don't understand what the bug is here. The JSON file you linked to is handled by the CI provisioner code, right?ios th What Beaker XML is it producing, and what is the problem you are seeing with it? "recipesets": [ { "arch": "x86_64", "bkr_data": { "name": "AppServer", "role": "Server" }, "distro": "rhel-7.2%", "hostrequire": [], "tag": [ "RTT_ACCEPTED" ], "variant": "Server" } ] produces: <distroRequires> <and> <distro_name op="like" value="rhel-7.2%"/> <distro_variant op="=" value="Server"/> <distro_arch op="=" value="x86_64"/> </and> </distroRequires> Please note the missing tag: 'RTT_ACCEPTED' Okay, does that mean the CI provisioner code is producing the wrong thing? Or is it invoking the bkr client with some options and *that* is producing the wrong XML? If so, what is the CI provisioner invoking? This is because the 7.2% is not supported in the Beaker API. (In reply to Gowrishankar Rajaiyan from comment #4) > This is because the 7.2% is not supported in the Beaker API. As mentioned by Ari at CID-376 I'm not clear what the bug is here. Is this still an issue? Not an issue anymore. |