Error creating Instance Group

KR1
Bronze 1
Bronze 1

I had created an instance template and created a single VM using the template.

Next i tried to create Instance group name: first-instance-group-1 and selected the instance template i created , selected min 03 VM, Location: single zone, Click Create

I  am getting below error

Failed to create instance group first-instance-group-1: Internal error. Please try again or contact Google Support. (Code: '6164C9B4E95AF.70EC525.C8096A0F')

10 7 425
7 REPLIES 7

I face the same error from today morning. Somebody please help. Not able to create or delete instance groups. Not able to add instances to the existing instance groups.

Internal error. Please try again or contact Google Support. (Code: '61656A326A804.26A96F0.650688EA')
internal error. Please try again or contact Google Support. (Code: '61656C9B6D8AA.7F63F3B.20A4D20')
internal error. Please try again or contact Google Support. (Code: '616578F7A13AD.2F5D4B6.FB024C79')

Hi team,

We are also facing the same issue. Someone please help

Failed to update instance group Internal error. Please try again or contact Google Support. (Code: '616596D12388D.13F5655.7D0E3C14')

I am facing the same issue please can someone help on this

Failed to create instance group instance-group-1: Internal error. Please try again or contact Google Support. (Code: '61659E4D255A3.70EC3B6.50A7825')

Hello All,

There is ongoing global issue with MIGs at this moment. 

DamianS_0-1713435469208.png

chers,
DamianS

Hello Damian.

I've had the same issue for two days now. Where were you able to see this incident report? The only status page I'm able to find for Google Cloud is https://status.cloud.google.com/summary , and enabling the "Service Health" API shows "No incidents".

cheers,

RespiceFinem

All,
Highly recommend to enable Health Events for projects or organization to being notified each time something is going wrong within Google Cloud, more info here : https://cloud.google.com/service-health/docs/view-events

cheers,
DamianS

Issue is resolved now. As Damian suggested, I started watching the incidents reported in the Service Health.