3 ms·
So far I'm 3 for 3 on stopped/started machines that come back no longer having the scheduled reboot event - maybe the problem isn't as annoying as we're thinkin
by ecaron 12y ago
So far I'm 3 for 3 on stopped/started machines that come back no longer having the scheduled reboot event - maybe the problem isn't as annoying as we're thinking?
(Edited because I said "reboot" and meant "stop/start")
- thezilch 12y agoThe post claims that it could take several hours before their scans identify hosts that were claimed during restarts.
- rands3311 12y agoA reboot won't address it at all (it also keeps you on the same host).. no point in doing that. From the e-mail notification: "You will not be able to stop/start or re-launch instances in order to avoid this maintenance update."
- ecaron 12y agoSorry, I should have phrased better. I issued a "stop and start". Per the AWS thread: > While executing a stop/start is absolutely fine to do, there is not a guarantee that you will land on an updated host. We are periodically polling for new instances and those impacted will receive new maintenance notifications accordingly. Which I take to mean there's a chance you could land on an updated host. I'll update if any of those machines come back to the Events view.
- deleted 12y ago[deleted]