I'm not sure we ever intended for the externallyProvisioned field to be reset to false, but right now it explicitly causes inspection to start. Unfortunately, it cannot possibly succeed with the Ironic node in the active state:

action \"inspecting\" failed: hardware inspection failed: unexpected provision state active","errorVerbose":"unexpected provision state active

If inspection is disabled, the next state is preparing, which I suspect will fail the same way for the same reason.

We need to decide on a sane behavior in this case and probably add the scenario to e2e tests.

/kind bug