Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrony NTP servers configuration is out-of-date when compared to Leap 15-3 JeOS #54

Closed
FroggyFlox opened this issue May 30, 2021 · 1 comment · Fixed by #121
Closed
Assignees

Comments

@FroggyFlox
Copy link
Member

FroggyFlox commented May 30, 2021

This is another follow-up to #49.
Currently, we define the NTP servers for chrony to use while building the installer as follows:

#=====================================
# Enable chrony if installed
#-------------------------------------
if [ -f /etc/chrony.conf ]; then
# chronyc sits at 100% CPU even if chronyd service is disable
# Looks like: https://github.com/balena-os/meta-balena/issues/1360
# This should help once sorted; for now not installing chronyd (shame)
# suseInsertService chronyd
for i in 0 1 2 3; do
echo "server $i.opensuse.pool.ntp.org iburst"
done > /etc/chrony.d/opensuse.conf
fi

However, Leap 15-3 JeOS now uses a much more streamlined setup using SUSE NTP pool:

#=====================================
# Enable chrony if installed
#-------------------------------------
if [ -f /etc/chrony.conf ]; then
	suseInsertService chronyd
fi

This results in:

# ls -lah /etc/chrony.d/pool.conf
-rw-r--r-- 1 root root 32 May 27  2020 /etc/chrony.d/pool.conf

... defining the SUSE pool:

# cat /etc/chrony.d/pool.conf
pool 2.suse.pool.ntp.org iburst

Interestingly, this file is provided by:

# zypper se --provides /etc/chrony.d/pool.conf
Loading repository data...
Warning: Repository 'Update Repository (Non-Oss)' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...

S | Name                 | Summary                                | Type
--+----------------------+----------------------------------------+--------
  | chrony-pool-empty    | Empty pool preconfiguration for chrony | package
  | chrony-pool-openSUSE | Chrony preconfiguration for openSUSE   | package
i | chrony-pool-suse     | Chrony preconfiguration for SUSE       | package

... which itself was installed as part of chrony, I believe:

# zypper info chrony-pool-suse
Loading repository data...
Warning: Repository 'Update Repository (Non-Oss)' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...


Information for package chrony-pool-suse:
-----------------------------------------
Repository     : Main Repository
Name           : chrony-pool-suse
Version        : 3.2-9.21.1
Arch           : noarch
Vendor         : SUSE LLC <https://www.suse.com/>
Installed Size : 32 B
Installed      : Yes (automatically)
Status         : up-to-date
Source package : chrony-3.2-9.21.1.src
Summary        : Chrony preconfiguration for SUSE
Description    : 
    This package configures chrony to use the SUSE NTP server pool by
    default.

It's interesting to see it pulls down chrony-pool-suse and not chrony-pool-opensuse... another way Leap and SLE are getting closer?

@phillxnet phillxnet self-assigned this Jul 31, 2022
@phillxnet
Copy link
Member

phillxnet commented Jul 31, 2022

It's interesting to see it pulls down chrony-pool-suse and not chrony-pool-opensuse... another way Leap and SLE are getting closer?

Just done a quick check and recent builds do actually install the opensuse variant but it also looks like they are now identical as they share exact info. Likely one is now a link to the other.

localhost:~ # zypper info chrony-pool-suse
Loading repository data...
Warning: Repository 'Leap_15_3_Updates' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...


Information for package chrony-pool-suse:
-----------------------------------------
Repository     : Update repository with updates from SUSE Linux Enterprise 15
Name           : chrony-pool-suse
Version        : 4.1-150300.16.9.1
Arch           : noarch
Vendor         : SUSE LLC <https://www.suse.com/>
Installed Size : 32 B
Installed      : No
Status         : not installed
Source package : chrony-4.1-150300.16.9.1.src
Upstream URL   : https://chrony.tuxfamily.org/
Summary        : Chrony preconfiguration for SUSE
Description    : 
    This package configures chrony to use the SUSE NTP server pool by
    default.

localhost:~ # zypper info chrony-pool-opensuse
Loading repository data...
Warning: Repository 'Leap_15_3_Updates' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...


Information for package chrony-pool-openSUSE:
---------------------------------------------
Repository     : Update repository with updates from SUSE Linux Enterprise 15
Name           : chrony-pool-openSUSE
Version        : 4.1-150300.16.9.1
Arch           : noarch
Vendor         : SUSE LLC <https://www.suse.com/>
Installed Size : 36 B
Installed      : Yes (automatically)
Status         : up-to-date
Source package : chrony-4.1-150300.16.9.1.src
Upstream URL   : https://chrony.tuxfamily.org/
Summary        : Chrony preconfiguration for openSUSE
Description    : 
    This package configures chrony to use the openSUSE NTP server pool by
    default.

I'll check again to see if this changes over when we use the kiwi-ng build-in for activating this service.

localhost:~ # rpm -ql chrony-pool-openSUSE
/etc/chrony.d/pool.conf

phillxnet added a commit to phillxnet/rockstor-installer that referenced this issue Jul 31, 2022
Update our chronyd config via Kiwi-ng build-in.
This brings us closer to our JeOS Leap 15.3 Appliance
upstream. Dropping our prior my-hand additional server
configs.
phillxnet added a commit that referenced this issue Jul 31, 2022
…ation_is_out-of-date_when_compared_to_Leap_15-3_JeOS

revert to 'suseInsertService chronyd' #54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants