How to avoid instance reboot without my consent/How to utilize Live migration feature in OCI
(Doc ID 2798370.1)
Last updated on MARCH 28, 2022
Applies to:OCI Compute - Version N/A and later
Information in this document applies to any platform.
You have a OCI hosted VM machine which got unexpectedly rebooted and you receive a Oracle CN(Customer Notification) mentioning the same with issue description mentioning an underlying Infrastructure issue. It will look like below:
The Oracle Cloud Infrastructure team detected the instance(s) identified below rebooted one or more times during the incident window listed in this notification, due to an error within the underlying infrastructure.
The error has been corrected and our monitoring indicates these instance(s) are now in a healthy state. We recommend that you verify the affected instance(s) are performing as expected. If assistance is required, please contact support.
Root Cause Analysis: A Network Interface Card experienced a failure, causing a hypervisor servicing customer instances to enter an unhealthy state. To mitigate the impact a reboot migration was performed to move any affected customer instances onto healthy infrastructure.
Impact start time in UTC: YYYY-MM-DDT00:36:00Z
Impact end time in UTC: YYYY-MM-DDT00:50:09.968Z
Tenant and instance list:
customerAd:Region and AD details
instanceId: Details of your instance ocid ,
instanceName: Details of your instance name ,
tenantName: Details of Tenancy Name/ocid,
compartmentId: Details of compartment ocid
OCI hosted VM reboot happened
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Additional Follow up FAQ:|
>>How to check whether you have opted for this feature?