Public bug reported:
When using the AWS::EC2::Volume and AWS::EC2::VolumeAttachment options
to add a volume to an AWS::EC2::Instance on AWS EC2, the volume is not
immediately available on the instance.
This causes fs_setup and disk_setup to fail.
What would prevent this failure is a "wait" option on both fs_setup and
disk_setup, which if true, will cause cloud-init to wait until the
device exists (caused by AWS catching up and attaching the device)
before continuing.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1832645
Title:
fs_setup/disk_setup: option to wait for the device to exist before
continuing
Status in cloud-init:
New
Bug description:
When using the AWS::EC2::Volume and AWS::EC2::VolumeAttachment options
to add a volume to an AWS::EC2::Instance on AWS EC2, the volume is not
immediately available on the instance.
This causes fs_setup and disk_setup to fail.
What would prevent this failure is a "wait" option on both fs_setup
and disk_setup, which if true, will cause cloud-init to wait until the
device exists (caused by AWS catching up and attaching the device)
before continuing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1832645/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
