On Sat, Sep 10, 2016 at 10:45 PM, Dusty Mabe <dusty@xxxxxxxxxxxxx> wrote: > > > On 09/11/2016 12:22 AM, Dusty Mabe wrote: >> >> >> On 09/10/2016 12:47 PM, Chris Murphy wrote: >>> On Fri, Sep 9, 2016 at 9:28 PM, Dusty Mabe <dusty@xxxxxxxxxxxxx> wrote: >>>> >>>> >>>> Should I open a bug for this? Can we get someone to look at it/work on it? >>> >>> Yes, and I think it needs a dmesg in case partprobe was called but >>> that failed for some reason. And then need to look at the cloud-init >>> code and see if partprobe is being called. This is not the best log, >>> it doesn't report the actual commands its using and the exit code for >>> each command. So we're left wondering if partprobe was called or not. >>> Maybe it's being called but is missing in the image? >> >> I opened a bug here and added some more information to it: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1374968 >> > > and.. this has actually already been reported and the fix is in > updates-testing. > > https://bugzilla.redhat.com/show_bug.cgi?id=1371761 Good catch. Looks like it affects udisks2/storaged as well. -- Chris Murphy _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx