Closed hannupiki-eficode closed 2 months ago
@hannupiki-eficode thanks for reporting. This issue is similar to https://github.com/crossplane-contrib/provider-upjet-aws/issues/1164 . The cause is explained at https://github.com/crossplane-contrib/provider-upjet-aws/issues/1164#issuecomment-2058500394 and we will follow up there.
Is there an existing issue for this?
Affected Resource(s)
At least these two:
Resource MRs required to reproduce the bug
No response
Steps to Reproduce
If you use nested compositions, deploy ApplicationGateway into child composition and verify that also parent composition is showing everything as ready.
What happened?
Expected: Resource and compositions would be reporting resource as failed in all levels (parent and child composition and resource itself). Observed: Resource, its composition and parent composition are showing everything as ready. Resource's LastActivityOperation is showing an error that prevents applying the change and therefor resource isn't matching the state that have been written into Git and pushed into cluster from there.
In these screenshots you see obvious failure that is rightfully failing, but also how these resources do look like with common ways of checking their status:
Output from
kubectl get managed
Parent composition
Actual ApplicationGateway resource
Relevant Error Output Snippet
No response
Crossplane Version
1.15.1
Provider Version
xpkg.upbound.io/upbound/provider-azure-network:v1.0.0, xpkg.upbound.io/upbound/provider-azure-managedidentity:v1.0.0
Kubernetes Version
v1.27.7
Kubernetes Distribution
AKS
Additional Info
No response