Description of problem: There is a need to test and document a recommended way how to make an existing RHV environment to utilize iSCSI bond feature (using the same subnet). We have a quite spare (in the matter of scenarios) description of iSCSI Bond in the "Administration Gude" https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/sect-preparing_and_adding_block_storage#Configuring_iSCSI_Multipathing However, most customers start their settings from a simple setting and then they want to migrate to iSCSI bond. This doc BZ was created from https://bugzilla.redhat.com/show_bug.cgi?id=1565198 Before we publish the recommended way, we have to test using continuous IO. Version-Release number of selected component (if applicable): RHV 4.x How reproducible: Let's take into consideration the worst case, e.g customer has a bond (from 2 NICs), on top of it Logical Network (responsible for a storage connection). Now he wants to move it (without downtime) to iSCSI bond using the same subnet. I have tested such scenario, it is working properly: I broke the bond, prepared Logical Networks (not-required), attached to NICs, created iSCSI Bond, everything on a running hypervisor. It seems to be ok, but I afraid to give recommendations for production environments. Actual results: It is working properly Expected results: We need to have a confirmation that VMs running on a host are not affected and nothing wrong with their I/O operations.
*** Bug 1565198 has been marked as a duplicate of this bug. ***
The flow of migrating storage traffic from mgmt network to dedicated storage network using iSCSI bond was tested.
Published document: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/administration_guide/index#Migrating_a_logical_network_to_an_iscsi_bond