Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionPatrick C. F. Ernzer
2021-03-28 17:28:19 UTC
Description of problem:
I just upgraded my Sat 6.7 to 6.8 and noticed that after the upgrade, RHEL 7 hosts that I provision now get `ntp` instead of `chrony`.
It seems that in the template named "Kickstart default" the line
```
use_ntp = host_param_true?('use-ntp') || (is_fedora && os_major < 16) || (rhel_compatible && os_major <= 7)
```
should read `< 7`, not `<= 7`, since in the RHEL 7 Admin guide ( https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-configuring_ntp_using_the_chrony_suite ) we recommend chrony for most use cases (quite rightly so IMNSHO).
Version-Release number of selected component (if applicable):
satellite-6.8.4-1.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. have a soe-ci setup[1] that tests that chrony is set up correctly[2]
2. do nightly CI runs against a Satellite 6.7
3. test for chrony passes at every CI run
4. Upgrade Satellite to 6.8
Actual results:
The kickstart file rendered from the template named "Kickstart default" now reads
```
[...]
%packages
yum
dhclient
ntp
-chrony
wget
@Core
redhat-lsb-core
%end
[...]
```
Obviously that is not what I want, I would have liked the template to render in a way that does NOT force chrony out and ntp in, just like 6.7 seems to have done.
Expected results:
Satellite 6.8's default provisioning template for kickstart installs continues rolling out the preferred chrony
Additional info:
[1] https://github.com/RedHatSatellite/soe-ci/
[2] the test in question is just a primitive bats test that
- checks for the presence of the RPM `chrony`
- does a `systemctl status chronyd` and expects a return code of 0
- does a `chronyc sources` and checks that the system under test is using at least 2 servers
I only caught this changed behaviour because that test is run each night.
Hello Patrick,
There is already a similar BZ [1]. I see that this BZ is more for enforcing Chrony to be default choice, but setting "use-ntp" host parameter to "false" would solve this issue. There is also a fix pending to be applied in the upstream. Can we close this BZ in favor of that one?
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1932369
Comment 2Patrick C. F. Ernzer
2021-05-10 11:52:28 UTC
(In reply to Oleh Fedorenko from comment #1)
> Can we close this BZ in favor of that one?
Yes!
*** This bug has been marked as a duplicate of bug 1932369 ***
Description of problem: I just upgraded my Sat 6.7 to 6.8 and noticed that after the upgrade, RHEL 7 hosts that I provision now get `ntp` instead of `chrony`. It seems that in the template named "Kickstart default" the line ``` use_ntp = host_param_true?('use-ntp') || (is_fedora && os_major < 16) || (rhel_compatible && os_major <= 7) ``` should read `< 7`, not `<= 7`, since in the RHEL 7 Admin guide ( https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-configuring_ntp_using_the_chrony_suite ) we recommend chrony for most use cases (quite rightly so IMNSHO). Version-Release number of selected component (if applicable): satellite-6.8.4-1.el7sat.noarch How reproducible: always Steps to Reproduce: 1. have a soe-ci setup[1] that tests that chrony is set up correctly[2] 2. do nightly CI runs against a Satellite 6.7 3. test for chrony passes at every CI run 4. Upgrade Satellite to 6.8 Actual results: The kickstart file rendered from the template named "Kickstart default" now reads ``` [...] %packages yum dhclient ntp -chrony wget @Core redhat-lsb-core %end [...] ``` Obviously that is not what I want, I would have liked the template to render in a way that does NOT force chrony out and ntp in, just like 6.7 seems to have done. Expected results: Satellite 6.8's default provisioning template for kickstart installs continues rolling out the preferred chrony Additional info: [1] https://github.com/RedHatSatellite/soe-ci/ [2] the test in question is just a primitive bats test that - checks for the presence of the RPM `chrony` - does a `systemctl status chronyd` and expects a return code of 0 - does a `chronyc sources` and checks that the system under test is using at least 2 servers I only caught this changed behaviour because that test is run each night.