Bug 1450152
| Summary: | gdeploy conf file for hc should be changed to start chronyd instead of ntpd | ||
|---|---|---|---|
| Product: | [oVirt] cockpit-ovirt | Reporter: | RamaKasturi <knarra> |
| Component: | Gdeploy | Assignee: | Devyani Kota <dkota> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | RamaKasturi <knarra> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | --- | CC: | bugs, dkota, j.tiemann, knarra, rbarry, rhs-bugs, robnunin, sabose, sasundar, smohan, stirabos, storage-qa-internal |
| Target Milestone: | ovirt-4.1.3 | Keywords: | Rebase |
| Target Release: | 0.10.7-0.0.18 | Flags: | rule-engine:
ovirt-4.1?
sabose: planning_ack? sabose: devel_ack+ knarra: testing_ack+ |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | cockpit-ovirt-0.10.7-0.0.19.el7ev | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-06 14:05:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1277939, 1485854 | ||
|
Description
RamaKasturi
2017-05-11 16:48:01 UTC
Devyani,
chronyd is enabled and already up with RHVH.
[root@cambridge ~]# systemctl is-enabled chronyd
enabled
[root@cambridge ~]# systemctl status chronyd
● chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2017-05-22 09:57:05 IST; 11h ago
Main PID: 1101 (chronyd)
CGroup: /system.slice/chronyd.service
└─1101 /usr/sbin/chronyd
So restarting the chronyd and enabling it across reboots is not required with RHVH. Can we conditionally enable and start chronyd only with RHEL 7 ?
(In reply to SATHEESARAN from comment #2) > Devyani, > > chronyd is enabled and already up with RHVH. > [root@cambridge ~]# systemctl is-enabled chronyd > enabled > [root@cambridge ~]# systemctl status chronyd > ● chronyd.service - NTP client/server > Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor > preset: disabled) > Active: active (running) since Mon 2017-05-22 09:57:05 IST; 11h ago > Main PID: 1101 (chronyd) > CGroup: /system.slice/chronyd.service > └─1101 /usr/sbin/chronyd > > So restarting the chronyd and enabling it across reboots is not required > with RHVH. Can we conditionally enable and start chronyd only with RHEL 7 ? Hi sas, I have installed latest RHV-H ISO and i see that chronyd is disabled and it is not up with RHV-H [root@rhsqa-grafton4 ~]# systemctl is-enabled chronyd disabled [root@rhsqa-grafton4 ~]# systemctl status chronyd ● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service; disabled; vendor preset: disabled) Active: inactive (dead) (In reply to RamaKasturi from comment #3) > (In reply to SATHEESARAN from comment #2) > > Devyani, > > > > chronyd is enabled and already up with RHVH. > > [root@cambridge ~]# systemctl is-enabled chronyd > > enabled > > [root@cambridge ~]# systemctl status chronyd > > ● chronyd.service - NTP client/server > > Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; vendor > > preset: disabled) > > Active: active (running) since Mon 2017-05-22 09:57:05 IST; 11h ago > > Main PID: 1101 (chronyd) > > CGroup: /system.slice/chronyd.service > > └─1101 /usr/sbin/chronyd > > > > So restarting the chronyd and enabling it across reboots is not required > > with RHVH. Can we conditionally enable and start chronyd only with RHEL 7 ? > > Hi sas, > > I have installed latest RHV-H ISO and i see that chronyd is disabled and > it is not up with RHV-H > > [root@rhsqa-grafton4 ~]# systemctl is-enabled chronyd > disabled > [root@rhsqa-grafton4 ~]# systemctl status chronyd > ● chronyd.service - NTP client/server > Loaded: loaded (/usr/lib/systemd/system/chronyd.service; disabled; vendor > preset: disabled) > Active: inactive (dead) This is the strange behaviour that we noticed with our setups. Kasturi and I have installed from the same ISO, but I see that chronyd is enabled and running while Kasturi's setup has chronyd disabled. I have installed RHVH with Virtual Machine, and I also see that chronyd is running. /root/anaconda-ks.cfg also shows that the chronyd is enabled during installation. <snip> # System services services --enabled="chronyd" </snip> Kasturi, could you also try installation with VM and update the result ? sas, i did installation with VM and i still see that chronyd is still disabled and not started. As discussed, can you check if there are any steps you are doing differently because of which it is enabled for you by default ? (In reply to RamaKasturi from comment #5) > sas, i did installation with VM and i still see that chronyd is still > disabled and not started. As discussed, can you check if there are any steps > you are doing differently because of which it is enabled for you by default ? The reason for the occurrence of this issue has been found. Short summary : When 'Network Time' is disabled in the anaconda screen, chronyd is disabled. Testing: 1. When first configuring the 'Network' and then setting up 'Date & Time' in the anaconda screen, has 'Network Time' enabled, which lead to chronyd enabled. 2. If 'Date & Time' is set first, then 'Network Time' is disabled,( as network itself is not yet configured ), which leads to the chronyd getting disabled. I was doing the former test and I had chronyd enabled, while kasturi was doing the latter and had chronyd enabled. Solution to this bug - Let's have chronyd enabled and started (In reply to SATHEESARAN from comment #6) > (In reply to RamaKasturi from comment #5) > > sas, i did installation with VM and i still see that chronyd is still > > disabled and not started. As discussed, can you check if there are any steps > > you are doing differently because of which it is enabled for you by default ? > > The reason for the occurrence of this issue has been found. > Short summary : When 'Network Time' is disabled in the anaconda screen, > chronyd is disabled. > > Testing: > 1. When first configuring the 'Network' and then setting up 'Date & Time' in > the anaconda screen, has 'Network Time' enabled, which lead to chronyd > enabled. > > 2. If 'Date & Time' is set first, then 'Network Time' is disabled,( as > network itself is not yet configured ), which leads to the chronyd getting > disabled. > > I was doing the former test and I had chronyd enabled, while kasturi was > doing the latter and had chronyd enabled. > > Solution to this bug - Let's have chronyd enabled and started Irrespective of the RHEL or RHVH platform Using latest ovirt-node-ng iso (http://resources.ovirt.org/pub/ovirt-4.1/iso/ovirt-node-ng-installer/ovirt-node-ng-installer-ovirt-4.1-2017052309.iso) to install oVirt node, gdeploy is still checking for ntpd instead of chronyd. ntp rpm isn't installed using the ovirt-node-ng iso above mentioned, standards repo from installation don't provide it, so manual intervention is needed to workaround this race condition. Verified and works fine with build cockpit-ovirt-dashboard-0.10.7-0.0.20.el7ev.noarch. I see that there are steps to enable and restart chronyd in the generated gdeploy conf file. lines from generated gdeploy config file: ========================================== [service1] action=enable service=chronyd [service2] action=restart service=chronyd *** Bug 1464079 has been marked as a duplicate of this bug. *** |