@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 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/cloud-utils/+bug/1619285/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
