Red Hat Bugzilla – Bug 823638
RFE: RHEL AMI MOTD
Last modified: 2013-01-30 15:39:24 EST
Description of problem:
The Message of the Day sucks in RHEL AMIs
Steps to Reproduce:
1. Launch a RHEL AMI
2. Log in and review the non-existent, boring MOTD
No MOTD given
Maybe include a number of updates available or something.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Is this still an issue?
Is this cloud-init related? If so, since the bug was initially filed,
a much newer version of cloud-init is now targeted for RHEL6.4.
Please confirm this is still an issue and if it is cloud-init
If it is still an issue is it still a feature that is needed in
6.4 and if so, what are the requirements?
It's still needed but I don't know if I'd call the MotD a blocker.
If an AMI does not contain the cloud-init package is the MOTD correctly
What version of cloud-init is being used?
Please direct me to the AMI that depicts this issue.
Why is this an issue for the AMI, when it seems to act the same
as the bare metal, el6, installation I have where there also is
The RFE was just to have an MotD, instrumented by cloud-init. It's not a blocker, I'll propose the next release.
/etc/motd is provided in package "setup". I think using package "cloud-init" to add content to it would be a kludge. Why not just update the "setup" package to add the content?
Any reason why the component shouldn't be changed to: "setup" ?
Moving to Component: "setup" since it provides /etc/motd.
If /etc/motd is to have the suggested banner content it should
likely be delivered that way and not altered by cloud-init at
boot time. Since not all images will use cloud-init and ...
Traditionally, motd is intentionally empty in the setup package - as it should be used for administrators for MOTD. I don't think we should provide any default there. There are other files in setup, which are modified by other packages/users - and it is expected this may happen - like /etc/exports, /etc/passwd , /etc/shadow ...therefore they don't have checks for md5 mtime and size in rpm -V. For me it is wontfix for setup package - but if you want to modify it in cloud-init package, feel free to do so (please take it back, otherwise I'll just close it)...