We receive hardware degradation notices periodically, and always try to restart the host ourselves to migrate it before AWS doe it autonomously. We did a restart on one last weekend, and today, AWS rebooted the host anyway. The notice states * What will happen when I stop and start the instance? You can stop and start the instance at any time before the scheduled start time of the scheduled reboot event. This will migrate the instance to a new host and the instance will not have to undergo the scheduled maintenance. Why then, if we had already stopped and started the instance, would it perform the maintenance anyway?

Received degradation notice. Restarted instance during outage window. AWS Rebooted it anyway

We receive hardware degradation notices periodically, and always try to restart the host ourselves to migrate it before AWS doe it autonomously. We did a restart on one last weekend, and today, AWS rebooted the host anyway. The notice states

What will happen when I stop and start the instance? You can stop and start the instance at any time before the scheduled start time of the scheduled reboot event. This will migrate the instance to a new host and the instance will not have to undergo the scheduled maintenance.

Why then, if we had already stopped and started the instance, would it perform the maintenance anyway?

トピック

計算する

タグ

Amazon EC2

言語

English

Thomas Spitzer

質問済み 3ヶ月前95ビュー

1回答

新しい順
投票が多い順
コメントが多い順

承認された回答

Sorry to hear that. Did you check to confirm the description of the scheduled events changed to [Completed] after you manually reboot the instance before the scheduled reboot? It could be possible that the manual reboot didn't clear the scheduled event or another reboot is required. Here is more detail how to react to scheduled events for instances.

エキスパート

AWS-User-alantam

回答済み 2ヶ月前

エキスパート

Oleksii Bebych

レビュー済み 2ヶ月前

エキスパート

Riku_Kobayashi

レビュー済み 2ヶ月前

Thomas Spitzer
2ヶ月前
thanks, useful detail in the documentation. Did not realize we could confirm the 'Completion' of the event based on our action. Its never been a problem before, but the unplanned reboot resulted in disruption to a number of our customers, so naturally there was some consternation.

Received degradation notice. Restarted instance during outage window. AWS Rebooted it anyway

関連するコンテンツ