For our release product, we have release noted the "host sets" limitation. Meanwhile, we made a temporary fix in cinder/volume/drivers/san/hp/hp_3par_common.py
try: self._delete_3par_host(hostname) self._remove_hosts_naming_dict_host(hostname)
- except hpexceptions.HTTPConflict as ex:
- # host will only be removed after all vluns
- # have been removed
- if 'has exported VLUN' in ex.get_description():
- pass
- else:
- raise
+ except Exception as ex:
+ LOG.info("Host '%s' could not be deleted: %s", hostname, ex.get_description())
We should not be removing the host for various reasons (host already exists, host a member of host set, host is a cluster member with other vluns attached, etc.). The host entry should be deleted if it gets created by the driver, but we currently do do that approach.
Hi Kurt,
For our release product, we have release noted the "host sets" limitation. Meanwhile, we made a temporary fix in cinder/ volume/ drivers/ san/hp/ hp_3par_ common. py
try:
self. _delete_ 3par_host( hostname)
self. _remove_ hosts_naming_ dict_host( hostname) HTTPConflict as ex: description( ): description( ))
- except hpexceptions.
- # host will only be removed after all vluns
- # have been removed
- if 'has exported VLUN' in ex.get_
- pass
- else:
- raise
+ except Exception as ex:
+ LOG.info("Host '%s' could not be deleted: %s", hostname, ex.get_
We should not be removing the host for various reasons (host already exists, host a member of host set, host is a cluster member with other vluns attached, etc.). The host entry should be deleted if it gets created by the driver, but we currently do do that approach.
Thanks for your looking into this problem.
-Yehia