YaST clone_system module errors on ntp.conf changes

This document (7021385) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 12 Service Pack 3 (SLES 12 SP3)

Situation

The following lines  in /etc/ntp.conf were uncommented:
server 127.127.1.0              # local clock (LCL)
fudge  127.127.1.0 stratum 10   # LCL is unsynchronized

After running yast clone_system, the following error was observed:
Internal error. Please report a bug report with logs.
Run save_y2logs to get complete logs.
Details: Invalid value #<CFA::NtpConf::FudgeRecord:0x00000005a18308 @augeas={:key=>"fudge[]", :value=>#<CFA::AugeasTreeValue:0x000
Caller:  /usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:206:in `call_builtin'
The /root/autoinst.xml file does not get created after this error.

The issue cannot be duplicated on SLES12 SP2.

If the following changes are made in /etc/ntp.conf:
server 127.127.1.0 mode 5 prefer
fudge 127.127.1.0 stratum 10

No errors are observed, but /root/autoinst.xml does not get a valid <ntp-client><peers> section.
  <ntp-client>
    <ntp_policy>auto</ntp_policy>
    <peers config:type="list"/>
    <restricts config:type="list"/>
    <start_at_boot config:type="boolean">false</start_at_boot>
    <start_in_chroot config:type="boolean">false</start_in_chroot>
    <sync_interval config:type="integer">5</sync_interval>
    <synchronize_time config:type="boolean">false</synchronize_time>
  </ntp-client>

Resolution

Reported to Engineering. Contact support for a PTF.

Currently you will need to leave the lines commented out and add the tags manually to the /root/autoinst.xml file.

Cause

The problem occurs in yast2-ntp-client-3.2.14-2.5.11 and earlier versions.

Disclaimer

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:7021385
  • Creation Date: 13-Sep-2017
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center