https://bugzilla.suse.com/show_bug.cgi?id=1188980 https://bugzilla.suse.com/show_bug.cgi?id=1188980#c2 Knut Alejandro Anderssen Gonz�lez changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kanderssen@suse.com --- Comment #2 from Knut Alejandro Anderssen Gonz�lez --- Yep, looks like related to https://bugzilla.suse.com/show_bug.cgi?id=1180699 and already tracked by https://trello.com/c/HtBLfvR0/4499-3-ostumbleweed-p5-1180699-microos-default... which is in the incoming board. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1188980 https://bugzilla.suse.com/show_bug.cgi?id=1188980#c4 Knut Alejandro Anderssen Gonz�lez changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #4 from Knut Alejandro Anderssen Gonz�lez --- With yast2-network-4.4.23 it will configure only one pool from the default list of sources (https://github.com/yast/yast-country/pull/282). But that means there will be at least two pools, the YaST one configured in /etc/chrony.conf and the other one provided by the chrony-pool-openSUSE RPM. The current YaST dialog models ignores anything under /etc/chrony.d so, it does not about the pools configured there and thus, them are not exposed in order to sync the time with the dialog. So, this looks like an enhancement for changing the current behavior, I will create a separate PBI in order to address it. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1188980 https://bugzilla.suse.com/show_bug.cgi?id=1188980#c5 --- Comment #5 from Knut Alejandro Anderssen Gonz�lez --- I have created a separate PBI in order to address this issue as it needs some discussions / agreements. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1188980 https://bugzilla.suse.com/show_bug.cgi?id=1188980#c6 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com, | |max@suse.com Flags| |needinfo?(max@suse.com) --- Comment #6 from Josef Reidinger --- Reinhard: We discussed this within a team and basically we have ideas how to fix it, but also we would like to verify it with you as you introduce that branding pools packages. So installation use-cases: 1. user wants distro defaults. In such case I think it makes sense to ensure that branding pool is installed ( so force install of chrony-pool-nonempty ) and ensure that chrony service is enabled and do nothing beside that. 2. user wants his own ntp server to be used. In such case we should force chrony-pool-empty and write to /etc/chrony.d/pool.conf server user wants to use. 3. user do not want ntp sync - in such case do not install chrony. And second case is modifications on running system. Reading is easy case as we can read all entries and read pool from it, but big topic is how to handle changes. What do you recommend to do? Remove pool keys from all configs and just use pool.conf? or disable touching of pools outside of pool.conf? And what about old chrony config in chrony.conf when user migrate? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1188980 Knut Alejandro Anderssen Gonz�lez changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kanderssen@suse.com |mfilka@suse.com -- You are receiving this mail because: You are on the CC list for the bug.