Description of problem: The function of adjusting iscsi-initiator should be enabled in cockpit. Version-Release number of selected component (if applicable): rhev-hypervisor7-ng-4.0-20160622.1.x86_64 imgbased-0.7.0-0.1.el7ev.noarch cockpit-0.108-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. Install NGN 2. Config network and login cockpit website 3. Check in storage for adjusting the iscsi-initiator function. Actual results: It is no possibility to adjust the iscsi-initiator with cockpit. Expected results: It should be enabled for adjusting the iscsi-initiator with cockpit. Additional info:
Could you please specify the individual items which are missing?
Fabian, Firstly, we need an ISCSI patrol list Raid in the cockpit UI. Secondly, we need some basic functions(add, delete, modify, search) for ISCSI initiator adjusting. e.g: add ISCSI storage which can be selected from the ISCSI target list, rename ISCSI initiator, added ISCSI storage list displaying, delete the added storages. Thirdly, we should make the error status for incorrect input.
I believe we've gotten as far as making it work on RHEL without session (login) support. Marius would know more details.
This video shows the level of iSCSI support in Cockpit: https://www.youtube.com/watch?v=N1Lw2OVLDoo Is this enough? On RHEL, the functionality is reduced due to some missing API in libiscsi. Please see bug 1341006 for progress on that.
hi mvollmer, We think it is enough for the cockpit. From your video, we can see the main functions mentioned in comment 2 are basically covered. Thanks! BTW, we can find the iscsi component on cockpit storage page for the latest RHVH version redhat-virtualization-host-4.0-20160727.1.x86_64(cockpit version is cockpit-0.114-2.el7.x86_64), is it ready for QE?
(In reply to weiwang from comment #5) > We think it is enough for the cockpit. From your video, we can see the main > functions mentioned in comment 2 are basically covered. Thanks! Great! > BTW, we can find the iscsi component on cockpit storage page for the latest > RHVH version redhat-virtualization-host-4.0-20160727.1.x86_64(cockpit > version is cockpit-0.114-2.el7.x86_64), is it ready for QE? It is ready for QE, but note the dependency on bug 1341006.
MOving to QE per comment#6
The bug is needed to be verified with 4.1.0, so we will verify this bug until 4.1.0 build is got.
This bug is targeted to ovirt-4.1, the RHVH 4.1 build is not ready to QE. We won't verify this bug. and we have to move back to MODIFIED status.
Test with redhat-virtualization-host-4.1-20170112.1, the iscsi-initiator function isn't enabled. So move back to MODIFIED status.
Test with redhat-virtualization-host-4.1-20160120.0, iscsi-initiator function isn't enabled. So set back to ASSIGNED status.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Moving to 4.1.6 since the platform bug needed for this one has not been fixed yet.
Still waiting for platform...
After talking to the cockpit team, using cockpit-storaged is not sufficient, since some required fixes to libstorage_iscsi are missing from platform, and are unlikely to land in 7.4. Moving out
Platform bug still in NEW after RHEL 7.5 beta release, postponing while we get estimation on when the new iscsi-initiator package will be available.
(In reply to Sandro Bonazzola from comment #19) > Platform bug still in NEW after RHEL 7.5 beta release, postponing while we > get estimation on when the new iscsi-initiator package will be available. So let's postpone realistically.
Any update?
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag.
Moving to 4.3.2 not being identified as blocker for 4.3.1
(In reply to Yaniv Kaul from comment #20) > So let's postpone realistically. yes!:) Sandro, can you please check if fixed as a side effect of anything else? If not I suggest WONTFIX, we didn't get to it for 4 years...
(In reply to Michal Skrivanek from comment #24) > yes!:) Sandro, can you please check if fixed as a side effect of anything > else? If not I suggest WONTFIX, we didn't get to it for 4 years... Wei, can you please try to reproduce with RHV-H 4.4/EL8?
cockpit equivalent version is included in ovirt-node-ng-image-4.4.0_beta2, movint to QE for test-only.
Test Version: ovirt-node-ng-4.4.0-0.20200409.0 cockpit-211.1-2.el8.x86_64 cockpit-system-211.1-2.el8.noarch cockpit-bridge-211.1-2.el8.x86_64 cockpit-ws-211.1-2.el8.x86_64 cockpit-storaged-211.1-2.el8.noarch cockpit-ovirt-dashboard-0.14.4-1.el8.noarch cockpit-dashboard-211.1-2.el8.noarch Test step: 1. install ovirt-node-ng-4.4.0-0.20200409.0 2. login cockpit 3. enter the storage page 4. check if iscsi functionality is existing 5. modify ISCSI Initiator Name 6. add ISCSI target 7. delete ISCSI target Test result: For upstream version: ISCSI target can be added successfully, but iscsi target can not be deleted. We reported a new bug 1825723. As for downstream version: And there is still no iscsi functionality in latest rhvh (rhvh-4.4.0.18-0.20200417.0) This bug has not been totally fixed, move the status to ASSIGNED
Closing can't fix. We waited 5 years for platform to fix cockpit, not willing to keep waiting anymore. Can't fix this bug without commitment on platform side. Please feel free to reopen once the functionality will be available on cockpit side.