Open smcdougal opened 3 years ago
@ratagupt FYI ^
Hi, I switched to webui-vue and am having the same issue; the BMC time is lost after reboot or reset.
I cannot repro this using palmetto in qemu built off top of tree from July. I did the steps above roughly except I set the time in the web UI because I had issues with the formatting of the json above (not sure what the issue was there).
I can manually verify that the DHCP UseNTPServers is still set to false, and the NTP Protocol is still disabled. I verified that UseNTP is set to false in /etc/systemd/network/00-bmc-eth0.network before and after the cold reset. 'timedatectl status' shows that the system clock is "not synchronized" and the NTP Service is inactive. But the time I set before the reset was still lost by the time the BMC comes back up.
What hardware do you expect to maintain the time over a cold reboot?
When NTP is turned off and a manual time is set, the manually set time is not retained following a BMC cold reset.
The only modification I made was to change to webui-vue rather than phosphor-webui. This is a Romulus build running in QEMU from a WSL Ubuntu session in Win10.
Version information: root@romulus:/# cat /etc/os-release ID=openbmc-romulus NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)" VERSION="2.10.0-dev" VERSION_ID=2.10.0-dev-393-g98120a8d8-dirty PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro) 2.10.0-dev" BUILD_ID="2.10.0-dev" OPENBMC_TARGET_MACHINE="romulus"
Test Script
But the time I set before the reset was still lost by the time the BMC comes back up.