-
Notifications
You must be signed in to change notification settings - Fork 273
Confusing behavior on removing externallyProvisioned: true
#2465
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
Comments
On thinking more about it, I think removing |
Add a new page on the externally provisioned feature. Since moving out of the externally provisioned state does not actually work [1], remove the corresponding transitions from the diagram. [1] metal3-io/baremetal-operator#2465 Signed-off-by: Dmitry Tantsur <[email protected]>
Add a new page on the externally provisioned feature. Since moving out of the externally provisioned state does not actually work [1], remove the corresponding transitions from the diagram. [1] metal3-io/baremetal-operator#2465 Signed-off-by: Dmitry Tantsur <[email protected]>
Add a new page on the externally provisioned feature. Since moving out of the externally provisioned state does not actually work [1], remove the corresponding transitions from the diagram. [1] metal3-io/baremetal-operator#2465 Signed-off-by: Dmitry Tantsur <[email protected]>
Changing ExternallyProvisioned does not actually work. Furthermore, it results in a host hopelessly stuck in the "inspecting" state (in my testing, I could not even delete it). Until we sort out this issue, let us prevent users from getting into a problem. Workaround for: metal3-io#2465 Signed-off-by: Dmitry Tantsur <[email protected]>
Changing ExternallyProvisioned does not actually work. Furthermore, it results in a host hopelessly stuck in the "inspecting" state (in my testing, I could not even delete it). Until we sort out this issue, let us prevent users from getting into a problem. Workaround for: metal3-io#2465 Signed-off-by: Dmitry Tantsur <[email protected]>
Changing ExternallyProvisioned does not actually work. Furthermore, it results in a host hopelessly stuck in the "inspecting" state (in my testing, I could not even delete it). Until we sort out this issue, let us prevent users from getting into a problem. Workaround for: metal3-io#2465 Signed-off-by: Dmitry Tantsur <[email protected]>
We have discussed this during community meeting, there are multiple options: |
@Rozzii: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Uh oh!
There was an error while loading. Please reload this page.
I'm not sure we ever intended for the
externallyProvisioned
field to be reset tofalse
, but right now it explicitly causes inspection to start. Unfortunately, it cannot possibly succeed with the Ironic node in theactive
state: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
The text was updated successfully, but these errors were encountered: