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.

Description of problem:

Currently, when creating a new Storagel Pool connection, there is no 
option to select `disk` type, only Filesystem Directory and Network File 
System are offered.

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

kernel-4.18.0-64.el8.x86_64
cockpit-system-184-1.el8.noarch

How reproducible:

100%

Steps to Reproduce:

From cockpit UI:

 Virtual Machines -> Storage Pools -> Create Storage Pool


Actual results:

There is no option offered to select disk storage pool type when creating 
a new one.

Expected results:

Support `disk` storage pool type when creating a new storage pool connection

Additional info:

It's been currently worked in this PR https://github.com/cockpit-project/cockpit/pull/11870

Test Versions:
cockpit-machines-196-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64


Test Steps:
1.Prepare a disk device(such as /dev/sdb)
2.Format the disk device by 'dd if=/dev/zero of=${device_name} bs=4k count=${num}', then part it by 'parted ${device_name} mktable ${partition}'
3.Create the Physical Disk storage pool through the page, then check it by 'virsh pool-list'


Test Results:
1. The storage pool can be created successfully


According to the results, move the 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:3325