RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1704853 - cockpit-machines missing dependency on virt-install
Summary: cockpit-machines missing dependency on virt-install
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.6
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: 7.8
Assignee: Katerina Koukiou
QA Contact: YunmingYang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-30 16:24 UTC by Lucas Caparelli
Modified: 2020-04-01 00:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-01 00:24:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1557039 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHBA-2020:1219 0 None None None 2020-04-01 00:24:38 UTC

Comment 2 Lucas Caparelli 2019-04-30 16:28:12 UTC
Description of problem:
 After installing "cockpit-machines" the "virt-install" component is not also installed. This results in an error when attempting to install a system.


Version-Release number of selected component (if applicable):
 cockpit-machines-176-4.el7.x86_64


How reproducible:
 Easily


Steps to Reproduce:
1. Install "cockpit-machines"
    # yum install cockpit-machines -y

2. Attempt to install a VM in the "Virtual Machines" UI
   Login -> "Virtual Machines" -> "Create VM" -> <Fill out information> -> "Create"

Actual results:
 --: line 82: virt-install: command not found

Expected results:
 Completed successfully, or noted that the package is necessary and prompt to confirm installation.

Additional info:
 Seen, and addressed, in RHEL 8 with the following bug report:

  1557039 – cockpit-machines missing dependency on virt-install
  https://bugzilla.redhat.com/show_bug.cgi?id=1557039

Comment 3 Martin Pitt 2019-05-02 05:59:07 UTC
In RHEL 8 this is done via "Recommends: virt-install". We can't do that in RHEL 7 as that doesn't have Recommends:. Adding it as a Requires would force this fairly heavy dependency onto everyone's system, which we prefer to avoid. cockpit-machines is useful for managing existing VMs without virt-install, so it's not absolutely required to have virt-install  all the time.

Comment 4 Kyle Walker 2019-05-02 12:41:46 UTC
@Martin,

That's a fair statement, but the error condition is surprising. To the average user, this would infer breakage in the utility as opposed to something that is per design and can be easily corrected. Is there any possibility that we could check if virt-install is installed in the "Create VM" menu? From there, we could either indicate that the package is necessary to proceed (with instructions how to install it), or we could prompt the user to see if they want to have cockpit install it for them. Similar to what is already done with the libvirt service status.

Comment 5 Martin Pitt 2019-05-02 15:36:03 UTC
We could look into installing it on demand, same as for pcp, tuned, firewalld and so on.

Comment 6 Katerina Koukiou 2019-07-02 07:28:46 UTC
Fixed upstream with:

commit 42958b53b7c2bbd1375ae28fc499a2c3e5abecbd (origin/master, origin/HEAD, master)
Author: Katerina Koukiou <kkoukiou>
Date:   Tue Jul 2 09:24:27 2019 +0200

    machines: Disable Create VM button if virt-install command is not available

$ git describe 42958b
197-37-g42958b53b

Comment 8 YunmingYang 2019-10-18 04:14:06 UTC
Test Versions:
cockpit-machines-195.4-2.el7.x86_64
libvirt-dbus-1.3.0-1.el7.x86_64


Test Steps:
1.Provision the host and install packages without virt-install
2.Login cockpit, then switch to 'Virtual Machines' page
3.install virt-install, then refresh the page


Test Results:
1.In step 2, the 'Create VM' button is gray and unclickable
2.In step 3, the 'Create VM' button is clickable


According to the results, move the status to VERIFIED.

Comment 10 errata-xmlrpc 2020-04-01 00:24:32 UTC
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-2020:1219


Note You need to log in before you can comment on or make changes to this bug.