Skip to content

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

Closed

Description

@aw185176

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

Activity

  1. jcanseco commented on May 6, 2021

    @jcanseco
    Member

    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).

  2. aw185176 commented on May 6, 2021

    @aw185176
    Author

    Awesome, thanks for the update.

  3. maqiuyujoyce commented on May 17, 2021

    @maqiuyujoyce
    Collaborator

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

  4. KingBain commented on Jun 6, 2023

    @KingBain

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      ⌂ 换网址