10:02 p.m.
------=_Part_1485_589399674.1367780528187
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
I found this errors on the event:=20
The error message for connection Export_Domain_IP:/nfs_name returned by VDS=
M was: generalexception=20
Failed to connect Host node2 to the Storage Domains Name_of_Export_Domain.=
=20
Failed to connect Host node1 to Storage Pool acloudDC=20
I'm running version 3.2.1, is there a way to fix it?=20
Jose=20
----- Mensagem original -----
De: "Michael Kublin" <mkublin(a)redhat.com>=20
Para: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com>=20
Cc: "users" <users(a)ovirt.org>=20
Enviadas: Domingo, 5 Maio, 2013 11:37:59=20
Assunto: Re: [Users] NFS Export Doamin=20
----- Original Message -----=20
From: "Gianluca Cecchi"
<gianluca.cecchi(a)gmail.com>=20
To: "Allon Mureinik" <amureini(a)redhat.com>=20
Cc: "users" <users(a)ovirt.org>=20
Sent: Sunday, May 5, 2013 10:31:35 AM=20
Subject: Re: [Users] NFS Export Doamin=20
=20
=20
=20
=20
Il giorno 05/mag/2013 08:21, "Allon Mureinik" < amureini(a)redhat.com > ha=
=20
scritto:=20
>=20
> Frankly, the host status shouldn't depend on any domain status, as a se=
ries=20
> of recent patches fixed.=20
Host status never depend on
status of export/import/iso domains=20
> I don't think got into oVirt 3.2, however.=20
>=20
> I'm wondering if this work should be backported to 3.2.1/3.2.2, but it'=
s=20
> quite a major change, not sure the risk justifies it...=20
>=20
> ________________________________=20
>>=20
>> From: suporte(a)logicworks.pt=20
>> To: users(a)ovirt.org=20
>> Sent: Saturday, May 4, 2013 10:26:19 PM=20
>> Subject: [Users] NFS Export Doamin=20
>>=20
>>=20
>> Hi,=20
>>=20
>> I'm runing oVirt 3.2, I had to restart all the system, when the system=
=20
>> (engine, hosts and storage) comes up, the NFS export domain
was not=20
>> connected to the switch, i notice that the hosts did not come live=20
>> because of that. This is not a main storage, is this a normal behavior=
?=20
>>=20
No the behaviour is not normal.=20
The status of host never depend and should not depend on status of export (=
also import/iso) domains.=20
Did you see in engine logs something like that:=20
"Domain export-domain-name was reported with error code .... "=20
> >> Jose=20
>>=20
> >> --=20
> >> ________________________________=20
> >> Jose Ferradeira=20
> >> http://www.logicworks.pt=20
>>=20
>>=20
> >> _______________________________________________=20
> >> Users mailing list=20
> >> Users(a)ovirt.org=20
> >> http://lists.ovirt.org/mailman/listinfo/users=20
> >=20
> >=20
> >=20
> > _______________________________________________=20
> > Users mailing list=20
> > Users(a)ovirt.org=20
> > http://lists.ovirt.org/mailman/listinfo/users=20
> >=20
> At least Don't let that an export or iso domain down can determine whole=
=20
infrastructure down. ..=20
=20
_______________________________________________=20
Users mailing list=20
Users(a)ovirt.org=20
http://lists.ovirt.org/mailman/listinfo/users=20
=20
_______________________________________________=20
Users mailing list=20
Users(a)ovirt.org=20
http://lists.ovirt.org/mailman/listinfo/users=20
=EF=BB=BF=EF=BB=BF=20
------=_Part_1485_589399674.1367780528187
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><body><div style=3D"font-family: Times New Roman; font-size:
10pt; co=
lor: #000000"><div>I found this errors on the
event:<br></div><div><br></di=
v><div><div id=3D"gwt-uid-1533_col2_row60">The error message for
connection=
Export_Domain_IP:/nfs_name returned by VDSM was: generalexception</div><di=
v><div id=3D"gwt-uid-1533_col2_row63">Failed to connect Host node2 to
the S=
torage Domains Name_of_Export_Domain.</div><div><div
id=3D"gwt-uid-1533_col=
2_row64">Failed to connect Host node1 to Storage Pool
acloudDC</div><div><b=
r></div><div>I'm running version 3.2.1, is there a way to fix
it?<br></div>=
<div><br></div><div>Jose<br></div></div></div></div><hr
id=3D"zwchr"><div s=
tyle=3D"color:#000;font-weight:normal;font-style:normal;text-decoration:non=
e;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style=3D=
"color: #000; font-weight: normal; font-style: normal; text-decoration: non=
e; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>De:
</b>"M=
ichael Kublin" &lt;mkublin(a)redhat.com&gt;<br><b>Para:
</b>"Gianluca Cecchi"=
&lt;gianluca.cecchi(a)gmail.com&gt;<br><b>Cc:
</b>"users" &lt;users(a)ovirt.or=
g><br><b>Enviadas: </b>Domingo, 5 Maio, 2013
11:37:59<br><b>Assunto: </b=
Re: [Users] NFS Export
Doamin<br><div><br></div><br><div><br></div><br><di=
v><br></div>----- Original Message -----<br>> From:
"Gianluca Cecchi" &l=
t;gianluca.cecchi(a)gmail.com&gt;<br>&gt; To: "Allon Mureinik"
<amureini@r=
edhat.com><br>> Cc: "users"
&lt;users(a)ovirt.org&gt;<br>&gt; Sent: Sun=
day, May 5, 2013 10:31:35 AM<br>> Subject: Re: [Users] NFS Export Doamin=
<br>> <br>> <br>> <br>>
<br>> Il giorno 05/mag/2013 08:21, "=
Allon Mureinik" < amureini(a)redhat.com > ha<br>>
scritto:<br>> &=
gt; <br>> > Frankly, the host status shouldn't depend on any
domain s=
tatus, as a series<br>> > of recent patches fixed.<br>Host
status nev=
er depend on status of export/import/iso domains<br>> > I don't
think=
got into oVirt 3.2, however.<br>> > <br>> >
I'm wondering if t=
his work should be backported to 3.2.1/3.2.2, but it's<br>> >
quite a=
major change, not sure the risk justifies it...<br>> >
<br>> >=
________________________________<br>> >> <br>>
>> From: =
suporte(a)logicworks.pt<br>&gt; >> To:
users(a)ovirt.org<br>&gt; >>=
Sent: Saturday, May 4, 2013 10:26:19 PM<br>> >> Subject:
[Users] =
NFS Export Doamin<br>> >> <br>> >>
<br>> >> Hi,<=
br>> >> <br>> >> I'm runing oVirt
3.2, I had to restart a=
ll the system, when the system<br>> >> (engine, hosts and
storage)=
comes up, the NFS export domain was not<br>> >> connected to
the =
switch, i notice that the hosts did not come live<br>> >>
because =
of that. This is not a main storage, is this a normal behavior?<br>>
>=
;> <br>No the behaviour is not normal.<br>The status of host never
depen=
d and should not depend on status of export (also import/iso) domains.<br>D=
id you see in engine logs something like that:<br>"Domain export-domain-nam=
e was reported with error code .... "<br>> >>
Jose<br>> >>=
; <br>> >> --<br>> >>
________________________________<br=
> >> Jose Ferradeira<br>>
>> http://www.logicworks.pt<br=
> >> <br>> >> <br>>
>> ________________________=
_______________________<br>>
>> Users mailing list<br>> >>=
; Users(a)ovirt.org<br>&gt; >>
http://lists.ovirt.org/mailman/listinfo/=
users<br>> > <br>> > <br>> >
<br>> > ______________=
_________________________________<br>> > Users mailing
list<br>> &=
gt; Users(a)ovirt.org<br>&gt; >
http://lists.ovirt.org/mailman/listinfo/us=
ers<br>> > <br>> At least Don't let that an export or
iso domain d=
own can determine whole<br>> infrastructure down. ..<br>>
<br>> __=
_____________________________________________<br>> Users mailing list<br=
> Users(a)ovirt.org<br>&gt;
http://lists.ovirt.org/mailman/listinfo/users=
<br>>
<br>_______________________________________________<br>Users maili=
ng list<br>Users@ovirt.org<br>http://lists.ovirt.org/mailman/listinfo/users=
<br></div><div><br></div><div style=3D"position:
absolute; left: -40px; top=
: -25px; width: 1px; height: 1px; overflow: hidden;" data-mce-bogus=3D"1"
c=
lass=3D"mcePaste"
id=3D"_mcePaste">=EF=BB=BF=EF=BB=BF</div></div></body></h=
tml>
------=_Part_1485_589399674.1367780528187--