providerrevision for provider-azure-azure never becomes ready

[Kaitou786]

What happened?

Hi I am trying to install the provider-azure-azure onto a new AKS cluster but it never becomes ready; seeing the providerrevisions:
I see:

Warning  ResolveDependencies  48s (x3 over 49s)   packages/providerrevision.pkg.crossplane.io  cannot resolve package dependencies: missing dependencies: [xpkg.upbound.io/upbound/provider-family-azure]
  Normal   ApplyClusterRoles    43s (x10 over 50s)  rbac/providerrevision.pkg.crossplane.io      Applied RBAC ClusterRoles
  Normal   BindClusterRole      43s (x6 over 50s)   rbac/providerrevision.pkg.crossplane.io      Bound system ClusterRole to provider ServiceAccount(s)
  Warning  SyncPackage          3s (x4 over 43s)    packages/providerrevision.pkg.crossplane.io  cannot establish control of object: subscriptions.azure.upbound.io is already controlled by ProviderRevision upbound-provider-family-azure-f87340b16c44 (UID 968b6d4d-5d60-4e3f-a52f-d4100ac33b8b)

How can we reproduce it?

Just applying the provider manifest causes this issue:

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-azure-azure
spec:
  package: xpkg.upbound.io/upbound/provider-azure-azure:v0.36.0

What environment did it happen in?

Crossplane version: v1.13.2

[Kaitou786]

Okay so one other thing I noticed; this time I installed the

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-family-azure
spec:
  package: xpkg.upbound.io/upbound/provider-family-azure:v0.36.0

manually so the error message while describing is on the SyncPackage when it tries to take ownership of the crd which the provider-family-azure already have; I manually deleted that ownership so the azure-provider-provider can move forward.
Turns out it tries to take ownership of all the azure CRDs

providerconfigs.azure.upbound.io                            
providerconfigusages.azure.upbound.io                       
resourcegroups.azure.upbound.io                             
resourceproviderregistrations.azure.upbound.io              
storeconfigs.azure.upbound.io                              
subscriptions.azure.upbound.io                          

I manually went in deleted the Ownership reference of the provider-family-azure from all the above CRDs after which provider provider-azure-azure is Healthy.

Though this does seem like a bug; Either the provider-family-azure should not create those CRDs with OwnerRef or provider-azure-azure shouldn't try to take ownership of them.

[Kaitou786]

Though after doing the above the original provider-family-azure becomes unhealthy since it again tries to gain owner reference to those CRDs

[Mikel-Landa]

Hi,
Had same issue. I think docs are a bit confusing. The provider family already has the resources so there is no need to install provider-azure-azure. If you just use the provider-family-azure it works.