Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
f68437d to
3326d42
Compare
|
/retest-required |
michburk
left a comment
There was a problem hiding this comment.
One question, otherwise lgtm.
There was a problem hiding this comment.
I noticed that your testproject has to construct cifmw_update_node_sets.stdout as a newline-delimited string, just for it to be parsed back into a list here in the cifmw. Do you think it would make sense to move this stdout normalizing to a task above when no manual cifmw_update_node_sets is provided. Then the job definition could pass os_update_compute_nodesets directly, rather than fabricating an oc stdout-shaped value.
There was a problem hiding this comment.
Hi Michael, thanks for raising it. I've just amended my patch :)
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 55m 15s |
Allow callers to supply the NodeSets used by the reboot deployment. When unset, continue discovering every NodeSet in the namespace. Signed-off-by: Samuel Rac <srac@redhat.com>
3326d42 to
79ed04f
Compare
|
Build failed (check pipeline). Post ❌ openstack-k8s-operators-content-provider FAILURE in 6m 22s |
Allow callers to supply the NodeSets used by the reboot deployment. When unset, continue discovering every NodeSet in the namespace.