Skip to content
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]: Deleting a provider leaves the CRD with an outdated ownerReference pointing to the old ProviderVersion #1557

Open
1 task done
pablomdc opened this issue Nov 6, 2024 · 0 comments
Labels
bug Something isn't working needs:triage

Comments

@pablomdc
Copy link

pablomdc commented Nov 6, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Affected Resource(s)

No response

Resource MRs required to reproduce the bug

No response

Steps to Reproduce

  1. Create a provider, for example xpkg.upbound.io/upbound/provider-aws-sqs:v1.9
  2. Delete the provider
  3. Install same provider
  4. ProviderVersion is unhealthy with error "already controlled by ProviderRevision"
  5. WA is to manually remove the ownerReferences from the CRD and to redeploy the provider (then it works)

What happened?

Cannot install new provider

Relevant Error Output Snippet

No response

Crossplane Version

v1.16

Provider Version

v1.9

Kubernetes Version

No response

Kubernetes Distribution

No response

Additional Info

No response

@pablomdc pablomdc added bug Something isn't working needs:triage labels Nov 6, 2024
@pablomdc pablomdc changed the title [Bug]: Deleting a provider remains the CRD hanged on old ProviderVersion ownerReference [Bug]: Deleting a provider leaves the CRD with an outdated ownerReference pointing to the old ProviderVersion Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs:triage
Projects
None yet
Development

No branches or pull requests

1 participant