<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div> </div>
<div>Hello List,</div>
<div> </div>
<div>i found in the meantime that the root of the problem is</div>
<div>that the iscsi client component of the driver is not able to connect to the iSCSI array from within the cinder-volume docker container.<br/>
But the same is possible from within the controller node, outside of the container...</div>
<div> </div>
<div>ICMP and even SSH from within the container to the iSCSI array work perfectly fine though.</div>
<div> </div>
<div>Therefore i believe this is most likely a sideeffect of the containerisation in the context of the Kolla-Ansible architecture...</div>
<div> </div>
<div>Not sure yet why the driver client behaves differently from the ssh client...</div>
<div> </div>
</div>
<div>
<div>Best</div>
<div> </div>
<div> </div>
<div>Stefan</div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Samstag, 20. März 2021 um 17:25 Uhr<br/>
<b>Von:</b> "Stefan Kelber" <Stefan.Kelber@gmx.de><br/>
<b>An:</b> "Radosław Piliszek" <radoslaw.piliszek@gmail.com>, openstack-discuss@lists.openstack.org<br/>
<b>Betreff:</b> Aw: Re: OpenStack Victoria - Kolla-Ansible - Cinder - iSCSI-backend - Update driver status failed: config is uninitialized.</div>
<div name="quoted-content">
<div style="font-family: Verdana;font-size: 12.0px;">
<div>
<div>Hello List,</div>
<div> </div>
<div>i managed to miss to reply to the list, hooray...</div>
<div> </div>
<div>That's why yoctozepto already had a look at the attached logs/config.</div>
<div>His take is that it is most likely in the realm of the driver, since the client keeps attempting to connect, which fails.</div>
<div>He also pointed out that the driver must end up in the container,</div>
<div>which fortunately is s.th. already taken care of, so the attached logs reflect that state.</div>
<div> </div>
<div>My hope is that someone recognises this error pattern from his/her iSCSI implementation,</div>
<div>since it seems to be quite typical...</div>
<div> </div>
</div>
<div>
<div>Best</div>
<div> </div>
<div>Stefan</div>
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Samstag, 20. März 2021 um 10:36 Uhr<br/>
<b>Von:</b> "Radosław Piliszek" <radoslaw.piliszek@gmail.com><br/>
<b>An:</b> "Stefan Kelber" <Stefan.Kelber@gmx.de><br/>
<b>Cc:</b> "openstack-discuss" <openstack-discuss@lists.openstack.org><br/>
<b>Betreff:</b> Re: OpenStack Victoria - Kolla-Ansible - Cinder - iSCSI-backend - Update driver status failed: config is uninitialized.</div>
<div>Hello Stefan,<br/>
<br/>
try adding in cinder-volume config, DEFAULT section:<br/>
<br/>
debug = true<br/>
<br/>
and then attaching its logs.<br/>
That sometimes unveils the underlying issue.<br/>
<br/>
-yoctozepto<br/>
<br/>
On Sat, Mar 20, 2021 at 12:41 AM Stefan Kelber <Stefan.Kelber@gmx.de> wrote:<br/>
><br/>
> Hello List,<br/>
><br/>
><br/>
><br/>
> 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).<br/>
><br/>
><br/>
><br/>
> I use a volume driver provided by the manufacturer, which is listed as "completely" supported by OpenStack.<br/>
><br/>
> And i can use it to log in to the array using the client.<br/>
><br/>
> iSCSI session is established.<br/>
><br/>
> Firewall etc off, as recommended.<br/>
><br/>
> 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.<br/>
><br/>
> Soon after having started the service cinder-volume, the service shuts down.<br/>
><br/>
> When reading the logfiles, it looks like the following error is the first one to show up, when starting the cinder-volume:<br/>
><br/>
><br/>
><br/>
> cinder-volume.log:<br/>
><br/>
> WARNING cinder.volume.manager [req-1290dad2-d09e-40f1-9b38-2f4b5e7accb8 - - - - -] Update driver status failed: (config name IFT-ISCSI) is uninitialized.<br/>
><br/>
> ERROR cinder.service [-] Manager for service cinder-volume host@IFT-ISCSI is reporting problems, not sending heartbeat. Service will appear "down".<br/>
><br/>
> DEBUG oslo_concurrency.lockutils [-] Acquired lock "singleton_lock" lock /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:266<br/>
><br/>
> DEBUG oslo_concurrency.lockutils [-] Releasing lock "singleton_lock" lock /usr/lib/python3.6/site-packages/oslo_concurrency/lockutils.py:282<br/>
><br/>
><br/>
><br/>
> cinder.conf is setup according to documentation by the manufacturer, and matches what i found similar from DELL and HITACHI.<br/>
><br/>
> Googling for this error unveils that this is a very frequent error, but non of the proposed solutions works for me.<br/>
><br/>
> Does any body have a clue where to look?<br/>
><br/>
> I am running out of ideas, unfortunately<br/>
><br/>
> Best<br/>
><br/>
> SK</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></body></html>