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 1672755 - [machines][RFE] Cannot create or select VM network profile on cockpit UI
Summary: [machines][RFE] Cannot create or select VM network profile on cockpit UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: 8.2
Assignee: Simon Kobyda
QA Contact: YunmingYang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-05 19:18 UTC by Javier Coscia
Modified: 2020-04-28 15:42 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:42:36 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3907021 0 Troubleshoot None Not able to select network profile from cockpit GUI in RHEL 8 2019-02-13 04:18:25 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:18:53 UTC 
Description of problem:

A network profile cannot be created through cockpit UI, neither a profile 
can be selected while building a VM


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

cockpit-machines-184-1.el8.noarch

How reproducible: 100%


Steps to Reproduce:
1. Cockpit > Virtual Machines
2. There's no `Networks` link to access information about the profile like it is for `Storage Pools`  and to create a new profile
3. If profile is created through virsh, a page reload is needed to make it visible and only after that you can change the profile of an already created vNIC

Actual results:

No option to create a new network profile on cockpit
Cannot select VM network profile while creating a VM, even if the profile exist

Expected results:

User should be able to create additional Network profiles through cockpit and be able to select which profile to use when building the VM
Comment 1 Simon Kobyda 2019-02-20 12:55:25 UTC 
Pull request in progress, resolving this issue:

https://github.com/cockpit-project/cockpit/pull/11204
Comment 2 Simon Kobyda 2019-02-20 13:00:32 UTC 
(In reply to Simon Kobyda from comment #1)
> Pull request in progress, resolving this issue:
> 
> https://github.com/cockpit-project/cockpit/pull/11204

Sorry, not resolving, but *referencing this issue, since this pull request doesn't allow adding new networks yet, so it only partly resolves this issue (you can access information about network, but not change it)

However soon there will be pull request which will allow adding and editing networks.
Comment 3 Katerina Koukiou 2019-08-07 14:59:43 UTC 
commit d6cf545bb2e6d326f3d248593bcaa0da9e25c8d6
Author: Simon Kobyda <skobyda>
Date:   Tue Aug 6 17:35:53 2019 +0200

    machines: Implement creation of Virtual Networks

$ git describe d6cf545bb2e6d326f3d248593bcaa0da9e25c8d6
200-3-gd6cf545bb
Comment 4 Martin Pitt 2019-08-08 05:33:22 UTC 
Released in upstream version 200. New feature, moving to RHEL 8.2.
Comment 6 Xianghua Chen 2019-12-11 07:04:22 UTC 
Verified with packages:
cockpit-machines-208-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+4066+0f1aadab.x86_64

Steps:
1. Enter Networks page,click "Create Virtual Network"
2. Create Network with the parameter below  
Name: random string 
Forward Mode: NAT 
Device: Automatic 
IP Configuration: IPv4 only 
IPv4 Network: 192.168.100.0
Mask or Prefix Length: 24
Click "Create"
The new network can be created.
3. Check the new created network on host by:
# virsh net-list --all
The information is corresponding to the web console.
4. Click "Activate"
The network is active , and the network status on host is active too.
5. Click "Delete"
The network is deleted on the web console and on the host.

So verified.
Comment 9 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.

https://access.redhat.com/errata/RHBA-2020:1639
Note You need to log in before you can comment on or make changes to this bug.