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 1709708 - [machines] The problems of 'iscsi storage pool' and 'iscsi direct storage pool' in rhel8.1
Summary: [machines] The problems of 'iscsi storage pool' and 'iscsi direct storage poo...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: cockpit-appstream
Version: 8.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 8.1
Assignee: Katerina Koukiou
QA Contact: YunmingYang
URL:
Whiteboard:
Depends On: 1710575
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-14 07:48 UTC by YunmingYang
Modified: 2020-11-14 09:40 UTC (History)
4 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:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:3325 0 None None None 2019-11-05 20:42:06 UTC

Description YunmingYang 2019-05-14 07:48:23 UTC 
Description of problem:
1. There is no libvirt-daemon-driver-storage-iscsi-direct in the default repo, so the creation of 'iscsi direct storage pools' will cause a error which is ''Error message: unsupported configuration: unknown storage pool type iscsi-direct'.
2. The 'iscsi storage pool' will create successfully, but show no size on the UI.The command can not get the size of it, either. 

Version-Release number of selected component (if applicable):
cockpit-machines-193-1.el8.noarch
cockpit-ws-193-1.el8.x86_64
cockpit-193-1.el8.x86_64
cockpit-system-193-1.el8.noarch
cockpit-storaged-193-1.el8.noarch
cockpit-bridge-193-1.el8.x86_64
cockpit-packagekit-193-1.el8.noarch
libvirt-dbus-1.2.0-2.module+el8+2704+d2eddeb5.x86_64
qemu-kvm-2.12.0-63.module+el8+2833+c7d6d092.x86_64
kernel-4.18.0-83.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare an iscsi target, and a RHEL8.1 host
2. Install the dependencies with the command 'yum module install -y virt && yum install -y cockpit-machines && systemctl enable --now cockpit.socket'
3. Login the cockpit page of the RHEL8.1 host
4. Create the 'iscsi storage pool' with the iscsi target, and use the command 'virsh pool-info ${pool-name}' to make sure the result.
5. Create the 'iscsi direct storage pool' with the iscsi target.

Actual results:
1. The creation of the 'iscsi storage pool' will take a few time, after that, there is no size for the pool shown on the page, the command can not get the size, either.
2. The creation of the 'iscsi direct storage pool' will fail with a error which is 'Error message: unsupported configuration: unknown storage pool type iscsi-direct'

Expected results:
1. The 'iscsi storage pool' and the 'iscsi direct storage pool' can be created correctly.

Additional info:
Comment 1 Katerina Koukiou 2019-05-15 19:47:25 UTC 
For the first issue https://bugzilla.redhat.com/show_bug.cgi?id=1710575 was reported.
For the second I need to take action and hide the feature, since libvirt 4.7 is not going to be in 8.1.

For the future please report separate issues for different bugs so that we can track them easier.
Comment 2 YunmingYang 2019-05-16 01:57:50 UTC 
(In reply to Katerina Koukiou from comment #1)
> For the first issue https://bugzilla.redhat.com/show_bug.cgi?id=1710575 was
> reported.
> For the second I need to take action and hide the feature, since libvirt 4.7
> is not going to be in 8.1.
> 
> For the future please report separate issues for different bugs so that we
> can track them easier.

OK, i will pay attention later， many thanks
Comment 3 Katerina Koukiou 2019-05-28 12:54:03 UTC 
commit 6167bdc062828411e9ec98306ba9249037371327
Author: Katerina Koukiou <kkoukiou>
Date:   Thu May 16 23:22:55 2019 +0200

    machines: hide iscsi-direct type from create new pool dialog when not available

$ git describe 6167bdc062828411e9ec98306ba9249037371327
194-50-g6167bdc06
Comment 5 YunmingYang 2019-06-23 13:14:16 UTC 
For the first issue, https://bugzilla.redhat.com/show_bug.cgi?id=1710575 was still ASSIGNED.
For the second one, has been verified on rhel 8.1.
No change because of the status of the first issue, leave this bug for tracing.
Comment 6 YunmingYang 2019-08-07 07:20:36 UTC 
Test Versions:
cockpit-machines-197.1-1.el8.noarch
libvirt-dbus-1.2.0-3.module+el8.1.0+3531+2918145b.x86_64


Test Steps:
1. Open the storage pool creation dialog
2. check the type of the dialog
3. Create a iSCSI storage pool


Test Results:
1.After step 2, 'iSCSI direct Target' has been hid
2.After step 3, the iSCSI storage pool can be created successfully, and the information of the storage pool can be shown correctly


According to the results, move the status to VERIFIED.
Comment 8 errata-xmlrpc 2019-11-05 20:41:55 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.