** Changed in: cloud-utils
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619285
Title:
cc_growpart fails on yakkety
To manage notifications about this
This bug was fixed in the package util-linux - 2.28.2-1ubuntu1
---
util-linux (2.28.2-1ubuntu1) yakkety; urgency=medium
* Merge from Debian unstable. Remaining changes:
- Regularly trim SSDs automatically (core-1311-ssd-trimming):
+ Add debian/fstrim-all.cron: Call fstrim
** Changed in: util-linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619285
Title:
cc_growpart fails on yakkety
To manage notifications about
This bug was fixed in the package cloud-utils - 0.29-0ubuntu3
---
cloud-utils (0.29-0ubuntu3) yakkety; urgency=medium
* debian/control: add Suggests for mtools to cloud-image-utils.
* debian/tests: add dep-8 auto package test.
* sync to trunk at revno 302
* ubuntu-cloudimg-q
** Changed in: cloud-utils (Ubuntu)
Status: Confirmed => Fix Committed
** No longer affects: cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619285
Title:
cc_growpart fail
Martin,
I uploaded just the workaround. As shown in that commit message, the exit
values are not reliable. Long ago I'd added the workaround, so the change here
was really just to extend the list of possible output messages to scrape for.
Not great, but will work.
I also added a autopackage t
** Branch linked: lp:~smoser/ubuntu/yakkety/cloud-utils/pkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619285
Title:
cc_growpart fails on yakkety
To manage notifications about this bug go to:
h
@Scott, thanks for drilling this down! If that patch got reverted in
upstream master, is there a reason to not do the same in the current
yakkety package, instead of working around it in cloud-init? Or would
checking the output message be more robust as the exit code is
effectively broken?
--
You
** Also affects: cloud-utils
Importance: Undecided
Status: New
** Changed in: cloud-utils
Status: New => Fix Committed
** Changed in: cloud-utils
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Branch linked: lp:cloud-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619285
Title:
cc_growpart fails on yakkety
To manage notifications about this bug go to:
https://bugs.launchpad.net/c
I'm going to fix this in cloud-utils (growpart) in the way that we'd addressed
this issue in the past:
scraping text output of the command ran with LANG=C.
Not the best fix in the world.
What happened that caused this was that this commit is in 2.28.1:
https://git.kernel.org/cgit/utils/util-
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619
I launched an instance that had an older util-linux (2.28-5ubuntu2).
cp /sbin/sfdisk /sbin/sfdisk.old
mkdir /tmp/bin
ln -s /sbin/sfdisk.old /tmp/bin
sudo apt-get install util-linux
Then, i can see failure with the 'test-growpart' script at [1]
sudo ./test-growpart
but this works as expected
sudo
Possibly/likely related bug, or even a duplicate: bug 1618525
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619285
Title:
cc_growpart fails on yakkety
To manage notifications about this bug go to:
Confirmed in local qemu. I built an image with autopkgtest-buildvm-
ubuntu-cloud (which downloads the current yakkety image and boots it and
does some initialization), same error there. So not related to
Scalingstack.
** Changed in: cloud-init (Ubuntu)
Importance: Critical => Undecided
** Chan
this breaks all autopkg tests in yakkety which need more than the two
initial 2GB
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
16 matches
Mail list logo
