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.

Sign up for GitHub

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

Jump to bottom

projects: spec.resourceId isn't respected when provided, metadata.name is used #462

Closed
2 of 3 tasks
aw185176 opened this issue May 6, 2021 · 4 comments
Closed
2 of 3 tasks

projects: spec.resourceId isn't respected when provided, metadata.name is used #462

aw185176 opened this issue May 6, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@aw185176
Copy link

aw185176 commented May 6, 2021

Checklist

Bug Description

spec.resourceId isn't respected when provided, metadata.name is set.

Additional Diagnostic Information

This is on version 1.49.1 deployed manually onto GKE

Kubernetes Cluster Version

Server Version: v1.18.16-gke.2100

Config Connector Version

1.49.1

Config Connector Mode

cluster

Log Output

Steps to Reproduce

Steps to reproduce the issue

  • create resource with spec.resourceId and metadata.name that are different
  • schedule it, you'll get underlying resource not exists error etc
  • if you then move the same spec.resourceId to metadata.name, it'll create immediately, implying that the spec.resourceId was a valid identifier from the start
@aw185176 aw185176 added the bug Something isn't working label May 6, 2021
@jcanseco
Copy link
Member

jcanseco commented May 6, 2021

Hi @aw185176, thanks for bringing this issue up to us. I can confirm that I was able to reproduce the issue with the following error message:

Update call failed: underlying resource no longer exists and can't be recreated without creating 
a brand new resource

We should have a fix out shortly (within the next couple weeks).

@aw185176
Copy link
Author

aw185176 commented May 6, 2021

Awesome, thanks for the update.

@maqiuyujoyce
Copy link
Collaborator

The issue should be fixed in Config Connector v1.50.0.

@KingBain
Copy link

KingBain commented Jun 6, 2023

Not sure this has been resolved. Having similar issue with latest version of CC
#818

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@KingBain @jcanseco @maqiuyujoyce @aw185176