-
Notifications
You must be signed in to change notification settings - Fork 247
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
🐛 Proceed to power off after deprovisioning #1312
Conversation
/test-centos-e2e-integration-main |
/lgtm |
/lgtm |
cf3a4f5
to
0c960c4
Compare
/lgtm |
/test-centos-e2e-integration-main |
Can this change be reflected back also in the state diagram https://github.com/metal3-io/baremetal-operator/blob/main/docs/BaremetalHost_ProvisioningState.png ? We are planning for a minor release of BMO soon, can we take this bug fix in before that @honza @zaneb |
Good catch! I updated the diagram, please have a look. |
@@ -51,11 +51,13 @@ digraph BaremetalHost { | |||
Provisioned -> Deprovisioning [label="!DeletionTimestamp.IsZero()"] | |||
|
|||
ExternallyProvisioned [shape=doublecircle] | |||
ExternallyProvisioned -> Deleting [label="!DeletionTimestamp.IsZero()"] | |||
ExternallyProvisioned -> PoweringOffBeforeDelete [label="!DeletionTimestamp.IsZero()"] |
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.
People have complained about all the Deleting3 [shape=point]
stuff making it unclear that the host goes into the Deleting state no matter where it was when deleted.
I wonder if this is the point where it finally becomes completely untenable to hide this info for the sake of saving a few lines on the diagram. How bad does it look if we include all the edges?
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.
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.
🤔 that's... not outstanding, but maybe not so bad that it's worth the ongoing confusion to avoid it. WDYT?
We don't actually go to PoweringOffBeforeDelete from Unmanaged or Registering, do we?
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.
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.
OK, I pushed the diagram changes. I think it's reasonably clear.
bb29507
to
5a01d08
Compare
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.
/approve
Registering -> Deleting2 [label="!DeletionTimestamp.IsZero()"] | ||
|
||
Deleting2 [shape=point] | ||
Registering -> PoweringOffBeforeDelete [label="!DeletionTimestamp.IsZero()"] | ||
|
||
ExternallyProvisioned -> Inspecting [label="!externallyProvisioned && NeedsHardwareInspection()"] |
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.
I just discovered that if we change all these ones with && or || to e.g.
ExternallyProvisioned -> Inspecting [label="!externallyProvisioned && NeedsHardwareInspection()"] | |
ExternallyProvisioned -> Inspecting [label="!externallyProvisioned &&\nNeedsHardwareInspection()"] |
it makes everything a bit more compact, and this one in particular fixes that diabolical intersection of the two edges at the top right.
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.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zaneb 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 |
abb1d1c
to
8cf8e29
Compare
8cf8e29
to
2359fba
Compare
2359fba
to
abb1d1c
Compare
/test-centos-e2e-integration-main |
/test-centos-e2e-integration-main |
Unmanaged -> Deleting1 [label="!DeletionTimestamp.IsZero()"] | ||
|
||
Deleting1 [shape=point] | ||
Unmanaged -> PoweringOffBeforeDelete [label="!DeletionTimestamp.IsZero()"] |
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.
This make me worried. Unmanaged hosts cannot be powered off. Isn't it the cause of the issue that we've recently discussed?
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.
We already have a follow up for this here #1356
Registering -> Deleting2 [label="!DeletionTimestamp.IsZero()"] | ||
|
||
Deleting2 [shape=point] | ||
Registering -> PoweringOffBeforeDelete [label="!DeletionTimestamp.IsZero()"] |
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.
Same
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.
We already have a follow up for this here #1356
/lgtm |
Follow up to #1176