Description of problem: include a libvirt-admin package by default, it would provide virt-admin command Version-Release number of selected component (if applicable): RHV 4.x How reproducible: n/a Steps to Reproduce: na/a Actual results: not present Expected results: it is included by default Additional info: More details and why it is needed in following KCS article: https://access.redhat.com/solutions/53568
QE will check whether RHVH include libvirt-admin package by default.
*** Bug 1625461 has been marked as a duplicate of this bug. ***
Hi Olimp, as we want to keep the footprint of the RHV-H Image as small as possible, I would like to know, why virt-admin is needed here. So is there a business or technical justification that the customer can't do the following instead: - edit libvirt.conf directly if needed Reason: libvirt.conf debug levels should only be adjusted by advice from CE&E anyways. If the instruction is changing the libvirt.conf and restarting libvirt is fine, there is no reason for adding any further stuff to the RHV-H image. Thanks! Martin
(In reply to Martin Tessun from comment #3) > Hi Olimp, > > as we want to keep the footprint of the RHV-H Image as small as possible, I > would like to know, why virt-admin is needed here. > > So is there a business or technical justification that the customer can't do > the following instead: > > - edit libvirt.conf directly if needed > > Reason: libvirt.conf debug levels should only be adjusted by advice from > CE&E anyways. If the instruction is changing the libvirt.conf and restarting > libvirt is fine, there is no reason for adding any further stuff to the > RHV-H image. > > Thanks! > Martin The log level changed by the configuration file can only be enabled by restarting the libvirtd service. The restart prevents support from collecting the right data as the state of the libvirt daemon changes and the issue may not appear any more. In some cases, the issue can be reproduced, but reproducing issues on libvirt daemon can be harmful to the system and can take a considerable amount of time. The virt-admin tool allows us to adjust us the log level on the fly. This is a significant advantage for support and consequently for the users. I believe that this package is must in the image.
Thanks Roman, makes sense to me. Approving from supportability and debug perspective.
Nir, please sync with Aviv on this as well, should be similar to bz 1580322
Hi Jarda, do we have any possibility setting libvirt loglevel without using virt-admin and without restarting libvirt?
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag.
(In reply to Martin Tessun from comment #7) > Hi Jarda, > > do we have any possibility setting libvirt loglevel without using virt-admin > and without restarting libvirt? Nope. virt-admin API is the solution you need for that.
Test Version RHVH-4.3-20190201.0-RHVH-x86_64-dvd1.iso cockpit-system-176-4.el7.noarch cockpit-ws-176-4.el7.x86_64 cockpit-bridge-176-4.el7.x86_64 cockpit-storaged-176-4.el7.noarch cockpit-ovirt-dashboard-0.12.1-1.el7ev.noarch cockpit-machines-ovirt-176-4.el7.noarch cockpit-176-4.el7.x86_64 cockpit-dashboard-176-4.el7.x86_64 ovirt-hosted-engine-setup-2.3.3-1.el7ev.noarch ovirt-hosted-engine-ha-2.3.1-1.el7ev.noarch Test Steps: 1. Clean install RHVH-4.3-20190201.0-RHVH-x86_64-dvd1.iso 2. Subscribe to stage CDN 3. Enable rhel-7-server-rhvh-4* repos 4. yum search virt-admin Result: "No matches found" virt-admin package not in RHVH optional channel. Moreinfo: RHVH doesn't include libvirt-admin package by default. Change ON_QA to "ASSIGNED"
Moving to 4.3.2 not being identified as blocker for 4.3.1
Tested on RHVH-4.3-20190226.0-RHVH-x86_64-dvd1.iso Verified. hannel:https://cdn.stage.redhat.com/content/dist/rhel/server/7/7Server/$basearch/rhvh/4/os
Test Version rhvh-4.3.0.5-0.20190225.0+1 subscription-manager-1.21.10-3.el7_6.x86_64 Test Steps: According to comment 13 Result: Libvirt-admin package exists in RHVH optional channel. Bug is fixed, change 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/RHBA-2019:1053
Re-opening this because I can't see any rhvh repo which has libvirt-admin package. Could you please let us know which repo should be having this package? I can't see it in any of the "rhel-7-server-rhvh-4*" repos.
Test Version: rhvh-4.3.6.5-0.20191108.0 Test Steps: 1. Install rhvh-4.3.6.5-0.20191108.0 2. #rpm -qa|grep virt-admin 3. run command #virt-admin Test Result: 1.the package info displayed as below: libvirt-admin-4.5.0-23.el7_7.1.x86_64 2.and command 'virt-admin' is avaliable to use. libvirt-admin had been included in the image of rhvh-4.3.6.5-0.20191108.0 May I ask in which version of rhvh you want to test? Because I used the latest version and the libvirt-admin package was pre-installed.
Sorry, I was checking the older version and was checking if the repo has it. I can confirm that the latest version has virt-admin. Closing it again. Sorry for confusion.