Comment 1 for bug 1770611

Hi Pedro,

please find the response on your query:
>>> The problem here is that I couldn´t reproduce it yet but to me it´s important to know if somehow invalid CHAPs in DB can be used to update host definition and secret on 3PAR. Could you answer this question? If this is the case, do we need to perform some update on cinder DB to avoid this issue?

HPE 3par driver do not directly update the cinder.volumes table with CHAP secret, its the cinder layer who sits on the top of the hpe 3par drivers updates the cinder DB. and this is what recommended

from driver, create_export() is responsible for updation of CHAP secret in cinder.volumes table

Since you already have vluns created in 3par with CHAP secret key, hpe3par driver.create_export(), will fetch the same secret from existing vlun and that secret will be set for newly created ones.

There might be some operation done, which triggers the bug #1737181 & #1690244 and due to which the CHAP is not/incorrectly set in 3par, and this is not sync with create_export()

As you have already tried applpying the patch https://review.openstack.org/#/c/531669/4 and https://review.openstack.org/#/c/482103/, but it didn't worked.

I suggest to remove all the vluns from 3par for any ONE specific host and then apply both the patches, restart the services and then perform the same operation from using that host