offline update fails when /var is a separate volume
Kamil Paral
kparal at redhat.com
Wed Jan 14 11:28:51 UTC 2015
> This is on Fedora 21.
>
> The gist is that /var gets mounted later than the check for
> /var/.updated used to trigger offline updates. Therefore if you have a
> separate /var volume, rather than a directory, you're not getting
> updates, and this is a silent fail.
> https://bugzilla.redhat.com/show_bug.cgi?id=1178978
>
> 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.
> b.) Should this be a common bugs for Fedora 21? It's probably rare to
> both have /var separate and depend on offline updates as the sole
> update mechanism.
It fits the CommonBugs purpose, in my opinion.
> c.) Should this be set to Rawhide? It's not fixed in a newer version
> of systemd, so I imagine it's a problem on Rawhide also and it's a
> beta criteria violation: "The installed system must be able to
> download and install updates with the default graphical package
> manager in all release-blocking desktops."
I think you can leave it reported against F21, but please propose it as a F22BetaBlocker. Describe that it also affects Rawhide/F22. Thanks!
More information about the test
mailing list