This is a very interesting idea, but care should be applied when
combined with cloud (disk) images. In particular, I worry that if an
encrypted disk image is distributed that the well-known passphrase could
be used to get the master key from any pristine copy of the disk image.
In effect, the mast
I think we've been avoiding this issue so far because the file system is
being created without partitioning the disk (layout: False). With "layout:
False", I'm guessing that whether gpt or mbr is specified makes no
difference.
Mike
On Thu, Apr 12, 2018 at 8:41 PM, Scott Moser
wrote:
> You prob
00 blocks) /dev/vdb too big to be
expressed
in 32 bits using a blocksize of 4096.
The default should switch to ext4. It so happens that this matches the
default in DataSourceAzure.py.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Assignee: Mike Gerdts (mg
** Changed in: cloud-init
Assignee: (unassigned) => Mike Gerdts (mgerdts)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667735
Title:
cloud-init doesn't retry metadata lookups a
