ntp service on centos is ntp.service, but cloud-init uses nptd.service

[ubuntu-server-builder]

This bug was originally filed in Launchpad as LP: #1897915

Launchpad details

affected_projects = []
assignee = smoser
assignee_name = Scott Moser
date_closed = 2020-11-24T17:59:03.735797+00:00
date_created = 2020-09-30T15:11:51.724190+00:00
date_fix_committed = 2020-10-01T16:36:39.404502+00:00
date_fix_released = 2020-11-24T17:59:03.735797+00:00
id = 1897915
importance = medium
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1897915
milestone = None
owner = smoser
owner_name = Scott Moser
private = False
status = fix_released
submitter = smoser
submitter_name = Scott Moser
tags = []
duplicates = []

Launchpad user Scott Moser(smoser) wrote on 2020-09-30T15:11:51.724190+00:00

The ntp (client) service file installed by the centos 7 'ntp' package is named
'ntpd' (note the d), but cloud-init's cc_ntp module identifies that
'service_name' as 'ntp'.

See below on centos 7. For centos 8, there is no 'ntp' package that I see,
it seems to have been replaced by chrony.

[root@cent71 ~]# rpm -ql ntp | grep systemd
/usr/lib/systemd/ntp-units.d/60-ntpd.list
/usr/lib/systemd/system/ntpd.service
[root@cent71 ~]# systemctl status ntp.service
Unit ntp.service could not be found.
[root@cent71 ~]# systemctl cat ntp.service
No files found for ntp.service.
[root@cent71 ~]# systemctl cat ntpd.service

/usr/lib/systemd/system/ntpd.service

[Unit]
Description=Network Time Service
After=syslog.target ntpdate.service sntp.service

[Service]
Type=forking
EnvironmentFile=-/etc/sysconfig/ntpd
ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS
PrivateTmp=true

[Install]
WantedBy=multi-user.target

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2020-09-30T15:42:47.868931+00:00

#589

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2020-10-01T16:36:38.820794+00:00

fix landed at #589 .
33c6d5c

[ubuntu-server-builder]

Launchpad user Chad Smith(chad.smith) wrote on 2020-11-24T17:59:05.541402+00:00

This bug is believed to be fixed in cloud-init in version 20.4. If this is still a problem for you, please make a comment and set the state back to New

Thank you.