offline update fails when /var is a separate volume

[Chris Murphy]

On Wed, Jan 14, 2015 at 5:39 AM, Kamil Paral <kparal at redhat.com> wrote:
>> > Questions:
>> > a.) Is the silent fail for offline updates itself a bug or need to be
>> > a feature request?
>>
>> I think the user should be informed about the results of an update, both
>> successful and unsuccessful. (For successful updates I do see a notification
>> on the next boot.)
>>
>> If you can, please file a ticket in gnome bugzilla.
>
> I was "lucky" enough to hit this today (due to https://bugzilla.redhat.com/show_bug.cgi?id=1182090), and I see an error message:
>
> http://i.imgur.com/sMnbzCc.png
> http://i.imgur.com/eW8KryD.png
>
> I have no idea why it was silent for you (maybe it's a bug), but the functionality seems to be there.

My guess is it's because the offline update service isn't even
initiated so the update hasn't failed because it hasn't started.
Failing to start is a different kind of failure and it doesn't look
like there's notification for this.

-- 
Chris Murphy