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 1672753 - [RFE] [machines] Cannot create additional network device on cockpit
Summary: [RFE] [machines] Cannot create additional network device on cockpit
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 8.2
Assignee: Martin Pitt
QA Contact: YunmingYang
Lucie Vařáková
Depends On:
TreeView+ depends on / blocked
Reported: 2019-02-05 19:04 UTC by Javier Coscia
Modified: 2020-04-28 15:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
The Virtual Machines page now supports creation and removal of virtual network interfaces. Screenshot: https://cockpit-project.org/blog/cockpit-203.html
Clone Of:
Last Closed: 2020-04-28 15:42:36 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3907041 0 Configure None Cannot create additional network device on cockpit in RHEL 8.0 2019-02-13 04:24:20 UTC
Red Hat Product Errata RHBA-2020:1639 0 None None None 2020-04-28 15:42:53 UTC

Description Javier Coscia 2019-02-05 19:04:11 UTC
Description of problem:

After or while creating a VM through cockpit UI, user cannot create an 
additional vNIC 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Cockpit > Virtual Machines > Create VM

Actual results:

- There is no option to add another vNIC interface other than the `default` one

Expected results:

- User should be able to create additional vNIC interfaces while creating the 
VM or after creating it.

Comment 1 Simon Kobyda 2019-09-24 07:51:55 UTC

commit 6b92175157e06d00739916d417cf2311e54a92d5
Author: Simon Kobyda <skobyda>
Date:   Wed Sep 4 16:25:57 2019 +0200

    machines: Implement adding virtual network interfaces
    Closes #12711

Comment 3 Xianghua Chen 2019-12-09 08:21:55 UTC
Verified with packages:

1. Prepare a running VM and switch to the network tab of the VM  
2. Click 'Add Network Interface' 
3. Set the parameters below:     
Interface Type: Virtual network         
source: default     
model: virtio     
Mac Adddress: Generate automatically     
Then click the "Add" button
4. Shut down the VM,the network interface should be removed.
5. Reopen the VM, click the 'Add Network Interface', then set the parameters below:     
Interface Type: Virtual network         
source: default     
model: virtio     
Mac Adddress: Generate automatically     
Persistence: Always attach     
Then click the "Add" button
6. Shut down the VM,the network interface should not be removed.

So verified.

Comment 7 errata-xmlrpc 2020-04-28 15:42:36 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.


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