Bug 1466422
Summary: | Chronyd not installed nor enabled or started after upgrade | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Lukas Svaty <lsvaty> |
Component: | Setup.Engine | Assignee: | Sandro Bonazzola <sbonazzo> |
Status: | CLOSED NOTABUG | QA Contact: | Lukas Svaty <lsvaty> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.3.5 | CC: | bugs, lsvaty, mperina, sbonazzo |
Target Milestone: | ovirt-4.1.5 | Keywords: | Unconfirmed |
Target Release: | --- | Flags: | rule-engine:
ovirt-4.1+
lsvaty: testing_ack+ |
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 08:12:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lukas Svaty
2017-06-29 14:28:37 UTC
(In reply to Lukas Svaty from comment #0) > Description of problem: > After upgrading engine from previous version which does not have chornyd > installed on hosts/engine it is not installed and started on new instance. > This behaviour is the same for hosts and engine. Can you please detail what do you mean with "This behaviour is the same for hosts and engine." Because as far as I can tell, ovirt-engine never required ntpd as rpm dependency and never tried to configure it, so I don't expect to see appearing any dependency on chrony or configuration migration from ntpd to chronyd at engine upgrade stage. On the other hand, vdsm on 4.1 explicitly requires chrony as rpm dependency, so I expect to see it installed on hosts. So IIUC. We are not forcing ntp nor chorny on engine side- VERIFIED (no change after upgrade) As for chrony we are installing the package, however not setting it up, running service or enabling the service. Thus if before upgrade service was not running, we just install the package, right? What is the purpose of this package installed if we are not setting it up? I believe we had this conversation as part of BZ#1466422, however we only agreed on installing chrony not setting it up. Wanna revisit? (In reply to Lukas Svaty from comment #2) > So IIUC. > > We are not forcing ntp nor chorny on engine side- VERIFIED (no change after > upgrade) Correct, we didn't enforce ntpd and we are not enforcing chrony on engine side. > As for chrony we are installing the package, however not setting it up, > running service or enabling the service. > Thus if before upgrade service was not running, we just install the package, > right? This is on host side since on engine we doesn't require chrony as a dependency. Quoting mperina on this: by default after installation DHCP client inject its configuration into chronyd, so it should configured using DHCP. We definitely don't want to provide UI for manual NTP configuration, so here's status: 1. DHCP configured hosts - everything should work automatically (assuming DHCP server contains NTP configuration) 2. Statically configured hosts - admin needs to configure chrony manually > > What is the purpose of this package installed if we are not setting it up? As above, DHCP injects NTP config into chrony > > I believe we had this conversation as part of BZ#1466422, however we only > agreed on installing chrony not setting it up. Wanna revisit? As per comment #3 I'm closing as not a bug. |