Cinder IBM SVC driver always uses iscsi for addhost

[Margarita Shakhova]

We are using SVC FC driver. This driver always deleted host when no more mappings exists. The host is authomatically created for the first mapping.

There is no option to use -fcwwpn in host creation, --iscsiname is used both for FC and ISCSI drivers:
https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/ibm/storwize_svc/storwize_svc_common.py#L232

This leads to degraded host with two usable FC ports and one unusable ISCSI port.

[Shrey Bhatnagar (shrey.bhatnagar)]

Hi Shakhova,

I want to reproduce this issue.
Please, provide all steps and logs.

Thanks,
Shrey

[Margarita Shakhova (shakhova-margarita)]

Hi,

In order to reproduce this issue you need a test lab with FC connection only (no ISCSI) between hosts and storage.

The easiest way to reproduce:

1. delete all LUNs if they already exist on host so the host will be disconnected from storage, you will se a warning in the log indicating that no volumes mapped:
https://github.com/openstack/cinder/blob/master/cinder/volume/drivers/ibm/storwize_svc/storwize_svc_common.py#L1223

2. create a new LUN - for example, start a VM booted from volume on the host from 1.

3. Check on Storwize Web UI that the host is now in Degraded state, this is because it was connected via ISCSI port which is unavailable.