Can't Repro
Status Update
No update yet.
Comments
gs...@google.com
yi...@google.com
Hi, this error only affects Cloud SDK version 186. It was previously reported in
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
ap...@google.com
🤖 This is an automatic update. The status of the related internal issue(s) listed in "Blocked By" has changed, so we've done the following:
* Moved this issue to a locked sub-component, because the issue has been closed. Please open a new issue if you need Google to re-visit this topic.
You can read more about what these statuses mean athttps://developers.google.com/issue-tracker/concepts/issues#fields
* Moved this issue to a locked sub-component, because the issue has been closed. Please open a new issue if you need Google to re-visit this topic.
You can read more about what these statuses mean at
ap...@google.com
🤖 This is an automatic update. The status of the related internal issue(s) listed in "Blocked By" has changed, so we've done the following:
* Moved this issue to a locked sub-component, because the issue has been closed. Please open a new issue if you need Google to re-visit this topic.
You can read more about what these statuses mean athttps://developers.google.com/issue-tracker/concepts/issues#fields
* Moved this issue to a locked sub-component, because the issue has been closed. Please open a new issue if you need Google to re-visit this topic.
You can read more about what these statuses mean at
Description
Our high availability memorystore instance changed its IP address
What you expected to happen:
According to this documentation, connection attempts should be redirected:
However, our redis instance changed from 10.0.0.3 to 10.0.0.4 and connection attempts to 10.0.0.3 timeout.
The documentation specifying the IP address range says we can set the IP address, but it is not clear how that is done.
Steps to reproduce:
Unknown
Other information (workarounds you have tried, documentation consulted, etc):
Using python redis library with StrictRedis client. At this point our workaround to proactively adjust the IP is to try to connect to each one in a range, one by one, which feels wrong and we're not sure what happens if we connect to a failover instance or if that is even possible. As a temporary workaround we simply moved the IP to the config but that still means we have to update and redeploy if this happens again.