| Summary: | Live ISOs offer NTP at boot but use both chronyd and systemd-timesyncd regardless | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | claire robinson <eeeemail> |
| Component: | RPM Packages | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | release_blocker | CC: | anaselli, doktor5000, isobuild, mageia, marja11, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| See Also: |
https://bugs.mageia.org/show_bug.cgi?id=15534 https://bugs.mageia.org/show_bug.cgi?id=17091 |
||
| Whiteboard: | MGA5TOO | ||
| Source RPM: | systemd | CVE: | |
| Status comment: | Also see Bug 17091 | ||
| Attachments: |
live.txt
installed.txt |
||
|
Description
claire robinson
2015-01-12 15:09:05 CET
Created attachment 5807 [details]
live.txt
Created attachment 5808 [details]
installed.txt
Claire i cannot understand which is the side effect in having both. Looking at installed.txt seems that both are trying to sync clock chronyd from 178.63.64.14 and 85.21.78.91 and systemd-timesyncd from 216.239.32.15:123 (time1.google.com). But I see that setting NTP in drackclock could at least disable systemd-timesyncd, since it does not manage it CC:
(none) =>
anaselli When neither is selected during installation, neither should be sync'ing the clock though really. I'm not sure the effect of having multiple services installed, they could conceivably end up fighting each other. I think we missed to change the chronyd.service with Conflicts=ntpd.service systemd-timesyncd.service and to add a similar line to ntpd.service Conflicts=chronyd.service systemd-timesyncd.service That should stop systemd-timesyncd.service i believe
Samuel Verschelde
2015-05-31 23:31:45 CEST
Whiteboard:
(none) =>
MGA5TOO FOR_ERRATA i think this is related to bug #15534
Samuel Verschelde
2015-06-02 09:46:20 CEST
See Also:
(none) =>
https://bugs.mageia.org/show_bug.cgi?id=15534
Marja Van Waes
2016-08-01 12:42:05 CEST
See Also:
(none) =>
https://bugs.mageia.org/show_bug.cgi?id=17091 We should find some solution for this before releasing Mageia 6. Priority:
Normal =>
release_blocker
David Walser
2016-08-09 23:39:13 CEST
Blocks:
(none) =>
15527 Why is this only a problem on the Live isos? CC:
(none) =>
marja11
Samuel Verschelde
2016-09-12 16:16:45 CEST
Status comment:
(none) =>
Also see Bug 17091 If nothing changed in drakxclock i don't think it's only a matter of Live. The problem is that systemd-timesyncd is installed and starts by default, if drakxclock does not manage it, it should at least disable it regardless if it installed or not e.g without care of command output. manaclock manages systemd-timesyncd but the code is pretty changed since it uses dbus. Assigning to Mageia tools maintainers as it seems to affect more than just live ISOs, as per comment 10. Also, the release blocker status of this bug might have to be reassessed based on our current priorities. Assignee:
isobuild =>
mageiatools
Samuel Verschelde
2016-10-18 13:09:53 CEST
Whiteboard:
MGA5TOO FOR_ERRATA =>
MGA5TOO AFAIC, it should be disabled by default in systemd... Source RPM:
drakxtools =>
systemd Done in systemd-230-7 Resolution:
(none) =>
FIXED Build failed Status:
RESOLVED =>
REOPENED Thierry pushed systemd-230-8 which fixed the build, so this one should be fixed. Status:
REOPENED =>
RESOLVED
Samuel Verschelde
2017-01-17 10:29:39 CET
Blocks:
15527 =>
(none) |