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
If this issue is time-sensitive, I have submitted a corresponding issue with GCP support.
Bug Description
Scheduled Queries created via BQ Data Transfer Configs keep the KCC object stuck in "Updating", while a new Scheduled Query is created in GCP each update cycle.
Additional Diagnostic Information
I'm deploying a BQ Data Transfer Config via KCC, by applying a k8s manifest via Terraform. The Data Transfer Config is used to set up a Scheduled Query. The object is created in Kubernetes, and the actual Scheduled Query is created in GCP, but the k8s object is stuck continuously in the "Updating" state, and with each update cycle, a new Scheduled Query is created in GCP. The k8s object does not seem to be aware that the Scheduled Query is actually created, and will keep trying to create new ones.
Kubernetes Cluster Version
Server Version: v1.27.8-gke.1067004
Config Connector Version
1.113.0
Config Connector Mode
namespaced mode (default)
Log Output
No response
Steps to reproduce the issue
deploy a BigQuery Scheduled Query via KCC
check the status/count of the Scheduled Queries in GCP, and the status of the KCC object
Scheduled Queries created via BQ Data Transfer Configs keep the KCC object stuck in "Updating", while a new Scheduled Query is created in GCP each update cycle.
We implemented direct cloud reconciler for this resource in Config Connector 1.123. This issue should be fixed.
Checklist
Bug Description
Scheduled Queries created via BQ Data Transfer Configs keep the KCC object stuck in "Updating", while a new Scheduled Query is created in GCP each update cycle.
Additional Diagnostic Information
I'm deploying a BQ Data Transfer Config via KCC, by applying a k8s manifest via Terraform. The Data Transfer Config is used to set up a Scheduled Query. The object is created in Kubernetes, and the actual Scheduled Query is created in GCP, but the k8s object is stuck continuously in the "Updating" state, and with each update cycle, a new Scheduled Query is created in GCP. The k8s object does not seem to be aware that the Scheduled Query is actually created, and will keep trying to create new ones.
Kubernetes Cluster Version
Server Version: v1.27.8-gke.1067004
Config Connector Version
1.113.0
Config Connector Mode
namespaced mode (default)
Log Output
No response
Steps to reproduce the issue
YAML snippets
The text was updated successfully, but these errors were encountered: