Now try to do ssh login to your atomic host, and you should see the dynamic MOTD. You also need to assert that there are no error logs preventing motdgen from writing to /var/run/motdgen due to SELinux. You can do:
ausearch -m avc
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2016-c8948356b9Please login to add feedback.
This update has been submitted for testing by rtnpro.
This update has obsoleted fedora-motd-0.1.2-1.fc24, and has inherited its bugs and notes.
rtnpro edited this update.
This update has been pushed to testing.
This update has reached 3 days in testing and can be pushed to stable now if the maintainer wishes
I booted the fedora atomic 23 vagrant libvirt image, modified
/etc/ostree/remotes.d/fedora-atomic.confto change 23 to 24, didsetenforce 0 && rpm-ostree rebase fedora-atomic:fedora-atomic/24/x86_64/docker-host(wouldn't work w/o permissive), rebooted, did the ostree admin hotfix, installed the pkg, logged out and in to see a MOTD. No selinux denials related to/var/run/motdgen.This update has been submitted for stable by bodhi.
Works for me!
I have booted fedora atomic 24 qcow2 image and the test passed successfully for the image after following the given procedure for testing.
After following the given procedure, I am able to see the dynamic MOTD after logging out and in. There are no error logs preventing motdgen from writing to
/var/run/motdgendue to SELinux.This update has been pushed to stable.