Description of problem: chronyd.service status is failed after the first reboot: [root@test2 ~]# systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mi 2017-12-06 08:46:08 CET; 10min ago Docs: man:chronyd(8) man:chrony.conf(5) Process: 45816 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=1/FAILURE) Dez 06 08:46:08 test2.example.org systemd[1]: Starting NTP client/server... Dez 06 08:46:08 test2.example.org chronyd[45818]: chronyd version 3.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS +IPV6 +DEBUG) Dez 06 08:46:08 test2.example.org chronyd[45818]: Fatal error : Invalid command at line 9 in file /etc/chrony.conf Dez 06 08:46:08 test2.example.org chronyd[45816]: Invalid command at line 9 in file /etc/chrony.conf Dez 06 08:46:08 test2.example.org systemd[1]: chronyd.service: control process exited, code=exited status=1 Dez 06 08:46:08 test2.example.org systemd[1]: Failed to start NTP client/server. Dez 06 08:46:08 test2.example.org systemd[1]: Unit chronyd.service entered failed state. Dez 06 08:46:08 test2.example.org systemd[1]: chronyd.service failed. [root@test2 ~]# cat /etc/chrony.conf # This file has been migrated or modified by imgbased driftfile /var/lib/chrony/drift server 0.centos.pool.ntp.org iburst server 1.centos.pool.ntp.org iburst server 2.centos.pool.ntp.org iburst server 3.centos.pool.ntp.org iburst makestep 1.0 3 disable monitor logdir /var/log/chrony rtcsync [root@test2 ~]# Version-Release number of selected component (if applicable): ovirt-node-ng-installer-master-2017120509 imgbased-1.0.999-0.201711282318gite17aefe.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1. Install ovirt-node-ng-installer-master-2017120509.iso 2. Enable the NIC, enable network time, and configure the ntp servers 3. Finish installation 4. Reboot and log into system 5. Check chronyd.service status using `systemctl status chronyd` Actual results: 1. After step5, the status of chronyd.service is failed Expected results: 1. After step5, the status of chronyd.service should be 'active (running)' Additional info:
QE can reproduce this issue. Test version: ovirt-node-ng-installer-master-2017120509 imgbased-1.0.999-0.201711282318gite17aefe.el7.centos.noarch chrony-3.1-2.el7.centos.x86_64 Test steps: 1. Install ovirt-node-ng-installer-master-2017120509.iso 2. Enable the NIC, enable network time, and configure the ntp servers 3. Finish installation 4. Reboot and log into system 5. Check chronyd.service status using `systemctl status chronyd` Test result: The status of chronyd.service is failed
Test version: ovirt-node-ng-installer-master-2017121109 imgbased-1.0.999-0.201712070959git7a10369.el7.centos.noarch chrony-3.1-2.el7.centos.x86_64 Test steps: 1. Install ovirt-node-ng-installer-master-2017120509.iso 2. Enable the NIC, enable network time, and configure the ntp servers 3. Finish installation 4. Reboot and log into system 5. Start chronyd.service using `systemctl start chronyd` 5. Check chronyd.service status using `systemctl status chronyd` Test result: The status of chronyd.service is running
Test version: ovirt-node-ng-4.2.1-0.20180111.0+1 imgbased-1.0.5-1.el7.centos.noarch chrony-3.1-2.el7.centos.x86_64 Test steps: 1. Install ovirt-node-ng-installer-ovirt-4.2-pre-2018011121.iso 2. Enable the NIC, enable network time, and configure the ntp servers 3. Finish installation 4. Reboot and log into system 5. Start chronyd.service using `systemctl start chronyd` 5. Check chronyd.service status using `systemctl status chronyd` Test result: The status of chronyd.service is running, so the bug is fixed, change bug status to VERIFIED. # systemctl start chronyd # systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; disabled; vendor preset: enabled) Active: active (running) since Tue 2018-01-30 04:45:03 EST; 4h 58min left Docs: man:chronyd(8) man:chrony.conf(5) Process: 12920 ExecStartPost=/usr/libexec/chrony-helper update-daemon (code=exited, status=0/SUCCESS) Process: 12916 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 12918 (chronyd) CGroup: /system.slice/chronyd.service └─12918 /usr/sbin/chronyd Jan 30 04:45:03 dhcp-10-212.nay.redhat.com systemd[1]: Starting NTP client/server... Jan 30 04:45:03 dhcp-10-212.nay.redhat.com chronyd[12918]: chronyd version 3.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS +IPV6 +DEBUG) Jan 30 04:45:03 dhcp-10-212.nay.redhat.com systemd[1]: Started NTP client/server. Jan 30 04:45:09 dhcp-10-212.nay.redhat.com chronyd[12918]: Selected source 10.5.27.10 Jan 30 04:45:09 dhcp-10-212.nay.redhat.com chronyd[12918]: System clock wrong by -17985.780475 seconds, adjustment started Jan 29 23:45:23 dhcp-10-212.nay.redhat.com chronyd[12918]: System clock was stepped by -17985.780475 seconds Hint: Some lines were ellipsized, use -l to show in full.
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.