Hie scott ,read the links you sentbut since i am using targetcli on
Centos 7.3 ,isnt that supposed to have incoporated that patch already ,
will read deeper to see how i can get it fixed
On Sun, Apr 2, 2017 at 8:40 PM, Scott Worthington <
scott.c.worthing...@gmail.com> wrote:
> Also, this
Thanks for following up, Gianluca. At this point, my main question is why
should I configure iSCSI Bonds within the oVirt engine instead of or in
addition to configuring iSCSI initiators and multipathd directly in the host's
OS.
The multipath.conf created by VDSM works fine with our devices,
In my perspective, the ovirt developers put very general configuration of
multipath.conf file, which in their opinion should work with as much as
posslible arrays.
So you should modify this file and try to do some tests, plug in, plug out
links etc.
If you want to get luns picture, you should
No. You have to edit vdsm.conf, when:
1) link will be broken, and it point to the iSCSI target IP and
2) you want to reboot your host or restart VDSM
I don't know, why but VDSM during startup tries to connect to IP target in
my opinion it should use the /var/lib/iscsi configuration which was set
I am using Centos 7 and tgtd (scsi-target-utils)
# cat /etc/centos-release
CentOS Linux release 7.3.1611 (Core)
# tgtd -V
1.0.55
# rpm -qi scsi-target-utils
Name: scsi-target-utils
Version : 1.0.55
Release : 4.el7
Architecture: x86_64
... etc
--
Lukas Kaplan
2017-03-31
Also, this 'targetctlfix' script seems to have helped others, too:
https://github.com/wfurmank/targetctlfix/blob/master/targetctlfix
On 4/2/2017 2:15 PM, martin chamambo wrote:
> I managed to configure the mail iscsi domain for my ovirt 4.1 engine and
> node , it connects to the storage
You need to set a global filter to ignore PVs found in LVs.
Please read the comments in this bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1139441
Hope that helps you.
On 4/2/2017 2:15 PM, martin chamambo wrote:
> I managed to configure the mail iscsi domain for my ovirt 4.1 engine
I managed to configure the mail iscsi domain for my ovirt 4.1 engine and
node , it connects to the storage initially and initialises the data center
,but after rebooting the node and engine , it creates unecessary vg and lvs
like below
280246d3-ac7b-44ff-8c03-dc2bcb9edb70
> On 31 Mar 2017, at 15:49, Nelson Lameiras
> wrote:
>
> Hello,
>
> We had a rather unpleseant surprise while upgrading our production
> datacenters to oVirt 4.0 => 4.1 (although I think this problem is not related
> to oVirt 4.1).
> Some critical VMs
On Fri, Mar 31, 2017 at 3:23 PM, George Mcro wrote:
> Hello,
>
> My infrastructure consist of 2 ovirt-nodes and one ovirt-engine. All of
> them use Centos 7.
>
> I have already configured Ovirt-Engine and both of ovirt-nodes. Before I
> install the two ovirt-nodes in
Hi Alexey,
can you please attach the engine/vdsm logs?
thanks.
On Fri, Mar 31, 2017 at 11:08 AM, Николаев Алексей <
alexeynikolaev.p...@yandex.ru> wrote:
> Hi, community!
>
> I'm try using ISCSI DATA DOMAIN with oVirt 4.1.1.6-1 and oVirt Node 4.1.1.
> But get this error while adding data
Il 02 Apr 2017 05:20, "Devin A. Bougie" ha
scritto:
We have a new 4.1.1 cluster up and running with OVS switches and an iSCSI
hosted_storage and VM data domain (same target, different LUN's).
Everything works fine, and I can configure iscsid and multipathd outside of
12 matches
Mail list logo