Closed kashifest closed 3 weeks ago
/test metal3-ubuntu-e2e-integration-test-main /test metal3-centos-e2e-integration-test-main
/test ?
@kashifest: The following commands are available to trigger required jobs:
/test build
/test generate
/test gomod
/test manifestlint
/test markdownlint
/test metal3-centos-e2e-integration-test-main
/test metal3-ubuntu-e2e-integration-test-main
/test shellcheck
/test test
/test unit
The following commands are available to trigger optional jobs:
/test metal3-centos-e2e-basic-test-main
/test metal3-centos-e2e-feature-test-main
/test metal3-e2e-1-26-1-27-upgrade-test-main
/test metal3-e2e-1-27-1-28-upgrade-test-main
/test metal3-e2e-1-28-1-29-upgrade-test-main
/test metal3-e2e-clusterctl-upgrade-test-main
/test metal3-ubuntu-e2e-basic-test-main
/test metal3-ubuntu-e2e-feature-test-main
Use /test all
to run the following jobs that were automatically triggered:
generate
gomod
manifestlint
unit
/override metal3-centos-e2e-integration-test-main centos is broken for unrelated reasons /test metal3-ubuntu-e2e-feature-test-main
@kashifest: Overrode contexts on behalf of kashifest: metal3-centos-e2e-integration-test-main
/override metal3-centos-e2e-integration-test-main
@kashifest: Overrode contexts on behalf of kashifest: metal3-centos-e2e-integration-test-main
can we change this SetError
to transient error too, that we are doing in Associate
:
https://github.com/metal3-io/cluster-api-provider-metal3/blob/e827f42e1a94149c789fed5828a924ff0a0c002d/baremetal/metal3machine_manager.go#L391
can we change this
SetError
to transient error too, that we are doing inAssociate
:
Ah ok, I thought we did that already !
Ah ok, I thought we did that already !
I only changed errors in SetPause and RemovePause yesterday, didn't want to break anything.
/test metal3-ubuntu-e2e-integration-test-main /override metal3-centos-e2e-integration-test-main /test metal3-ubuntu-e2e-feature-test-main
@kashifest: Overrode contexts on behalf of kashifest: metal3-centos-e2e-integration-test-main
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: adilGhaffarDev
The full list of commands accepted by this bot can be found here.
The pull request process is described here
This is a bug and it is a followup of https://github.com/metal3-io/cluster-api-provider-metal3/pull/1765. According to
once
failureReason
orfailureMessage
surface on the CAPI object who is referencing the infra object, they cannot be restored anymore. Hence, CAPM3 should not clear them as well.For the same reason, this PR is removing one of the occurrences of setError so as not to through terminal error while associating BMH but through transient error.
Signed-off-by: Kashif Khan kashif.khan@est.tech