fix multus include#10105
Conversation
|
|
|
Welcome @darkobas2! |
|
Hi @darkobas2. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/ok-to-test |
|
If the |
well on my setup I did not need it.. but when i uploaded the first patch i noticed the CI job was failing without it. |
Could you try again without this line changed? Anyway the CI is a bit flaky these days when there are too much tasks running so you would have to push force to relaunch the CI anyway :x 🙈... |
|
i understand your concern... in case multus is needed and these wars are needed playbook should fail... i can look into how to maybe implement this logic where the multus_manifest_x vars are defined... meanwhile the CI should be running |
|
Sorry could you rebase your PR and push force to relaunch the pipeline again 🙏 😬 |
| delegate_to: "{{ groups['kube_control_plane'][0] }}" | ||
| run_once: true | ||
| with_items: "{{ multus_manifest_1.results }} + {{ multus_nodes_list|map('extract', hostvars, 'multus_manifest_2')|list|json_query('[].results') }}" | ||
| with_items: "{{ multus_manifest_1.results + multus_nodes_list|map('extract', hostvars, 'multus_manifest_2.results')|list }}" |
There was a problem hiding this comment.
So you were indeed right the CI fails with this change :(.
I think something like that should work though:
| with_items: "{{ multus_manifest_1.results + multus_nodes_list|map('extract', hostvars, 'multus_manifest_2.results')|list }}" | |
| with_items: "{{ multus_manifest_1.results + (multus_nodes_list|map('extract', hostvars, 'multus_manifest_2.results') | default([]))|list }}" |
There was a problem hiding this comment.
sorry that didnt work.
"msg": "Failed to template loop_control.label: 'None' has no attribute 'item'. 'None' has no attribute 'item'"
I could not get it to work otherwise, so I added a task after this one to fail if this task resulted with item.name 'None'
There was a problem hiding this comment.
i even tried setting
default([{'item': {'name': 'None', 'type': 'None', 'file': 'None'}}]
There was a problem hiding this comment.
Hmmm actually I am thinking that the extract might simply not works... Does this works better?
| with_items: "{{ multus_manifest_1.results + multus_nodes_list|map('extract', hostvars, 'multus_manifest_2.results')|list }}" | |
| with_items: "{{ multus_manifest_1.results + (multus_nodes_list|map('extract', hostvars, 'multus_manifest_2')|list|json_query('[].results')) }}" |
If this works I believe it's the only change that we would really need to have it working consistently...
There was a problem hiding this comment.
sorry i cant test locally in the next day or two.... CI is failing too.. will push again later to retry
There was a problem hiding this comment.
No worries, thanks for all your OSS works ❤️
`` "msg": "Failed to template loop_control.label: 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'item'. 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'item'", "skip_reason": "Conditional result was False"} `` fixes case when multus should NOT be included.
floryut
left a comment
There was a problem hiding this comment.
@darkobas2 Thank you for the PR 👍
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: darkobas2, floryut, MrFreezeex The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
`` "msg": "Failed to template loop_control.label: 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'item'. 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'item'", "skip_reason": "Conditional result was False"} `` fixes case when multus should NOT be included.
"msg": "Failed to template loop_control.label: 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'item'. 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'item'", "skip_reason": "Conditional result was False"}case when multus should NOT be included.
/kind bug
What this PR does / why we need it:
if multus is not enabled, unable to deploy/upgrade.
Which issue(s) this PR fixes:
Special notes for your reviewer:
someone with multus should test this.
Does this PR introduce a user-facing change?: