MOTD on Public Cloud Instances Unchanged after OS Upgrade
This document (000020640) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise for SAP Applications in Public Clouds (All Versions)
azureuser@sles15sp1:~> head -n 1 /etc/motd
SUSE Linux Enterprise Server 12 SP4 x86_64 (64-bit)
Solution A.Revert to system *-release package default motd
1. Delete the old /etc/motd
# rm /etc/motd
2. Reinstall the *-release package for the basesystem product. It is of utmost importance to install the correct *-release package for the installed SLE product. See Additional Information section for instructions to verify the baseproduct.
For regular SLES systems:
# zypper in --force sles-release
For SLES for SAP systems:
# zypper in --force SLES_SAP-release
Solution B.If desired, one may also manually update the version string to match the new OS version.
When RPM installs the new *-release package during an OS upgrade, the custom motd file causes RPM verification to fail since it was modified from its original state in the package. As a result, the RPM installation saves the new blank motd file as /etc/motd.rpmnew and retains the original motd. This is expected behavior.
The "basesystem" product can be found two ways:
1. Target file of /etc/products.d/basesystem symbolic link.
# ls -l /etc/products.d/basesystem
2. Checking installed products with zypper.
# zypper pd -i
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020640
- Creation Date: 14-Apr-2022
- Modified Date:15-Apr-2022
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com