-
Notifications
You must be signed in to change notification settings - Fork 293
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
I reinstall by KCC cluster just now and during that I removed old resources in the old KCC (KCC only, not underlying GCP resources) and then I'm now "reacquiring" those resources in a new installation of KCC by running kubectl apply -f xxx.yaml
on the files one by one. When I try to apply a KCC config for folders it does not work, I get this error:
status:
conditions:
- lastTransitionTime: "2020-04-16T12:22:15Z"
message: 'Update call failed: error applying desired state: Error creating folder
''xxxxxxxxxxxx'' in ''folders/xxxxxxxxxxx'': Error waiting for creating
folder: Error code 9, message: The folder operation violates display name
uniqueness within the parent.'
reason: UpdateFailed
status: "False"
type: Ready
I also tried to create a new folder in the UI and then to acquire that one, but it also fails like this:
status:
conditions:
- lastTransitionTime: "2020-04-16T12:28:49Z"
message: 'Update call failed: error applying desired state: Error creating folder
''test-folder'' in ''folders/xxxxxxxxxxxxx'': Error waiting for creating folder:
Error code 9, message: The folder operation violates display name uniqueness
within the parent.'
reason: UpdateFailed
status: "False"
type: Ready
ConfigConnector Version
Run the following command to get the current ConfigConnector version
1.7.1
To Reproduce
Steps to reproduce the behavior:
-
Create new folder in the UI
YAML snippets:
# Top level namespace used for folders
apiVersion: v1
kind: Namespace
metadata:
name: global-resources
annotations:
cnrm.cloud.google.com/folder-id: "xxxxxxxx" # Folder where subfolders are created
cnrm.cloud.google.com/project-id: xxxxxxxxxxxx # Project id of project where the config connector is running
---
apiVersion: resourcemanager.cnrm.cloud.google.com/v1beta1
kind: Folder
metadata:
namespace: global-resources
name: test-folder
annotations:
cnrm.cloud.google.com/deletion-policy: abandon # Don't delete GCP resource if KCC entry is deleted
spec:
displayName: test-folder
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working