9:33 a.m.
Thank you
----- Original Message -----
From: "Ian Fraser" <Ian.Fraser(a)asm.org.uk>
To: "Maor Lipchuk" <mlipchuk(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Wednesday, August 12, 2015 2:48:46 PM
Subject: RE: [ovirt-users] iSCSI Bond fails
Hi Maor,
Sorry for the delay in replying, I had to destroy the original environment
but have managed to repeat the problem.
I was already able to use the iSCSI storage domain before trying to add the
bond if that is what you are asking.
I have opened bug: 1252809 and attached vdsm.logs from all 3 machines.
Best regards
Ian Fraser
Systems Administrator | Agency Sector Management (UK) Limited |
www.asm.org.uk
[t] +44 (0)1784 242200 | [m] +44 (0)7974 776893 | [f] +44 (0)1784 242012 |
[e] Ian.Fraser(a)asm.org.uk
Registered in England No. 2053849 | Registered address: Ashford House 41-45
Church Road Ashford Middx TW15 2TQ
Follow us on twitter @asmukltd
-----Original Message-----
From: Maor Lipchuk [mailto:mlipchuk@redhat.com]
Sent: 28 July 2015 18:12
To: Ian Fraser
Cc: users(a)ovirt.org
Subject: Re: [ovirt-users] iSCSI Bond fails
Hi Ian,
Can u try to connect with this interface through the Host to the iSCSI
storage?
Can u please open a bug and add the VDSM logs as well
Regards,
Maor
----- Original Message -----
> From: "Ian Fraser" <Ian.Fraser(a)asm.org.uk>
> To: users(a)ovirt.org
> Sent: Tuesday, July 28, 2015 6:08:30 PM
> Subject: [ovirt-users] iSCSI Bond fails
>
>
>
> Hi All,
>
>
>
> When I add a iSCSI bond to 2 interfaces that are pointing to 2 targets
> I get an event “iSCSI bond 'bondname' was successfully updated but
> some of the hosts encountered connection issues”
>
>
>
> What I believe is relevant in the engine.log:
>
>
>
> 2015-07-28 13:19:32,593 ERROR
> [org.ovirt.engine.core.bll.storage.AddIscsiBondCommand]
> (org.ovirt.thread.pool-8-thread-19) [5bd20956] Host vh-01 -
> 8251e76f-6469-4fe0-9d63-2d5feacd8cc0 encounter problems to connect to
> the iSCSI Storage Server. The following connections
>
> were problematic (connectionid=vdsm result):
> {c8485ac1-3b76-4cfe-af4a-20c2af91f43e=0,
> 43cb0e74-000e-4a80-ad28-45d6ac6da223=0,
> ed8c65aa-8448-45dd-b2f3-7f880669ce05=465,
> 2b5d8496-dc44-43f7-87a4-ec11c93e1291=0}
>
> 2015-07-28 13:19:32,706 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSComm
> and]
> (org.ovirt.thread.pool-8-thread-17) [5bd20956] FINISH,
> ConnectStorageServerVDSCommand, return:
> {ed8c65aa-8448-45dd-b2f3-7f880669ce05=465,
> 2b5d8496-dc44-43f7-87a4-ec11
>
> c93e1291=0, b9631bdd-52fa-485d-81ea-c26f0d6a0881=0,
> 4cea7519-eeae-4215-99a9-7926b1bae271=0}, log id: 44abae2c
>
> 2015-07-28 13:19:32,706 ERROR
> [org.ovirt.engine.core.bll.storage.AddIscsiBondCommand]
> (org.ovirt.thread.pool-8-thread-17) [5bd20956] Host vh-02 -
> c0ed58d7-1116-4281-8f97-dc76695172b7 encounter problems to connect to
> the iSCSI Storage Server. The following connections
>
> were problematic (connectionid=vdsm result):
> {ed8c65aa-8448-45dd-b2f3-7f880669ce05=465,
> 2b5d8496-dc44-43f7-87a4-ec11c93e1291=0,
> b9631bdd-52fa-485d-81ea-c26f0d6a0881=0,
> 4cea7519-eeae-4215-99a9-7926b1bae271=0}
>
> 2015-07-28 13:19:32,811 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSComm
> and]
> (org.ovirt.thread.pool-8-thread-49) [5bd20956] FINISH,
> ConnectStorageServerVDSCommand, return:
> {d7daaa08-889c-4efb-aa0f-92a2842fa493=0,
> bb96ef88-80d6-42a5-b4d1-96a4a1
>
> 29d7e6=0, ed8c65aa-8448-45dd-b2f3-7f880669ce05=465,
> 2b5d8496-dc44-43f7-87a4-ec11c93e1291=0}, log id: 6d6e6f3a
>
> 2015-07-28 13:19:32,811 ERROR
> [org.ovirt.engine.core.bll.storage.AddIscsiBondCommand]
> (org.ovirt.thread.pool-8-thread-49) [5bd20956] Host vh-03 -
> 0ca1f2ce-8c28-4954-9d9d-75519c3bf8a5 encounter problems to connect to
> the iSCSI Storage Server. The following connections
>
> were problematic (connectionid=vdsm result):
> {d7daaa08-889c-4efb-aa0f-92a2842fa493=0,
> bb96ef88-80d6-42a5-b4d1-96a4a129d7e6=0,
> ed8c65aa-8448-45dd-b2f3-7f880669ce05=465,
> 2b5d8496-dc44-43f7-87a4-ec11c93e1291=0}
>
> 2015-07-28 13:19:32,815 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (ajp--127.0.0.1-8702-9) [5bd20956] Correlation ID: 5bd20956, Call Stack:
> null, Custom Event ID: -1, Message: iSCSI bond 'bondname' was
> successfully created in Data Cent
>
> er 'Default' but some of the hosts encountered connection issues.
>
>
>
> Seemingly this part is relevant :
> ed8c65aa-8448-45dd-b2f3-7f880669ce05=465
>
>
>
> I looked up result 465 in vdsm/storage/storage_exception.py which is
> “Failed to setup iSCSI subsystem.” I have checked what I can for the
> connection
> ed8c65aa-8448-45dd-b2f3-7f880669ce05 and all seems well so I don’t
> know what it is trying to tell me.
>
>
>
> Does anyone know what might be wrong?
>
>
>
> Best regards
>
>
>
> Ian Fraser
>
>
>
> Systems Administrator | Agency Sector Management (UK) Limited |
> www.asm.org.uk
>
> [t] +44 (0)1784 242200 | [f] +44 (0)1784 242012 | [e]
> ian.fraser(a)asm.org.uk
>
> Ashford House 41-45 Church Road Ashford Middx TW15 2TQ
>
> Follow us on twitter @asmukltd
>
>
>
>
>
> The information in this message and any attachment is intended for the
> addressee and is confidential. If you are not that addressee, no
> action should be taken in reliance on the information and you should
> please reply to this message immediately to inform us of incorrect
> receipt and destroy this message and any attachments.
>
> For the purposes of internet level email security incoming and
> outgoing emails may be read by personnel other than the named recipient or
> sender.
>
> Whilst all reasonable efforts are made, ASM (UK) Ltd cannot guarantee
> that emails and attachments are virus free or compatible with your
> systems. You should make your own checks and ASM (UK) Ltd does not
> accept liability in respect of viruses or computer problems experienced.
> Registered address: Agency Sector Management (UK) Ltd. Ashford House,
> 41-45 Church Road, Ashford, Middlesex, TW15 2TQ Registered in England
> No.2053849
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
________________________________
The information in this message and any attachment is intended for the
addressee and is confidential. If you are not that addressee, no action
should be taken in reliance on the information and you should please reply
to this message immediately to inform us of incorrect receipt and destroy
this message and any attachments.
For the purposes of internet level email security incoming and outgoing
emails may be read by personnel other than the named recipient or sender.
Whilst all reasonable efforts are made, ASM (UK) Ltd cannot guarantee that
emails and attachments are virus free or compatible with your systems. You
should make your own checks and ASM (UK) Ltd does not accept liability in
respect of viruses or computer problems experienced.
Registered address: Agency Sector Management (UK) Ltd. Ashford House, 41-45
Church Road, Ashford, Middlesex, TW15 2TQ
Registered in England No.2053849
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________