XtremIO/OpenStack: Two minutes delay when attaching XtremIO volume in iSCSI configuration

Summary: Two minutes delay may occur when attaching XtremIO volume in OpenStack iSCSI configuration. If there are some XtremIO iSCSI target ports that are not connected to the OpenStack host, it will wait until the iSCSI login timeout occurs. By default, there is a 2-minutes wait. There will be a delay, but the volume attach process will succeed. This timeout occurs in all cases when trying to attach volume in OpenStack. Here are some examples where this can occur: 1. Creating a volume from an image 2. Changing volume type 3. Server (instance) start from Bootable Volume 4. Adding a volume to server (instance) 5. Migration (Live or Cold) 6. Evacuate ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

Even if XtremIO has 8 defined iSCSI ports (have IP address) and only 4 iSCSI ports can be accessed from OpenStack by partitioning the subnet, OpenStack will try to iSCSI login to all the iSCSI ports.

In this case, wait for the iSCSI login to timeout.

This timeout is 2 minutes by default (defined by /etc/iscsi/iscsid.conf).

[cinder-volume.log]
2021-01-21 23:58:02.015 1062 DEBUG oslo.privsep.daemon [-] privsep: Exception during request[140370202752416]: Unexpected error while running command.
Command: iscsiadm -m node -T <Initiator WWN> -p x.x.x.x:3260 --login
Exit code: 8
Stdout: 'Logging in to [iface: default, target: <Initiator WWN>, portal: x.x.x.x,3260]\n
'Stderr: 'iscsiadm: Could not login to [iface: default, target: <Initiator WWN>, portal: x.x.x.x,3260].\n
iscsiadm: initiator reported error (8 - connection timed out)\n
iscsiadm: Could not log into all portals\n
' _process_cmd /usr/lib/python3.6/site-packages/oslo_privsep/daemon.py:454
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/oslo_privsep/daemon.py", line 449, in _process_cmd
    ret = func(*f_args, **f_kwargs)
  File "/usr/lib/python3.6/site-packages/oslo_privsep/priv_context.py", line 247, in _wrap
    return func(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/os_brick/privileged/rootwrap.py", line 194, in execute_root
    return custom_execute(*cmd, shell=False, run_as_root=False, **kwargs)
  File "/usr/lib/python3.6/site-packages/os_brick/privileged/rootwrap.py", line 143, in custom_execute
    on_completion=on_completion, *cmd, **kwargs)
  File "/usr/lib/python3.6/site-packages/oslo_concurrency/processutils.py", line 424, in execute
    cmd=sanitized_cmd)
oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command.
Command: iscsiadm -m node -T <Initiator WWN> -p x.x.x.x:3260 --login
Exit code: 8

Cause

XtremIO cinder driver (xtremio.py) returns all XtremIO target ports to cinder/osbrick.

The cinder/osbrick tries iSCSI login to all target ports returned by the XtremIO cinder driver.

This is the designed behavior of XtremIO cinder driver.

There is no option in cinder.conf to limit/specify the target ports.

Resolution

Change the network configuration so that the IP addresses of all target ports can be connected from the OpenStack host.

If there is an unused iSCSI port, delete the IP setting for that port.

Affected Products

XtremIO, XtremIO Family, XtremIO HW Gen2 400GB, XtremIO HW Gen2 400GB Encrypt Capbl, XtremIO HW Gen2 400GB Encrypt Disable, XtremIO HW Gen2 400GB Exp Encrypt Disable, XtremIO HW Gen2 400GB Expandable, XtremIO HW Gen2 800GB Encrypt Capbl , XtremIO HW Gen2 800GB Encrypt Disable, XtremIO HW Gen3 40TB, XtremIO HW Gen3 40TB Encrypt Disable, XtremIO HW X2-R, XtremIO HW X2-R Encrypt Disable, XtremIO HW X2-S, XtremIO HW X2-S Encrypt Disable, XtremIO HW X2-T, XtremIO HW X2-T Encrypt Disable, XtremIO X1, XtremIO X2 ...
Article Properties
Article Number: 000183724
Article Type: Solution
Last Modified: 30 Aug 2022
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.