Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-12 Thread Bill Dossett
To: Daniel Helgenberger; Bill Dossett Cc: users@ovirt.org Subject: Re: [ovirt-users] Fwd: RE: FC QLogic question - Original Message - On 11.09.2014 14:23, Fabian Deutsch wrote: Hey Daniel, - Original Message - On 11.09.2014 14:09, Fabian Deutsch wrote: Hey Bill and Daniel

Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-12 Thread Sander Grendelman
This could also be an selinux issue with FC on the node, I've hit that one before. Especially since the luns do show up with multipath -ll Could be as simple as flipping a sanlock related selinux boolean. A quick test would be to boot in permissive mode. See

Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-12 Thread Bill Dossett
. Thanks all for the help. Bill From: sander.grendel...@gmail.com [mailto:sander.grendel...@gmail.com] On Behalf Of Sander Grendelman Sent: 12 September 2014 08:28 To: Bill Dossett Cc: users@ovirt.org Subject: Re: [ovirt-users] Fwd: RE: FC QLogic question This could also be an selinux issue

Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-12 Thread Bill Dossett
Grendelman Cc: users@ovirt.org Subject: Re: [ovirt-users] Fwd: RE: FC QLogic question Hmmm… I’ve just gone to add a storage domain and in the admin portal and bingo bango, all my LUNs appeared. Just wiping out everything from my last lab now. Thanks everyone, I am not quite sure why it started

[ovirt-users] Fwd: RE: FC QLogic question

2014-09-11 Thread Daniel Helgenberger
Hi Daniel, I did a lsmod | grep qxl and it returned nothing... did you perhaps mean qla? [root@ovirt141 ~]# lsmod | grep qla qla2xxx 466573 56 I think that is the one lsscsi does list all of the LUNs... so that's working! But

Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-11 Thread Fabian Deutsch
Hey Bill and Daniel, it would indeed be interesting - mandatory - to know if it's qla* or qxl (qxl is IMHO related to graphics). Once we know that I'll see if the bug below fixes it. I'd need your help to verify that we are also including all relevant dependencies. Thanks - fabian -

Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-11 Thread Fabian Deutsch
Hey Daniel, - Original Message - On 11.09.2014 14:09, Fabian Deutsch wrote: Hey Bill and Daniel, it would indeed be interesting - mandatory - to know if it's qla* or qxl (qxl is IMHO related to graphics). Once we know that I'll see if the bug below fixes it. Hello Fabian,

Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-11 Thread Daniel Helgenberger
On 11.09.2014 14:23, Fabian Deutsch wrote: Hey Daniel, - Original Message - On 11.09.2014 14:09, Fabian Deutsch wrote: Hey Bill and Daniel, it would indeed be interesting - mandatory - to know if it's qla* or qxl (qxl is IMHO related to graphics). Once we know that I'll see if

Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-11 Thread Fabian Deutsch
- Original Message - On 11.09.2014 14:23, Fabian Deutsch wrote: Hey Daniel, - Original Message - On 11.09.2014 14:09, Fabian Deutsch wrote: Hey Bill and Daniel, it would indeed be interesting - mandatory - to know if it's qla* or qxl (qxl is IMHO related to

Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-11 Thread Daniel Helgenberger
Hi Sven! Thanks for the heads up on the BZ. One question remains; if the firmware is missing in oVirt node then how come Bill does the module loaded and all the LUNs with lsscsi? Cheers, -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19

Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-11 Thread Sven Kieske
I really don't know, maybe it got silently fixed and the BZ was not updated. Just another reason _not_ to use node (sorry fabian) imho. On 11/09/14 18:16, Daniel Helgenberger wrote: Hi Sven! Thanks for the heads up on the BZ. One question remains; if the firmware is missing in oVirt

Re: [ovirt-users] Fwd: RE: FC QLogic question

2014-09-11 Thread Sven Kieske
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11.09.2014 19:20, Douglas Schilling Landgraf wrote: I do believe we are improving all components of oVirt release after release, including oVirt Node. Discouraging people to use it (or any other component) won't help the project. We are here to