Bug 1272085 - timedatectl reports "NTP synchronized: yes" after "set-ntp off"
timedatectl reports "NTP synchronized: yes" after "set-ntp off"
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: systemd-maint
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-15 08:49 EDT by Marius Vollmer
Modified: 2016-07-19 14:13 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 14:13:43 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marius Vollmer 2015-10-15 08:49:01 EDT
Description of problem:

When using systemd-timesyncd, timedatectl still claims that the clock is synchronized via NTP after switching NTP off.

Version-Release number of selected component (if applicable):
systemd-219-24.fc22.x86_64

How reproducible:
Always

Steps to Reproduce:
1. systemctl disable timedatex
2. systemctl stop timedatex
3. timedatectl set-ntp on
4. Wait until you see "NTP synchronized: yes"
5. timedatectl set-ntp off

Actual results:
timedatectl keeps showing "NTP synchronized: yes".

Expected results:
"NTP synchronized: no".

Additional info:

The same happens when breaking the timesyncd configuration, maybe like this

    # echo NTP=foo.bar.blargl >/etc/systemd/timesyncd.conf.d/50-broken.conf
    # systemctl restart systemd-timesyncd

The clock is not really synchronized anymore, but timedatectl pretends that it is.

Setting the time manually via 'timedatectl' or 'date' resets the state to "NTP synchronized: no".
Comment 1 Fedora End Of Life 2016-07-19 14:13:43 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.