Comment 7 for bug 1619285

@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?