You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Submit the definition, composition, and claim. Once all resources are deployed, try to delete the claim. The claim will remain temporarily, as it's waiting in the background for the Managed Resources (MRs) to be deleted. Eventually, all MRs will be deleted except for one – the MonitorActivityLogAlert – even though it will have been successfully removed from Azure. As a result, the claim cannot be deleted immediately because it continues running in the foreground, waiting for the last MR to be removed.
Is there an existing issue for this?
Affected Resource(s)
insights.azure.upbound.io/v1beta1 - MonitorActivityLogAlert
Resource MRs required to reproduce the bug
Definition
Composition
Claim
Steps to Reproduce
Submit the definition, composition, and claim. Once all resources are deployed, try to delete the claim. The claim will remain temporarily, as it's waiting in the background for the Managed Resources (MRs) to be deleted. Eventually, all MRs will be deleted except for one – the MonitorActivityLogAlert – even though it will have been successfully removed from Azure. As a result, the claim cannot be deleted immediately because it continues running in the foreground, waiting for the last MR to be removed.
After deletion of claim
description of MR
azure-provider.log
attaching screenshot and the provider log for reference.
What happened?
Ideally MR should get deleted once we deletes the claim.
Relevant Error Output Snippet
No response
Crossplane Version
1.15.2
Provider Version
1.5.0
Kubernetes Version
1.28.2
Kubernetes Distribution
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: