Bug 1426210
Summary: | peer roles should not include roles of different tasks | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Jan Tluka <jtluka> |
Component: | scheduler | Assignee: | beaker-dev-list |
Status: | CLOSED NOTABUG | QA Contact: | tools-bugs <tools-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | develop | CC: | mjia, tklohna |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-07-29 16:58:10 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
Jan Tluka
2017-02-23 12:26:43 UTC
(In reply to Jan Tluka from comment #0) > This looks like a bug in roles fetching for a task. The roles should be > fetched from the tasks of same name only. What makes you say this? The roles have always been based on the TESTORDER, each task will see the role variables for the corresponding task in the same position in each recipe. It has never been limited to tasks of the same name as far as I know. In position 10 of your example you have /distribution/beaker/beah/misc/sync in the host recipe. Can you just use /distribution/dummy there instead with role=STANDALONE to avoid the syncing behaviour? And then let them sync on the start of task 11? (In reply to Dan Callaghan from comment #1) > (In reply to Jan Tluka from comment #0) > > This looks like a bug in roles fetching for a task. The roles should be > > fetched from the tasks of same name only. > > What makes you say this? Hi Dan, I think lack of some deeper documentation for this feature. Not sure why I thought it worked this way. Anyway ... > The roles have always been based on the TESTORDER, each task will see the > role variables for the corresponding task in the same position in each > recipe. It has never been limited to tasks of the same name as far as I know. > > In position 10 of your example you have /distribution/beaker/beah/misc/sync > in the host recipe. Can you just use /distribution/dummy there instead with > role=STANDALONE to avoid the syncing behaviour? And then let them sync on > the start of task 11? Thanks for explaining and pointing me to TESTORDER. Do I understand this correctly that adding role=STANDALONE would turn off the sync feature for a task? Maybe it's just enough to add role=STANDALONE to lnst/install task. The beah/misc/sync task syncs with other task on second baremetal host. (In reply to Jan Tluka from comment #2) > Maybe it's just enough to add role=STANDALONE to lnst/install task. The > beah/misc/sync task syncs with other task on second baremetal host. Yeah this sounds like the right approach, if you don't actually want that task to sync with the others. |