<html><head>
<meta name="Generator" content="Novell Groupwise Client (Version 18.2.0 Build: 135307)">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head>
<body style="font: 10pt/normal Segoe UI; font-size-adjust: none; font-stretch: normal;"><div class="GroupWiseMessageBody" id="GroupWiseSection_1617623464000_TWIN.Administrator@twinmro.com_4D673D8009A70000BE0E37010000C42E_"><div><br></div><div>I have confirmation of a carryover chronyd bug from SP2 into SP3 (bugzilla number 1173760).</div><div><br></div><div>Steps to reproduce;</div><div>- Built a new x86_64 SLES15 SP3 Beta box and updated.</div><div>- Setup an internal time source for chronyd on install both manually and with autoyast - no issues. Time is fine.</div><div>- Install FIPS pattern, and set grub bootloader kernel boot option 'fips=1' and restart</div><div>- chronyd fails to load with internal time source. If a public time source is used for chronyd, it seems to load fine (but of course, one can't use a public source if servers are not supposed to see the internet or are "air gapped").</div><div><br></div><div>We suspect there needs to be something else done on the internal time source, or a local configuration change not documented for FIPS systems; we've tried several different internal time clock sources and manual edits of chronyd configurations -- nothing seems to work. The issue does not exist on SLES 12 systems. Curious to know if others in FIPS environments have seen this behavior with SLE 15 and if there's a workaround...(it seems that we are missing something very simple, admittedly we are not experts with chronyd yet, but so far SUSE support can replicate the issue - but has no solution for us either).</div><div><br></div><div>This post is FYI only. This is a known issue, although not documented in the readme, it's going to limit deployment in many regulated environments... </div><div><br></div><div>Kevin</div><div><br></div></div></body></html>