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 1680973 - [RFE] [machines] Provide network boot VM - PXE
Summary: [RFE] [machines] Provide network boot VM - PXE
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
high
medium
Target Milestone: rc
: 8.1
Assignee: Martin Pitt
QA Contact: YunmingYang
URL:
Whiteboard:
Depends On: 1678935
Blocks: 1701002
TreeView+ depends on / blocked
 
Reported: 2019-02-25 15:43 UTC by Javier Coscia
Modified: 2020-11-14 14:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 20:41:39 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3938101 0 Supportability None Can I boot through network (PXE) on Cockpit UI ? 2019-02-25 15:48:54 UTC
Red Hat Product Errata RHBA-2019:3325 0 None None None 2019-11-05 20:41:48 UTC

Description Javier Coscia 2019-02-25 15:43:29 UTC
Description of problem:

Currently, cockpit UI only allows users to select Filesystem (path to the 
image on host) or URL source methods.

We should add the option to allow PXE network boot

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

cockpit-machines-184.1-1.el8.noarch

How reproducible:

100%

Steps to Reproduce:
1. Start the creation of a new VM through cockpit.
2. Click the drop down `installation source type`
3. Only filesystem and url are displayed/


Actual results:

There's no option to allow users to boot through network (PXE) through 
cockpit UI

Expected results:

PXE source installation method should be allowed

Comment 1 Martin Pitt 2019-02-27 10:12:13 UTC
Katerina is working on this feature at the moment.

Comment 4 YunmingYang 2019-05-29 06:37:40 UTC
Test Versions:
cockpit-machines-193-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64


Test Steps:
1.Click the 'Create VM' button. 
2.Choose 'Network Boot(PXE)' for installation source type and choose an network card which can connect a PXE server on the host(eg:eno0) for installation source 


Test Results:
The VM can be created by 'Network Boot(PXE)'


According to the results, network boot for VM is provided.So move the status to VERIFIED.

Comment 6 errata-xmlrpc 2019-11-05 20:41:39 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-2019:3325


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