Bug 1729222
| Summary: | VDSM should depend on fence-agents-all which doesn't require telnet package | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Javier Coscia <jcoscia> |
| Component: | vdsm | Assignee: | Eli Mesika <emesika> |
| Status: | CLOSED ERRATA | QA Contact: | Pavol Brilla <pbrilla> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.3.4 | CC: | abagga, abpatil, cww, ggasparb, jortialc, lleistne, lsurette, lsvaty, mhaicman, mkalinin, mperina, mtessun, openscap-maint, pelauter, ralford, sirao, srevivo, stirabos, usurse, vpolasek, wsato, ycui |
| Target Milestone: | ovirt-4.4.3 | Keywords: | Reopened, TestOnly |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | vdsm-4.40.35 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-24 13:11:27 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1883420 | ||
| Bug Blocks: | 1835650 | ||
|
Description
Javier Coscia
2019-07-11 15:52:21 UTC
Martin, do you think we can really remove the dependency? (In reply to Simone Tiraboschi from comment #4) > Martin, do you think we can really remove the dependency? It's not that easy, right now we depend on fence-agents-all so we know that each up-to-date host always has all required and updated fence agents. Currently in RHV 4.3 we support following fence agents: apc apc_snmp bladecenter cisco_ucs drac5 drac7 eps hpblade ilo ilo2 ilo3 ilo4 ilo_ssh ipmilan kdump rsa rsb wti So to maintain current functionality we would need to depend on 14 packages instead of 1: fence-agents-apc fence-agents-apc-snmp fence-agents-bladecenter fence-agents-cisco-ucs fence-agents-drac5 fence-agents-eps fence-agents-hpblade fence-agents-ilo fence-agents-ilo-ssh fence-agents-ipmilan fence-agents-rsa fence-agents-rsb fence-agents-wti That's not such a big problem until we will add new supported agent (which will happen in 4.4, when we introduce support for redfish): because we can't be sure that all hosts in cluster/datacenter are updated into latest version, so new supported agent is installed, fencing operation might not be successful, so host will stay non-responsive. But even with above change we will not get rid of telnet, because apc fence agent depends on it, so we would need to remove support for APC fence agent, which doesn't seem to me as a good idea. Martin, what do you think? Moving to virt, not really a node team issue. this will affect plain RHEL deployments as well when removing telnet after host is deployed. Moving to Infra to track fencing We need to add requirement for fence-agents-4.2.1-53.el8_3.1 into VDSM # yum list vdsm Updating Subscription Management repositories. Last metadata expiration check: 0:40:19 ago on Mon 02 Nov 2020 12:16:35 PM CET. Installed Packages vdsm.x86_64 4.40.26.3-1.el8ev @rhv-4-mgmt-agent-for-rhel-8-x86_64-rpms Available Packages vdsm.ppc64le 4.40.35.1-1.el8ev rhv-4.4.3 vdsm.x86_64 4.40.35.1-1.el8ev rhv-4.4.3 [root@demo-rhv-host ~]# yum list telnet Updating Subscription Management repositories. Last metadata expiration check: 0:40:36 ago on Mon 02 Nov 2020 12:16:35 PM CET. Available Packages telnet.x86_64 1:0.17-73.el8_1.1 rhel-8-for-x86_64-appstream-rpms telnet.x86_64 1:0.17-73.el8_1.1 rhel-8.2.0-appstream-rpms was able to removed telnet from server and vdsm with fence agent stayed on server Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (RHV RHEL Host (ovirt-host) 4.4.z [ovirt-4.4.3]), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:5213 |