"could not complete the operation" error while requesting an IPv4 address

閲覧: 175 回
最初の未読メッセージにスキップ

Guoliang Qian

未読、
2017/12/13 9:12:092017/12/13
To: Google Cloud SQL discuss
Hi,

I've been seeing this error since morning.  Has anyone experienced the same?  (BTW, an authorized network has been added first.)

Any suggestion how to deal with it is highly appreciated.

Very grateful for your time looking into it.

Thanks,

Bill

Carlos (Cloud Platform Support)

未読、
2017/12/13 17:03:282017/12/13
To: Google Cloud SQL discuss
Did you obtain this error while creating or upgrading an existing instance? 

If so which were the exact parameters you were using? Let me know if this was a PostgreSQL or MySQL instance, the machine type, region and zone. I would like to try to reproduce the behavior. I have seen this message appear when there are not enough resources in the zone. Nevertheless I find strange it is referring IP addresses.

Guoliang Qian

未読、
2017/12/13 17:14:002017/12/13
To: Google Cloud SQL discuss

It is an existing D1 MySQL instance in us-cental.  

However, I wasn't upgrading it.  I have been seeing it simply after requesting an IPv4 address.

Screenshot attached.

Guoliang Qian

未読、
2017/12/14 7:07:162017/12/14
To: Google Cloud SQL discuss
Hi,

I saw something weird just now.  I tied to request an IPv4 address again and hope the issue would have been resolved.  I did see "Done" in the normal lower left corner.  However, the IP address was not showing on the page.  And I clicked on "Request IPv4 Address" again, the "Could not complete operation" message was shown.

Thanks, 

Bill

Carlos (Cloud Platform Support)

未読、
2017/12/14 11:11:432017/12/14
To: Google Cloud SQL discuss
I was just able to create a first generation instance in “us-central” with no IP and after that patch it to obtain an address. Please try to assign the IP using the CLI, it might reveal additional information.

Guoliang Qian

未読、
2017/12/14 14:55:402017/12/14
To: Google Cloud SQL discuss
I am getting "ERROR: (gcloud.sql.instances.patch) HTTPError 403: The client is not authorized to make this request.".

Guoliang Qian

未読、
2017/12/14 16:37:272017/12/14
To: Google Cloud SQL discuss
Hi,

I am finally able to run the gcloud command after properly authenticated/authorized for the instance.  

However, now I am getting "ERROR: (gcloud.sql.instances.patch) HTTPError 503: Service temporarily unavailable. This is most likely a transient error. Please retry."

Thanks,

Bill

Andrew Karpushin

未読、
2017/12/14 16:51:322017/12/14
To: Google Cloud SQL discuss
I also can't request IPv4 address for my instance in europe-west1 for several days already. MySQL first generation.

Guoliang Qian

未読、
2017/12/15 6:47:102017/12/15
To: Google Cloud SQL discuss
Hi Andrew,

Have you been able to assign IPv4 now?  I still can't.

Thanks,

Bill

Karthick (Cloud Platform Support)

未読、
2017/12/15 14:48:512017/12/15
To: Google Cloud SQL discuss
Hello,

Can you please share your project number and the affected instance name along with the output of "gcloud --verbosity=debug sql instances patch INSTANCE NAME --assign-ip" , in a private message ?

This way I can take it to engineering team and troubleshoot further.


Guoliang Qian

未読、
2017/12/15 15:13:292017/12/15
To: Google Cloud SQL discuss
information has been sent privately.

Guoliang Qian

未読、
2017/12/20 6:47:162017/12/20
To: Google Cloud SQL discuss
Hi Karthick,

Wonder if there is any update on this issue.  I am still not able to assign an IP to the instance.

Thanks,

Bill

nau...@google.com

未読、
2017/12/20 10:12:412017/12/20
To: Google Cloud SQL discuss
Hello Bill 

I have followed up with the engineering team and will post an update once have any information. 

Thank you for the patience. 

Guoliang Qian

未読、
2017/12/27 7:27:482017/12/27
To: Google Cloud SQL discuss
Hi,

It's been two weeks without any resolution.  I can't afford to keep paying for the instance and not being able to conduct and any work.  I have cloned a new instance, which works properly.  

Can you please let me know what option I have to get a more prompt update in the future?

Thanks,

Bill

Karthick (Cloud Platform Support)

未読、
2017/12/27 19:45:502017/12/27
To: Google Cloud SQL discuss
Hello Guoliang, 

I have created an Public Issue Tracker for you to check on the updates and resolution. We are experiencing a higher-than-normal volume in the Issue Tracker at the moment, and so our response time was slightly delayed. Thank you for your patience as we get to each issue.

Karthick (Cloud Platform Support)

未読、
2017/12/28 17:18:512017/12/28
To: Google Cloud SQL discuss
Hello Guoliang, 

It looks like the instance in the log you have provided is deleted, and we can't find any logs from the backend that are relevant. However, we have an ongoing bug that looks related to this and our internal team is working on the fix. You can track Public Issue Tracker for any updates we have. 


全員に返信
投稿者に返信
転送
新着メール 0 件