providerrevision.pkg.crossplane.io stuck in unhealthy state and provider does not deploy

[vijayansarathy]

I am trying to deploy the Crossplane AWS Provider for IAM using the package xpkg.upbound.io/upbound/provider-aws-iam:v0.47.2. I was earlier using v0.37.0 of the package and everything was working fine. After I undeployed the older version and deployed the new one, the AWS Provider does not come up in a healthy state at all.

What happens is that the providerrevision.pkg.crossplane.io resource does not get into a healthy state. I have attached two screenshots, one showing the output of kubectl get crossplane command and the other one showing kubectl describe of the aforementioned resource. In the output of kubectl describe command, I see a warning under the Events which states cannot resolve package dependencies: node already exists

This has happened to one other time when I was doing something similar, switching between different versions of the Provider. Once it gets into this state, even if I undeploy everything, including the main Crossplane controller, I don't seem to be able to get the Provider reach a healthy state.

Has anyone encountered this behavior? How do you recover from it?
Thanks,
Viji

[vijayansarathy]

I came across this issue #3423 which is the same problem I have been encountering. After deleting the Lock resource, things are working OK.
I am afraid that this may happen in Production down the road when we are trying to upgrade the provider versions.