You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, the cinder-volume service ignores the linstor_default_uri specified and defaults to using linstor://localhost, errors-out when unable to do so, and goes into a crash-backoff loop.
We've identified the code responsible for this behavior and prepared a patch/diff file:
The changes look good, but against what branch/release did you do the patch?
Latest version(einstein) seems to have fixed most of those things, except of 2 occurrences, which I'm going to fix in a sec
The changes look good, but against what branch/release did you do the patch?
These changes were made against the "stein" release; the Python venv version is cinder-20.1.5 and cinder-20.2.1.dev3, we were using this repository for Cinder with OpenStack-Ansible.
We are currently using LINSTOR controllers in a HA configuration accessible from a floating IP managed by Corosync+Pacemaker.
Our
cinder.conf
uses the following configuration (organization specific data obfuscated) for the LINSTOR backend:However, the
cinder-volume
service ignores thelinstor_default_uri
specified and defaults to usinglinstor://localhost
, errors-out when unable to do so, and goes into a crash-backoff loop.We've identified the code responsible for this behavior and prepared a patch/diff file:
linstor.txt
After applying this patch/diff, the
cinder-volume
service accepts the specified URI and works properly in sending API requests to our controller.Can these changes be verified?
The text was updated successfully, but these errors were encountered: