Bug 1725954
| Summary: | libvirt-admin package not available in RHVH | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Javier Coscia <jcoscia> |
| Component: | ovirt-host | Assignee: | Yuval Turgeman <yturgema> |
| Status: | CLOSED ERRATA | QA Contact: | cshao <cshao> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.3.5 | CC: | cshao, lsvaty, mavital, mtessun, nlevy, qiyuan, rdlugyhe, sbonazzo, weiwang, yaniwang, yturgema |
| Target Milestone: | ovirt-4.3.5 | Keywords: | Regression |
| Target Release: | 4.3.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-host-4.3.4-1.el7ev | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the libvirt-admin package was missing from the optional Red Hat Virtual Host (RHVH) repository, rhel-7-server-rhvh-4*. The current release adds libvirt-admin to the RHVH image instead of the optional repository.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-12 11:55:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1731884, 1738897 | ||
| Bug Blocks: | 1728283 | ||
|
Description
Javier Coscia
2019-07-01 20:06:53 UTC
It was removed for bz 1688835 - I'd rather add it to the image itself since it doesn't pull any other requirements. Is that acceptable ? Since libvirt-admin doesn't seem to require additional packages (deps), I do agree that adding the RPM into the image would be better decided to add the package in the image itself. Test version: redhat-virtualization-host-4.3.5-20190710.2.el7_7 ovirt-host-4.3.4-1.el7ev Test result: # rpm -qa| grep libvirt-admin libvirt-admin-4.5.0-23.el7.x86_64 So the bug is fixed, change bug status to VERIFIED. 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, 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/RHEA-2019:2451 |