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 1975677 - libiscsi is going to be removed from RHEL 9
Summary: libiscsi is going to be removed from RHEL 9
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libvirt
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Jiri Denemark
QA Contact: Meina Li
URL:
Whiteboard:
: 1986114 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-24 07:59 UTC by Miroslav Rezanina
Modified: 2021-12-07 22:01 UTC (History)
11 users (show)

Fixed In Version: libvirt-7.5.0-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-07 21:57:54 UTC
Type: Bug
Target Upstream Version: 7.5.0
Embargoed:

Attachments (Terms of Use)

Description Miroslav Rezanina 2021-06-24 07:59:58 UTC 
With BZ 1967133, qemu-kvm-block-iscsi package will be removed (as a first step to libiscsi removal). Libvirt has to be updated to handle this change.
Comment 1 Miroslav Rezanina 2021-06-24 08:07:06 UTC 
I wrongly understand dependency chain. libvirt is using libiscsi directly without dependency on qemu-kvm. However, libiscsi itself will be removed and we need to get rid of all dependencies requiring this package so libvirt has to remove iscsi storage driver.
Comment 2 Jiri Denemark 2021-06-24 09:02:03 UTC 
Patch sent upstream for review: https://listman.redhat.com/archives/libvir-list/2021-June/msg00721.html

BTW, iscsi storage driver access storage via block devices in /dev provided by
the iSCSI kernel driver. We need to disable iscsi-direct storage driver to
remove libiscsi dependency.
Comment 3 Jiri Denemark 2021-06-24 09:11:27 UTC 
Pushed upstream as

commit b3bbe5d8f58ccb81ab40ad2b6c3df5d1c0b70139
Refs: v7.4.0-248-gb3bbe5d8f5
Author:     Jiri Denemark <jdenemar>
AuthorDate: Thu Jun 24 10:18:17 2021 +0200
Commit:     Jiri Denemark <jdenemar>
CommitDate: Thu Jun 24 11:08:54 2021 +0200

    spec: Drop libiscsi support in RHEL-9

    https://bugzilla.redhat.com/show_bug.cgi?id=1975677

    Signed-off-by: Jiri Denemark <jdenemar>
    Reviewed-by: Ján Tomko <jtomko>
Comment 5 Han Han 2021-06-25 08:57:02 UTC 
Pre-verfiy it since libiscsi is disbaled in spec file.
Comment 6 Han Han 2021-06-28 07:17:32 UTC 
Meili, this update will only disable iscsi-direct storage pools.
Assign it to you.
Comment 10 Meina Li 2021-07-21 03:54:45 UTC 
Hi,Jiri :
Can we have a clearer error message like "not support iscsi-direct" when defining an iscsi-direct pool?
I think the current error message "internal error: missing backend for pool type 6 (iscsi-direct)" may confuse us sometimes. Thanks.

Test Version:
libvirt-7.5.0-1.el9.x86_64
qemu-kvm-6.0.0-9.el9.x86_64

Test Steps:
1. Check the current packages which are related with iscsi.
# rpm -qa | grep iscsi
libiscsi-1.19.0-4.el9.x86_64
iscsi-initiator-utils-iscsiuio-6.2.1.2-7.gita8fcb37.el9.x86_64
iscsi-initiator-utils-6.2.1.2-7.gita8fcb37.el9.x86_64
libvirt-daemon-driver-storage-iscsi-7.5.0-1.el9.x86_64
libvirt-daemon-driver-storage-iscsi-debuginfo-7.5.0-1.el9.x86_64
---Don't include qemu-kvm-block-iscsi and iscsi-direct related packages
2. Define an iscsi-direct pool
# virsh pool-define iscsi-direct.pool 
error: Failed to define pool from iscsi-direct.pool
error: internal error: missing backend for pool type 6 (iscsi-direct)
Comment 11 Peter Krempa 2021-07-21 06:59:10 UTC 
(In reply to Meina Li from comment #10)
> Hi,Jiri :
> Can we have a clearer error message like "not support iscsi-direct" when
> defining an iscsi-direct pool?

No as this would require downstream only patches. From the upstream point of view ...

> I think the current error message "internal error: missing backend for pool
> type 6 (iscsi-direct)" may confuse us sometimes. Thanks.

... this error message is okay, since it indicates that the backend for 'iscsi-direct' is not compiled or installed and there's no upstream notion of iscsi-direct being "unsupported.
Comment 12 Jiri Denemark 2021-07-21 07:42:58 UTC 
I don't think the message is confusing. It clearly says the support for
iscsi-direct is missing. It doesn't say why it is missing (not installed vs.
disabled during build), but that would mean changing the error message
depending on how various parts of libvirt are enabled or disabled in the spec
or even shipped in case some subpackage is only shipped with a specific
product.
Comment 13 Meina Li 2021-07-22 01:08:03 UTC 
According to comment 10 and comment 12, move this bug to be verified.
Comment 14 Peter Krempa 2021-07-26 18:23:05 UTC 
*** Bug 1986114 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.