Add parallel test for new baremetal resources#26541
Add parallel test for new baremetal resources#26541openshift-merge-robot merged 1 commit intoopenshift:masterfrom
Conversation
1ccbffa to
af4e179
Compare
af4e179 to
e845562
Compare
|
/retest |
|
/lgtm |
|
@bfournie looks like the tests failed in the latest run |
Yeah its looks like the resources were created but occasionally can get 0 bios config settings returned from the provisioner (I had seen this on masters but I guess its possible on workers too). I will have a fix for that in bmo, until then I'll remove the check for settings not empty |
e845562 to
109148c
Compare
109148c to
14216cb
Compare
|
/test e2e-metal-ipi |
66b9a1a to
d1e05f9
Compare
|
/retest-required |
7c44f8f to
18dd121
Compare
|
/test e2e-aws-serial |
|
/lgtm |
| for _, h := range hosts.Items { | ||
| hostName := getStringField(h, "baremetalhost", "metadata.name") | ||
|
|
||
| g.By("check that each baremetalhost has a corresponding hostfirmwaresettings") |
There was a problem hiding this comment.
This message will be printed for each host, but it does not show any information about that. It could be improved by also adding the current hostname for more clarity
There was a problem hiding this comment.
Good point. Included the hostname in the debug output.
|
|
||
| // Reenable this when fix to prevent settings with 0 entries is in BMO | ||
| // g.By("check that hostfirmwaresettings settings have been populated") | ||
| // expectStringMapField(*hfs, "hostfirmwaresettings", "status.settings").ToNot(o.BeEmpty()) |
There was a problem hiding this comment.
Do we still need to keep this commented code?
There was a problem hiding this comment.
Yes, per comment, the code should be uncommented when metal3-io/baremetal-operator#995 merges that will prevent empty settings fields.
| // expectStringMapField(*hfs, "hostfirmwaresettings", "status.settings").ToNot(o.BeEmpty()) | ||
|
|
||
| g.By("check that hostfirmwaresettings conditions show resource is valid") | ||
| expectSliceField(*hfs, "hostfirmwaresettings", "status.conditions").ToNot(o.BeEmpty()) |
There was a problem hiding this comment.
Isn't something already somehow addressed within the checkConditionStatus method?
There was a problem hiding this comment.
I think its necessary to check that conditions is not empty but I've moved this check to checkConditionStatus and simplified it.
Add a test to check that the hostfirmwaresettings and firmwareschema resources are created and populated with BIOS configuration settings.
18dd121 to
d7719b2
Compare
|
/test e2e-metal-ipi Changes look fine to me, let's see first a run on the various e2e-metal-ipi configurations |
|
/test e2e-metal-ipi |
|
/test e2e-metal-ipi-ovn-ipv6 |
|
/test e2e-metal-ipi-ovn-ipv6 |
|
/retest |
|
/test e2e-metal-ipi-ovn-ipv6 |
|
/lgtm |
|
/test e2e-metal-ipi-ovn-ipv6 |
|
/assign @derekwaynecarr |
|
cc @ardaguclu |
|
/approve |
|
cc @bparees |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andfasano, ardaguclu, bfournie, bparees, elfosardo 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 |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/test e2e-gcp |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
Add a test to check that the hostfirmwaresettings and firmwareschema resources are created and populated with BIOS configuration settings.