You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
projects: spec.resourceId isn't respected when provided, metadata.name is used #462
If this issue is time-sensitive, I have submitted a corresponding issue with GCP support.
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
Activity
jcanseco commentedon 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:
We should have a fix out shortly (within the next couple weeks).
aw185176 commentedon May 6, 2021
Awesome, thanks for the update.
maqiuyujoyce commentedon May 17, 2021
The issue should be fixed in Config Connector v1.50.0.
KingBain commentedon Jun 6, 2023
Not sure this has been resolved. Having similar issue with latest version of CC
#818