Can't access to instances locate at us-central1-c zone

[HS Ho]

I'm facing issue accessing my instances in us-central1-c zone, any network issue at that zone?

[Ing. José de Jesús Vargas Ibáñez]

That’s the zone we’re my servers are running. They are back online now.

El El jue, 11 de octubre de 2018 a la(s) 18:52, HS Ho <hsho.et...@gmail.com> escribió:

I'm facing issue accessing my instances in us-central1-c zone, any network issue at that zone?

--
© 2018 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
 
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-dis...@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussio...@googlegroups.com.
To post to this group, send email to gce-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/a2d8e1b1-b25c-4e0d-a643-7ffe67bdefdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

José de Jesús Vargas Ibáñez

Gestor de proyectos

E-mail: jesus....@codes.com.mx

Oficina: +52 (55) 5362 9691

www.codes.com.mx

[Veera (Google Cloud Support)]

Hello, 

Thank you for contacting Google Cloud Platform Support. I understand you were unable to access instance in us-central1-c. There was a known issue in Google Cloud Networking in us-central1-c at that time which has been fixed as of 17:30 PST. I would like to apologize for any inconvenience this issue may have caused to you. You can follow this Google Cloud dashboard [1] for further updates on this issue.

[1] https://status.cloud.google.com/incident/cloud-networking/18016

[Arek Fryz]

Hello,

After our servers come online after yesterday outage we lost sudoers on our servers.

When trying to sudo console shows:

google_accounts_daemon: gpasswd: user 'xxxx' is not a member of 'google-sudoers'

google-accounts: WARNING Could not update user xxxx. Command '['gpasswd', '-d', 'xxxx', 'google-sudoers']' returned non-zero exit status 3.

It happens on all servers affected by outage. As a workaround/fix I added enable-oslogin metatag to instances and that created new user account with sudo configured correctly. I'm wondering if it happened that Google implemented and forced "enable-oslogin" (or some other new account management mechanizm) recently and our servers pulled update when we restarted them yesterday or is it something related to outage? Looks like sudoers configs are OK because new account works fine. And I don't see any other errors in logs suggesting what's wrong with old account.

Any suggestions will be appreciated. 

Arek

[xchri...@google.com]

I see you were able to resolve this issue here. The solution was to use OS Login to be able to login & have sudo access. From that point you would have the option to add users back to the google sudoers group with command like [10], or continue using OS login to regain sudo access. 

[10] usermod -aG google-sudoers <USERNAME>