Hi Zied,
On 2 February 2016 at 12:03, Zied ABID <zied+debian@abid.tn> wrote:
Package: cloud.debian.org
Severity: normal
Tags: newcomer
Dear Maintainer,
* What led up to the situation?
Create new instance from one of the official Debian Jessie 8.1
images
(https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie)
* What exactly did you do (or not do) that was effective (or
ineffective)?
Create instance with a volume other than the default size (8GB),
say 30GB.
* What was the outcome of this action?
Root partition still at size 8GB in front of 30GB (EBS) volume
size.
* What outcome did you expect instead?
Root partition should be resized as same as (EBS) volume.
This bug is reproducible in at least 2 tested images (in eu-west-1 and
us-west-1)
This bug affect only Jessie 8.1 images, Wheezy images looks fine.
As a work-around, installing cloud-initramfs-growroot package resolve
the issue
for installed instances (after reboot) or for new instances created
from nested
image.
This is a known issue, which is related to #784004[1]. We are already
tackling it on threads[2][3] at the "debian-cloud" mailing list.
PS: If you consider this issue as a bug, I'm available to reproduce,
test and
validate new AWS images. I'm already looking at Anders Ingemann's
bootstrap-vz
work to find-out how to suggest a patch, but I'm not sure that I'm on
the right
path.
Patches[4][5] were suggested to bootstrap-vz and the most recent one
was merged. What happened is, AFAICT, there were no newer EC2 images
generate using those fixes.
Regards,
Tiago.
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784004
[2]: https://lists.debian.org/debian-cloud/2016/01/msg00035.html
[3]: https://lists.debian.org/debian-cloud/2016/01/msg00056.html
[4]: https://github.com/andsens/bootstrap-vz/pull/239
[5]: https://github.com/andsens/bootstrap-vz/pull/269