Closed zaneb closed 6 days ago
/cc @dtantsur
/hold cancel
/retest
It seems Prow is having issues. Failures are non PR related.
/approve
Looks valid to me.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dtantsur
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/test generate /test gomod /test manifestlint
/test ?
@kashifest: The following commands are available to trigger required jobs:
/test generate
/test gomod
/test manifestlint
/test markdownlint
/test shellcheck
/test test
The following commands are available to trigger optional jobs:
/test metal3-centos-e2e-basic-test-main
/test metal3-centos-e2e-feature-test-main-features
/test metal3-centos-e2e-feature-test-main-pivoting
/test metal3-centos-e2e-feature-test-main-remediation
/test metal3-centos-e2e-integration-test-main
/test metal3-dev-env-integration-test-centos-main
/test metal3-dev-env-integration-test-ubuntu-main
/test metal3-e2e-1-29-1-30-upgrade-test-main
/test metal3-e2e-clusterctl-upgrade-test-main
/test metal3-ubuntu-e2e-basic-test-main
/test metal3-ubuntu-e2e-feature-test-main-features
/test metal3-ubuntu-e2e-feature-test-main-pivoting
/test metal3-ubuntu-e2e-feature-test-main-remediation
/test metal3-ubuntu-e2e-integration-test-main
Use /test all
to run the following jobs that were automatically triggered:
generate
gomod
manifestlint
/test metal3-e2e-clusterctl-upgrade-test-main
/lgtm
If we have to recreate the provisioner's state during deprovisioning, we must first call Adopt() to ensure that something will actually happen to deprovision it. This is the case regardless of provisioning method, but previously only happened when an image was provisioned. In practice, the ironic provisioner was attempting to adopt in cases where it was not originally intended to, and subsequent changes mean it is never necessary.
If an externally provisioned host has a provisioning image set and then the externallyProvisioned flag is removed, we should not begin an inspection (which would involve rebooting the host), but instead move directly to the provisioned state. This is also the case regardless of provisioning method, but previously only happened when an image was provisioned.