http://bugzilla.suse.com/show_bug.cgi?id=1137196 http://bugzilla.suse.com/show_bug.cgi?id=1137196#c1 Thorsten Kukuk <kukuk@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Critical --- Comment #1 from Thorsten Kukuk <kukuk@suse.com> --- certficiates are created with wrong lifetime because of this. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137196 http://bugzilla.suse.com/show_bug.cgi?id=1137196#c2 Richard Brown <rbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown@suse.com --- Comment #2 from Richard Brown <rbrown@suse.com> --- (In reply to Thorsten Kukuk from comment #0)

We enable chronyd.service during installation of openSUSE kubic, but not chrony-wait.service.

Not sure if this is a YaST problem or a control.xml problem (see various comments in [bsc#1129730] for more details)

I could shove chrony-wait.service into the control.xml but given chrony.service seems to be enabled by the yast-caasp NTP module, then I think this is best left to the YaST Team Yastees, enable_service on https://github.com/yast/yast-caasp/blob/797b62b3993ea1841aedeccbc3862c27ff3a... needs to include chrony-wait as well as chronyd -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137196 http://bugzilla.suse.com/show_bug.cgi?id=1137196#c4 Stefan Schubert <schubi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |schubi@suse.com Resolution|--- |FIXED Assignee|yast-internal@suse.de |schubi@suse.com --- Comment #4 from Stefan Schubert <schubi@suse.com> --- chrony-wait service will be enabled: master: yast/yast-caasp: Pull Request 41 SR 709363 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137196 http://bugzilla.suse.com/show_bug.cgi?id=1137196#c6 --- Comment #6 from Thorsten Kukuk <kukuk@suse.com> --- (In reply to Jiri Srain from comment #5)

Do we have the same (or similar) problem also for general openSUSE / SLES?

Yes, the initial report about missing chrony-wait.service enablement was plain SLES. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137196 http://bugzilla.suse.com/show_bug.cgi?id=1137196#c8 --- Comment #8 from Jiri Srain <jsrain@suse.com> --- (In reply to Stefan Schubert from comment #7)

(In reply to Jiri Srain from comment #5)

...

Do we have the same (or similar) problem also for general openSUSE / SLES?

I do not know the Trello card has been for TW only.

My point was: You reference a PR for yast2-caasp - but I believe that we have the very same issue for openSUSE / SLES in general; if I enable NTP via yast ntp-client, both services should be enabled. IMO we need a fix for the NTP client YaST module. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1137196 http://bugzilla.suse.com/show_bug.cgi?id=1137196#c10 --- Comment #10 from Thorsten Kukuk <kukuk@suse.com> --- (In reply to Stefan Schubert from comment #9)

Ok thanks, I see. But if one service cannot work correctly without another wouldn't it be better to solve this on chrony level ? I must admit I am not a chrony expert :-)

Has nothing to do with chrony, but systemd. Don't ask my why, but it looks like nobody solved that on service level (ntp, systemd-timesyncd, ...), -- You are receiving this mail because: You are on the CC list for the bug.