-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CloudSQLInstance contantly being updated #454
Comments
I am seeing the same behavior using the same versions of crossplane, gcp-provider en GKE as @bartse. I had to disable public network ( for which i couldn't find an option in crossplane). Afterwards the DB is constantly being updated. |
Happens for us, too. Constant update leads to 400 error messages per 5 minutes and makes it impossible to actually maintain the database in a stable way. |
I've encountered the same issue when working with this. I'm using the full URI for the private network, so it can't be that. I've tried to look through GCP logs to find out what the differences are between the two instance versions (the existing one and the one on which crossplane detects a change), and the only things that I found are these arguments:
|
The same issue is on the same provider version. We thought it was related failover replica, but looks like no. Any idea? |
I am experiencing the same. Deletion of CloudSQLInstance object and recreation of it solve the issue, but the initial behavior happens to us randomly |
I assume this provider is deprecated in favor of the new https://github.com/crossplane-contrib/provider-upjet-gcp , are you folks still affected by this issue ? If I can send a patch to fix this issue, will it be useful for you folks ? There is no release in this repository for past couple of years, so not sure even if the patch is sent, will it be releasable. I work in the cloud SQL engineering team, if you are affected by this issue, Cloud SQL may have issues starting other operations. For example scheduled backups won't be taken as the DB is continuously busy. So this is not a benign issue. |
On reading through the code, the code does a generic diff using golang cmp.Diff, but there are many read only properties on the instance. currentDiskSize being one of them.
So the diff will always return something and it will fail the comparison and it will go on a continuous loop. The bug is trivial to fix and I can send a patch request, if it can be released. |
What happened?
1.9.0
+ gcp provider0.21.0
running on GKE1.21
I did find earlier bug reports but those seem to have been fixed a while ago so not sure anyone else is experiencing this issue.
The text was updated successfully, but these errors were encountered: