OpenStack Victoria - Kolla-Ansible - Cinder - iSCSI-backend - Update driver status failed: config is uninitialized.

Radosław Piliszek radoslaw.piliszek at gmail.com
Sat Mar 20 09:36:39 UTC 2021


Hello Stefan,

try adding in cinder-volume config, DEFAULT section:

  debug = true

and then attaching its logs.
That sometimes unveils the underlying issue.

-yoctozepto

On Sat, Mar 20, 2021 at 12:41 AM Stefan Kelber <Stefan.Kelber at gmx.de> wrote:
>
> Hello List,
>
>
>
> i have trouble connecting an INFORTREND iSCSI array as external iSCSI backend to Cinder in OpenStack Victoria, deployed via Kolla-Ansible (All in One, it's still PoC).
>
>
>
> I use a volume driver provided by the manufacturer, which is listed as "completely" supported by OpenStack.
>
> And i can use it to log in to the array using the client.
>
> iSCSI session is established.
>
> Firewall etc off, as recommended.
>
> I can even start cinder-volume and as long as this service stays up, i can create volumes and remove them, but always they are reported in "Error" state.
>
> Soon after having started the service cinder-volume, the service shuts down.
>
> When reading the logfiles, it looks like the following error is the first one to show up, when starting the cinder-volume:
>
>
>
> cinder-volume.log:
>
> WARNING cinder.volume.manager [req-1290dad2-d09e-40f1-9b38-2f4b5e7accb8 - - - - -] Update driver status failed: (config name IFT-ISCSI) is uninitialized.
>
> ERROR cinder.service [-] Manager for service cinder-volume host at IFT-ISCSI is reporting problems, not sending heartbeat. Service will appear "down".
>
> DEBUG oslo_concurrency.lockutils [-] Acquired lock "singleton_lock" lock /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:266
>
> DEBUG oslo_concurrency.lockutils [-] Releasing lock "singleton_lock" lock /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:282
>
>
>
> cinder.conf is setup according to documentation by the manufacturer, and matches what i found similar from DELL and HITACHI.
>
> Googling for this error unveils that this is a very frequent error, but non of the proposed solutions works for me.
>
> Does any body have a clue where to look?
>
> I am running out of ideas, unfortunately
>
> Best
>
> SK



More information about the openstack-discuss mailing list