-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ HostFirmwareComponents CRD and Controller & Tests #1559
Conversation
9fab17e
to
f862054
Compare
f862054
to
b9b63fc
Compare
/test metal3-bmo-e2e-test-pull |
cc @dtantsur @elfosardo @honza |
3392307
to
dd3e962
Compare
/test metal3-bmo-e2e-test-pull |
/test metal3-bmo-e2e-test-pull Didn't find any logs in the links .-. let's try again to see |
dd3e962
to
f30f6d9
Compare
/test metal3-bmo-e2e-test-pull |
d65522e
to
5f4b845
Compare
/test metal3-bmo-e2e-test-pull |
5f4b845
to
8d6dc0d
Compare
/test metal3-bmo-e2e-test-pull |
- New Controller for HostFirmwareComponents - Updated the CRD based on kustomization - added GetFirmwareComponentsForNode to the Provisioner interface - implemented GetFirmwareComponentsForNode in ironic.go - Tests for HFC Controller Signed-off-by: Iury Gregory Melo Ferreira <[email protected]>
8d6dc0d
to
5473226
Compare
/test metal3-bmo-e2e-test-pull |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: honza The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
if componentListErr != nil { | ||
bmcAccess, _ := p.bmcAccess() | ||
if bmcAccess.FirmwareInterface() == "no-firmware" { | ||
return nil, fmt.Errorf("node %s is using firmware interface %s: %w", ironicNode.UUID, bmcAccess.FirmwareInterface(), componentListErr) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a follow-up: we should not include node UUIDs or refer to nodes or interfaces in user-visible messages since users don't have access to Ironic. Here we should talk about the driver not supporting firmware updates.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#1655 will take care of this and the other parts we discussed
/lgtm |
This commit is to address some feedback from metal3-io#1559. - Automatically create the HFC for the BMH - GetFirmwareComponents now takes into consideration that an empty list was returned and will only throw an error if the FirmwareInterface is different from `redfish`.
This commit is to address some feedback from metal3-io#1559. - Automatically create the HFC for the BMH - GetFirmwareComponents now takes into consideration that an empty list was returned and will only throw an error if the FirmwareInterface is different from `redfish`.
This commit is to address some feedback from metal3-io#1559. - Automatically create the HFC for the BMH - GetFirmwareComponents now takes into consideration that an empty list was returned and will only throw an error if the FirmwareInterface is different from `redfish`. Signed-off-by: Iury Gregory Melo Ferreira <[email protected]>
This commit is to address some feedback from metal3-io#1559. - Automatically create the HFC for the BMH - GetFirmwareComponents now takes into consideration that an empty list was returned and will only throw an error if the FirmwareInterface is different from `redfish`. - extended PrepareData to contain the TargetFirmwareComponents - actionPreparing takes into account the HFC Signed-off-by: Iury Gregory Melo Ferreira <[email protected]>
This commit is to address some feedback from metal3-io#1559. - Automatically create the HFC for the BMH - GetFirmwareComponents now takes into consideration that an empty list was returned and will only throw an error if the FirmwareInterface is different from `redfish`. - extended PrepareData to contain the TargetFirmwareComponents - actionPreparing takes into account the HFC Signed-off-by: Iury Gregory Melo Ferreira <[email protected]>
This commit is to address some feedback from metal3-io#1559. - Automatically create the HFC for the BMH - GetFirmwareComponents now takes into consideration that an empty list was returned and will only throw an error if the FirmwareInterface is different from `no-firmware`. - extended PrepareData to contain the TargetFirmwareComponents - actionPreparing takes into account the HFC Signed-off-by: Iury Gregory Melo Ferreira <[email protected]>
This commit is to address some feedback from metal3-io#1559. - Automatically create the HFC for the BMH - GetFirmwareComponents now takes into consideration that an empty list was returned and will only throw an error if the FirmwareInterface is different from `no-firmware`. - extended PrepareData to contain the TargetFirmwareComponents - actionPreparing takes into account the HFC Signed-off-by: Iury Gregory Melo Ferreira <[email protected]>
What this PR does / why we need it:
metal3-io/metal3-docs#364