Checklist

• I did not find a related open issue.
• I did not find a solution in the troubleshooting guide: (https://cloud.google.com/config-connector/docs/troubleshooting)
• If this issue is time-sensitive, I have submitted a corresponding issue with GCP support.

Bug Description

Attempting to delete a StorageBucketAccessControl (or StorageDefaultObjectAccessControl) resource after its referenced StorageBucket has already been deleted fails with the following error:

Delete call failed: error fetching live state: error getting ID for resource: error getting value from reference: could not parse reference resolution value '<nil>' as string

It seems that the StorageBucket needs to be deleted first. Otherwise, the only way to unstuck the delete is to do a forced cleanup.

Additional Diagnostic Information

Kubernetes Cluster Version

Client Version: v1.21.0
Server Version: v1.18.16-gke.2100

Config Connector Version

1.49.1

Config Connector Mode

cluster

Log Output

N/A

Steps to Reproduce

Steps to reproduce the issue

1. Apply both the StorageBucket and StorageBucketAccessControl below.
2. Wait for both to be UpToDate.
3. Delete the StorageBucket.
4. Delete the StoageBucketAccessControl.
5. Observe that StorageBucketAccessControl fails with DeleteFailed.

The same is true if you replace StorageBucketAccessControl with a StorageDefaultObjectAccessControl resource instead.

YAML snippets

1. StorageBucket:

apiVersion: storage.cnrm.cloud.google.com/v1beta1
kind: StorageBucket
metadata:
  annotations:
    cnrm.cloud.google.com/project-id: my-project
  name: my-bucket

2. StorageBucketAccessControl:

apiVersion: storage.cnrm.cloud.google.com/v1beta1
kind: StorageBucketAccessControl
metadata:
  name: my-bucket-access-control
spec:
  bucketRef:
    name: my-bucket
  entity: allAuthenticatedUsers
  role: READER