7bd9b54388
The Message of the Day (MOTD) is assembled from several sources, including: /etc/motd.head; /etc/sysinv/motd.system; /etc/platform/motd.license; and /etc/motd.tail. In the event that /etc/sysinv/motd.system is missing, the MOTD will simply exclude the system name. During the bootstrap process of controller-0, the motd.system file is generated utilizing the predefined system name. However, this is not the case during the bootstrap process of controller-1, where the file remains ungenerated. The proposed solution initialize the motd.system file using a puppet template during controller-1 unlocking step. Test Plan: - PASS: Fresh Install DX Env - PASS: Verify MOTD message on controller-0. - PASS: Verify MOTD message on controller-1. - PASS: Fresh Install STD Env - PASS: Verify MOTD message on controller-0. - PASS: Verify MOTD message on controller-1. Closes-bug: 2037551 Signed-off-by: Jorge Saffe <jorge.saffe@windriver.com> Change-Id: I97b7e140baf837aecd961d7ea8fc5947fcae2106
stx-puppet
The starlingx/stx-puppet repository handles the Puppet service1.
The Puppet service runs during bootstrap, and at every reboot, to provide a consistent configuration across the StarlingX system nodes.
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest2.