| Summary: | numanodes tag did not work right | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Wayne Sun <gsun> |
| Component: | general | Assignee: | beaker-dev-list |
| Status: | CLOSED NOTABUG | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | dcallagh, hliu, mjia, rjoost |
| 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: | 2016-02-03 05:34:53 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
Wayne Sun
2016-01-20 10:18:07 UTC
Thanks for your report. Looks like there is a mistake in the hostrequires paramater. You can request either by: --hostrequire '<system><numanodes ..></system' which is the recommended way or by: --hostrequire 'numa_node_count >= 2' which is deprecated but still works. Would you mind to confirm? (In reply to Roman Joost from comment #1) > Thanks for your report. > > Looks like there is a mistake in the hostrequires paramater. You can request > either by: > > --hostrequire '<system><numanodes ..></system' > > which is the recommended way or by: > > --hostrequire 'numa_node_count >= 2' > > which is deprecated but still works. > > Would you mind to confirm? Both way you mentioned are working: # bkr workflow-simple --hostrequire="<system><numanodes op='>=' value='2'/></system>" --debug --distro="RHEL-7.2-20151030.0" --task="/distribution/dummy" --prettyxml --arch="x86_64" <job retention_tag="Scratch"> <whiteboard></whiteboard> <recipeSet priority="Normal"> <recipe ks_meta="" whiteboard=""> <distroRequires> <and> <distro_name op="=" value="RHEL-7.2-20151030.0"/> <distro_arch op="=" value="x86_64"/> </and> </distroRequires> <hostRequires> <and> <system> <numanodes op=">=" value="2"/> </system> </and> </hostRequires> <repos/> <partitions/> <task name="/distribution/install" role="STANDALONE"> <params/> </task> <task name="/distribution/dummy" role="STANDALONE"> <params/> </task> </recipe> </recipeSet> </job> Submitted: ['J:1197584'] # bkr workflow-simple --hostrequire='numa_node_count >= 2' --debug --distro="RHEL-7.2-20151030.0" --task="/distribution/dummy" --prettyxml --arch="x86_64" <job retention_tag="Scratch"> <whiteboard></whiteboard> <recipeSet priority="Normal"> <recipe ks_meta="" whiteboard=""> <distroRequires> <and> <distro_name op="=" value="RHEL-7.2-20151030.0"/> <distro_arch op="=" value="x86_64"/> </and> </distroRequires> <hostRequires> <and> <numa_node_count op=">=" value="2"/> </and> </hostRequires> <repos/> <partitions/> <task name="/distribution/install" role="STANDALONE"> <params/> </task> <task name="/distribution/dummy" role="STANDALONE"> <params/> </task> </recipe> </recipeSet> </job> Submitted: ['J:1197586'] So the problem is --hostrequire="numanodes >= 2" used to work but not working now. (In reply to Wayne Sun from comment #2) > So the problem is --hostrequire="numanodes >= 2" used to work but not > working now. Are you sure that has ever worked? What Beaker versions did you see it work/stop working? Maybe you were using it and by coincidence it was giving you machines with more than 1 NUMA node even though the filter was having no effect? We introduced the <numanodes/> filter, which must be enclosed in <system/>, in Beaker 0.10.1: https://git.beaker-project.org/cgit/beaker/commit/?id=12cb295834a207629862b88efa53f0b342a07abe Prior to that the only supported filter was <numa_node_count/>. (In reply to Dan Callaghan from comment #3) > (In reply to Wayne Sun from comment #2) > > So the problem is --hostrequire="numanodes >= 2" used to work but not > > working now. > > Are you sure that has ever worked? What Beaker versions did you see it > work/stop working? > > Maybe you were using it and by coincidence it was giving you machines with > more than 1 NUMA node even though the filter was having no effect? > > We introduced the <numanodes/> filter, which must be enclosed in <system/>, > in Beaker 0.10.1: > > https://git.beaker-project.org/cgit/beaker/commit/ > ?id=12cb295834a207629862b88efa53f0b342a07abe > > Prior to that the only supported filter was <numa_node_count/>. Ok, got it. Thanks for clarify this, I think this could be closed as NOTABUG now. |