I think it would be nice if the /etc/motd (or some other mechanism) would inform users of pending security updates on login.
And, a welcome side-effect is that having cloud images check with the update server network periodically gives us a better measure of whether we're actually being used. Right now, cloud images are probably being drastically undercounted, as many aren't updated ever.
See also this RFE for yum-cron to output to motd: https://bugzilla.redhat.com/show_bug.cgi?id=995537
I am not sure if this is the right place to answer this (vs the bug reference in comment:1), but the reason many cloud instances do not get updated is because they operate in a MTTR vs. a MTBF model. In other words, an instance should never get updates, rather, when updates are required, a new instance (w/ the updates) should be created, the application tested, traffic migrated, and then the original instance is destroyed.
In recognition that most computing stereotypes are well shy of the 80% rule :), I think having this function, perhaps even by default, is a good thing, as long as it is "disable-able" easily. In many environments, the performance and/or network hit of collecting this information would not be acceptable.
What: A system to display a count (or list?) of updates waiting to be applied
Where: New code needs to be written. https://bugzilla.redhat.com/show_bug.cgi?id=995537 could help.
Why: Helpful to users. Side-effect: we can count checkins.
When: nice by F21 release.
Who: (TBD)
Started working on it here: https://github.com/rtnpro/fedora-motd
Patch for adding and enabling Fedora MOTD on Fedora cloud base kickstart file spin_kickstarts_fedora_cloud_base_fedora_motd.patch
Could some help with building Fedora cloud base image with the above patch applied to the kickstart file?
Closing this ticket as part of trac clean up process. If you want to reopen, please reopen it after we move to pagure.io as atomic-wg.
Login to comment on this ticket.