We are experiencing an issue with Google Compute Engine RHEL and CentOS 7 and 8 instances. Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart.

482 views
Skip to first unread message

Google Cloud Platform Status

unread,
Jul 30, 2020, 11:49:52 AM7/30/20
to gce-ope...@googlegroups.com
Description: We are experiencing an issue with Google Compute Engine RHEL and CentOS 7 and 8 instances.

Symptoms: Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart. Customers should not update or reboot instances running RHEL or CentOS 7 and 8.

Our engineering team continues to investigate the issue.

We will provide an update by Thursday, 2020-07-30 09:30 US/Pacific with current details.

We apologize to all who are affected by the disruption.

Diagnosis: Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart.

Workaround: Do not update or reboot instances running RHEL or CentOS 7 and 8.

Google Cloud Platform Status

unread,
Jul 30, 2020, 12:27:34 PM7/30/20
to gce-ope...@googlegroups.com
Description: We are experiencing an issue with Google Compute Engine RHEL and CentOS 7 and 8 instances.

Symptoms: Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart. Customers should not update or reboot instances running RHEL or CentOS 7 and 8.

Our engineering team continues to investigate the issue. We are also preparing instructions for recovery from this issue for affected instances.

We will provide an update by Thursday, 2020-07-30 10:15 US/Pacific with current details.

Google Cloud Platform Status

unread,
Jul 30, 2020, 12:41:51 PM7/30/20
to gce-ope...@googlegroups.com
Description: We are experiencing an issue with Google Compute Engine RHEL and CentOS 7 and 8 instances.

Symptoms: Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart. Customers should not update or reboot instances running RHEL or CentOS 7 and 8.

Our engineering team continues to investigate the issue.

We will provide an update by Thursday, 2020-07-30 10:30 US/Pacific with current details.

Diagnosis: Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart with errors messages referring to a combination of: "X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID", "FXSAVE_STATE" or "Find image based on IP".

This issue affects instances with specific versions of the shim package installed. To find the currently installed shim version, use the following command: rpm -q shim-x64

Affected shim versions:
CentOS 7: shim-x64-15-7.el7_9.x86_64
CentOS 8: shim-x64-15-13.el8.x86_64
RHEL 7: shim-x64-15-7.el7_8.x86_64
RHEL 8: shim-x64-15-14.el8_2.x86_64

Workaround: Do not update or reboot instances running RHEL or CentOS 7 and 8. If you are on an affected shim version, run "yum downgrade shim\* grub2\* mokutil" to downgrade to the correct version. This command may not work on CentOS 8. If you have already rebooted, you will need to attach the disk to another instance, chroot into the disk, then run the yum downgrade command.

Google Cloud Platform Status

unread,
Jul 30, 2020, 12:52:23 PM7/30/20
to gce-ope...@googlegroups.com
Description: We are experiencing an issue with Google Compute Engine RHEL and CentOS 7 and 8 instances.

Symptoms: Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart with errors messages referring to a combination of: "X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID", "FXSAVE_STATE" or "Find image based on IP".

This issue affects instances with specific versions of the shim package installed. To find the currently installed shim version, use the following command: `rpm -q shim-x64`

Affected shim versions:

CentOS 7: shim-x64-15-7.el7_9.x86_64
CentOS 8: shim-x64-15-13.el8.x86_64
RHEL 7: shim-x64-15-7.el7_8.x86_64
RHEL 8: shim-x64-15-14.el8_2.x86_64

Workaround: Do not update or reboot instances running RHEL or CentOS 7 and 8. If you are on an affected shim version, run `yum downgrade shim\* grub2\* mokutil` to downgrade to the correct version. This command may not work on CentOS 8. If you have already rebooted, you will need to attach the disk to another instance, chroot into the disk, then run the yum downgrade command.

Our engineering team continues to investigate the issue.

We will provide an update by Thursday, 2020-07-30 11:00 US/Pacific with current details.
Reply all
Reply to author
Forward
0 new messages