-
Notifications
You must be signed in to change notification settings - Fork 33
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
🌱 Introduce ReconcileError with Transient and Terminal Error type #787
🌱 Introduce ReconcileError with Transient and Terminal Error type #787
Conversation
/test metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main |
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.
/test metal3-ubuntu-e2e-integration-test-main
Thanks for the contribution, nice work in general but I have a question below.
@@ -0,0 +1,85 @@ | |||
/* |
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 assume from the license message, that this file and the related test file were copied.
Is there a possibility to find these Error types in some library that we could pull in as a dependency instead of duplicating this code?
If this is not copied but written by you, then my question is that why are you adding the K8s author copyright?
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 know other files have this copyright here, I will start a discussion with the community related to that also.
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 have copied from capm3. I am pretty much sure I have written those code in capm3. What would be proper copyright in this case?
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 have used at least # Copyright 2023 The Metal3 Authors.
elsewhere.
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.
Fixed now. I used 2024 as PR is opened in 2024
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.
Thanks @Sunnatillo !
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 did similar for CAPM3 too, some time back right?
/cc @kashifest @lentzi90
/lgtm |
/hold |
Remove RequeueAfterError(depricated in CAPM3) Signed-off-by: Sunnatillo <sunnat.samadov@est.tech>
2a930b2
to
fa6581d
Compare
/test metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main |
/test metal3-ubuntu-e2e-integration-test-main |
1 similar comment
/test metal3-ubuntu-e2e-integration-test-main |
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
Related to this, I guess we should also think about following CAPI by using conditions instead of ErrorMessage
, right?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lentzi90 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 |
/retest |
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.
/lgtm
yes, I will checl what beta2 is bringing and trying to align with it |
This is currently held for copyright issue, which is now fixed. But then
Are you going to change this PR still, or merge this and then change it later? Unhold if latter. |
No, this is different task. |
This PR:
Introduces ReconcileError with Transient and Terminal Error type
Removes RequeueAfterError (as it was depricated in CAPI and CAPM3)
ReconcileError represents an generic error of Reconcile loop. errorType indicates what type of action is required to recover. It can take two values:
a. Transient - Can be recovered , will be requeued after.
b. Terminal - Cannot be recovered, will not be requeued.
When error is not ReconcileError it will be returned to Reconciler.