-
Notifications
You must be signed in to change notification settings - Fork 124
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
[Bug]: Policy objects do not flip to Unready status when an invalid update is applied #1164
Comments
+1 |
Same here, tested with provider-aws versions |
Hello folks, Thank you for bringing up this issue. The issue can be reproduced with provider version
Also tried with
|
I'm seeing the same issue with Here is the status YAML, showing that the resource is still
When this failure does not bubble up to the Claim resource, users are led to believe that the change was successful. |
@diranged thanks for reporting this. Currently, managed resource reconciler From MR reconciler perspective, the update reconciliation is successful, as it successfully completes the For the sake of completeness, per Crossplane Resource Model (XRM) this situation should result in Anyways, we consider this as a valid request and investigate possible solutions and address the issue. |
Thanks for the thoughtful and helpful response... I appreciate you guys looking into how to make the experience better! |
I'm closing this issue because we introduced a fix for the issue in provider v1.4.0 |
Is there an existing issue for this?
Affected Resource(s)
iam.aws.upbound.io / Policy
Resource MRs required to reproduce the bug
Good Policy
Bad Policy
Steps to Reproduce
Create the Policy
Create the working policy first ... everything is fine:
Now, update the policy with an invalid inlinePolicy
What happened?
Bug: The policy is still considered
Ready
Given that the resource cannot be reconciled - it should go into an
Unready
state ... but instead it staysReady
. TheLastAsyncOperation
does flip toFalse
, but that's not enough.. I believe the resource should flip into an unready state.Relevant Error Output Snippet
No response
Crossplane Version
1.15.0
Provider Version
1.1.0
Kubernetes Version
1.28.0
Kubernetes Distribution
Localstack
Additional Info
Creation Logs
Failure Logs after Bad Policy Update
The text was updated successfully, but these errors were encountered: