You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When specifying an amazon-ebs builder, I'm trying to set the boot volume size with launch_block_device_mappings. By the above bug, I should set this to "xvda" for Windows root devices.
May relate to #122.
When specifying an amazon-ebs builder, I'm trying to set the boot volume size with launch_block_device_mappings. By the above bug, I should set this to "xvda" for Windows root devices.
However, with the hcl code,
I get three volumes. The goal is to increase /dev/sda1 from 30 -> 50GB, but instead I get a new volume:
|
device_name = "/dev/xvda"
||--------|------|------|
| vol-006f0d5xxxx | /dev/sda1 | 30 | Attached | 2023/12/15 |
| vol-07130xxx | /dev/xvda | 50 | Attached | 2023/12/15 |
| vol-0a14a96xxx | xvdb | 100 | Attached |
|
device_name = "xvda"
||------|------|------|
| vol-0279fxxx | /dev/sda1 | 30 | Attached | 2023/12/15 |
| vol-03214xxx | xvda | 50 | Attached | 2023/12/15 |
| vol-0111xxx | xvdb | 100 | Attached |
The two xvdX volumes are kept separate and neither applies to the root volume. However, when I specify either
/dev/sda
orsda
, I get an error:I believe this is a bug or regression. Or is there something wrong with the builder config?
The text was updated successfully, but these errors were encountered: