for this bug, later in the cycle we'll be publishing a "rescue" EBS volume for booting from. All the other options would include a dramatic change of behavior that would not be desireable for users -- like a "rescue SSH console" or some other nonsense.
The path forward will be:
- Canonical will publish a "rescue volume" which is a cloud image with a label of "RESCUE_VOL".
- Cloud-Init on boot will recognize this rescue volume and swtich over to the rescue volume (Cloud init launches before the general mount)
- Users will then rescue their system the same way
The rescue volumes should land sometime this cycle.
for this bug, later in the cycle we'll be publishing a "rescue" EBS volume for booting from. All the other options would include a dramatic change of behavior that would not be desireable for users -- like a "rescue SSH console" or some other nonsense.
The path forward will be:
- Canonical will publish a "rescue volume" which is a cloud image with a label of "RESCUE_VOL".
- Cloud-Init on boot will recognize this rescue volume and swtich over to the rescue volume (Cloud init launches before the general mount)
- Users will then rescue their system the same way
The rescue volumes should land sometime this cycle.