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]: TokenPassword resource stuck when corresponding Token is deleted first #778

Open
1 task done
felfa01 opened this issue Jul 4, 2024 · 3 comments
Open
1 task done
Labels
bug Something isn't working needs:triage

Comments

@felfa01
Copy link

felfa01 commented Jul 4, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Affected Resource(s)

containerregistry.azure.upbound.io/v1beta1 - TokenPassword

Resource MRs required to reproduce the bug

No response

Steps to Reproduce

  1. Create a Token
  2. Create a TokenPassword with spec.forProvider.containerRegistryTokenIdRef pointing towards the Token
  3. Delete Token
  4. Delete TokenPassword

For our setup, we have both these resources in an ArgoCD Application so we can't really control the order in which they are deleted (deleting tokenpassword first and then token works fine).

What happened?

TokenPassword is stuck and not deleted due to 404s towards the token in the ACR

Relevant Error Output Snippet

conditions:
  - lastTransitionTime: "2024-07-04T10:53:53Z"
    message: |-
      observe failed: failed to observe the resource: [{0 retrieving Token (Subscription: "xxxxx"
      Resource Group Name: "registry"
      Registry Name: "registry"
      Token Name: "read"): unexpected status 404 with error: ResourceNotFound: The resource read could not be found. retrieving Token (Subscription: "xxxxx"
      Resource Group Name: "registry"
      Registry Name: "registry"
      Token Name: "read"): unexpected status 404 with error: ResourceNotFound: The resource read could not be found. []}]
    reason: ReconcileError
    status: "False"
    type: Synced
  - lastTransitionTime: "2024-07-04T10:53:41Z"
    reason: Deleting
    status: "False"
    type: Ready
  - lastTransitionTime: "2024-07-04T10:53:52Z"
    message: 'async delete failed: failed to delete the resource: [{0 deleting Container
      Registry Token Password: (Password Name "password" / Token Name "read"
      / Registry Name "registry" / Resource Group "registry"): performing
      Update: unexpected status 404 with error: ResourceNotFound: The resource read
      could not be found. deleting Container Registry Token Password: (Password Name
      "password" / Token Name "read" / Registry Name "registry"
      / Resource Group "registry"): performing Update: unexpected status 404 with
      error: ResourceNotFound: The resource read could not be found.
      []}]'

Crossplane Version

1.15.1

Provider Version

1.0.1

Kubernetes Version

1.29

Kubernetes Distribution

AKS

Additional Info

No response

@felfa01 felfa01 added bug Something isn't working needs:triage labels Jul 4, 2024
@illrill
Copy link

illrill commented Jul 4, 2024

I have the exact same problem! Need to manually remove the finalizer on the TokenPassword MR to get it resolved

Copy link

github-actions bot commented Oct 3, 2024

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Oct 3, 2024
@illrill
Copy link

illrill commented Oct 3, 2024

/fresh

@github-actions github-actions bot removed the stale label Oct 4, 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

2 participants