When lio is configured for iscsi_helper things break due to usage of CONF (Juno)

Bug #1455249 reported by John Griffith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
High
John Griffith
Nominated for Juno by Jay Bryant

Bug Description

In the base volume driver there's a check for iscsi_helper that then results in a call to initialize_connection that is intended to be for configurations using LIO iscsi_helper:
    https://github.com/openstack/cinder/blob/stable/juno/cinder/volume/driver.py#L1022

The problem is that this is using the global CONF instead of self.configuration, which means that every driver on the system will pick up this setting and attempt the initialize. This includes drivers that have their own target mechanism and don't use LIO or Tgt etc.

This is particularly problematic because RHEL based distributions have switched to using LIO as the default iscsi_helper and tools like packstack and foreman appear to configure this automatically. So if somebody attempts to configure a backend like SolidFire things like copy-image-to-volume will fail during the attach phase because the initialize_connection method is not implemented in those drivers.

This was fixed in Kilo during target rework, but we never went back and fixed it in Juno.

summary: When lio is configured for iscsi_helper things break due to usage of
- CONF
+ CONF (Juno)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (stable/juno)

Fix proposed to branch: stable/juno
Review: https://review.openstack.org/183330

Jay Bryant (jsbryant)
Changed in cinder:
importance: Undecided → High
assignee: nobody → John Griffith (john-griffith)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (stable/juno)

Change abandoned by John Griffith (<email address hidden>) on branch: stable/juno
Review: https://review.openstack.org/183330

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.