2:49 p.m.
--_000_DBXPR06MB544F4ED5888DED7D2252803C3300DBXPR06MB544eurprd_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi all,
1 of our older clusters in use, consists of 2 nodes contain Fedora 20, with=
the virt-preview repository enabled.
The Engine itself is installed on a dedicated server (CentOS 6) and is stil=
l on version 3.5.1.1-1.el6.
During some maintenance a couple of days ago on the Fedora 20 nodes, also =
the installed vdsm package was updated by the engineer working on the nodes=
.
We went from version 'vdsm-4.16.10-8.gitc937927.fc20' to 'vdsm-4.16.26-0.fc=
20'.
This morning I wanted to remove some old snapshots on running vm's, only to=
find out that the delete button is once again greyed out.
I also created a new snapshot on a running vm to test if it would only happ=
en on snapshots that were already there before the update, but the delete b=
utton would still remain greyed out.
Only turning off the vm allows me to use the delete button.
When looking at the nodes within the cluster, they both still have Live Sna=
pshot Support on Active.
Before the vdsm update, the live merge functionality worked perfectly.
Anybody experienced something similar?
Could It be because the Engine is still running on 3.5.1?
We are also running 2 clusters with F21 nodes that have the same vdsm versi=
on nummer installed and they don't have an issue at all; connected to the s=
ame engine.
Kind Regards,
Roel
--_000_DBXPR06MB544F4ED5888DED7D2252803C3300DBXPR06MB544eurprd_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml"
xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word"
=
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"
xmlns=3D"http:=
//www.w3.org/TR/REC-html40" <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Dus-ascii"=
<meta name=3D"Generator" content=3D"Microsoft
Word 15 (filtered medium)" <style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.E-mailStijl17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1558859571;
mso-list-type:hybrid;
mso-list-template-ids:-237859530 673224566 68354051 68354053 68354049 6835=
4051 68354053 68354049 68354051 68354053;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" / </xml><![endif]--><!--[if gte mso
9]><xml <o:shapelayout
v:ext=3D"edit" <o:idmap v:ext=3D"edit"
data=3D"1" /
</o:shapelayout></xml><![endif]--
</head <body lang=3D"NL"
link=3D"#0563C1" vlink=3D"#954F72" <div
class=3D"WordSection1" <p
class=3D"MsoNormal">Hi all,<o:p></o:p></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB">1 of our older clusters in use,=
consists of 2 nodes contain Fedora 20, with the virt-preview repository en=
abled.<o:p></o:p></span></p <p
class=3D"MsoNormal"><span lang=3D"EN-GB">The Engine itself is
installed =
on a dedicated server (CentOS 6) and is still on version 3.5.1.1-1.el6.<o:p=
></o:p></span></p <p
class=3D"MsoNormal"><span
lang=3D"EN-GB"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB">During some maintenance a coupl=
e of days ago on the Fedora 20 nodes, also the installed vdsm package=
was updated by the engineer working on the
nodes.<o:p></o:p></span></p <p
class=3D"MsoNormal"><span lang=3D"EN-GB">We went from version
‘vds=
m-4.16.10-8.gitc937927.fc20’ to
‘vdsm-4.16.26-0.fc20’.<o:=
p></o:p></span></p <p
class=3D"MsoNormal"><span
lang=3D"EN-GB"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB">This morning I wanted to remove=
some old snapshots on running vm’s, only to find out that the delete=
button is once again greyed out.<o:p></o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB">I also created a new snapshot o=
n a running vm to test if it would only happen on snapshots that were alrea=
dy there before the update, but the delete button would still remain greyed=
out.<o:p></o:p></span></p <p
class=3D"MsoNormal"><span lang=3D"EN-GB">Only turning off the
vm allows =
me to use the delete button.
<o:p></o:p></span></p <p
class=3D"MsoNormal"><span
lang=3D"EN-GB"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB">When looking at the nodes withi=
n the cluster, they both still have Live Snapshot Support on Active.<o:p></=
o:p></span></p <p
class=3D"MsoNormal"><span lang=3D"EN-GB">Before the vdsm
update, the liv=
e merge functionality worked perfectly.<o:p></o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB">Anybody experienced something s=
imilar?<o:p></o:p></span></p <p
class=3D"MsoNormal"><span lang=3D"EN-GB">Could It be because
the Engine =
is still running on 3.5.1?<o:p></o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB">We are also running 2 clusters =
with F21 nodes that have the same vdsm version nummer installed and they do=
n’t have an issue at all; connected to the same
engine.<o:p></o:p></s=
pan></p <p
class=3D"MsoNormal"><span
lang=3D"EN-GB"><o:p> </o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB"><o:p></o:p></span></p <p class=3D"MsoNormal"><span
lang=3D"EN-GB">Kind Regards,<o:p></o:p></span>=
</p <p class=3D"MsoNormal"><span
lang=3D"EN-GB">Roel<o:p></o:p></span></p </div
</body </html
--_000_DBXPR06MB544F4ED5888DED7D2252803C3300DBXPR06MB544eurprd_--
4:37 p.m.
Fedora 20 is not supportrd, in particular with virt-preview repo, which is
not maintained few month before Fedora 20 went EOL.
The best advice is to upgrade the host to Fedora 21.
בתאריך 13 באוק׳ 2015 3:04 אחה״צ, "Roel de Rooy" <RdeRooy(a)motto.nl> כתב:
Hi all,
1 of our older clusters in use, consists of 2 nodes contain Fedora 20,
with the virt-preview repository enabled.
The Engine itself is installed on a dedicated server (CentOS 6) and is
still on version 3.5.1.1-1.el6.
During some maintenance a couple of days ago on the Fedora 20 nodes, also
the installed vdsm package was updated by the engineer working on the nodes.
We went from version ‘vdsm-4.16.10-8.gitc937927.fc20’ to
‘vdsm-4.16.26-0.fc20’.
This morning I wanted to remove some old snapshots on running vm’s, only
to find out that the delete button is once again greyed out.
I also created a new snapshot on a running vm to test if it would only
happen on snapshots that were already there before the update, but the
delete button would still remain greyed out.
Only turning off the vm allows me to use the delete button.
When looking at the nodes within the cluster, they both still have Live
Snapshot Support on Active.
Before the vdsm update, the live merge functionality worked perfectly.
Anybody experienced something similar?
Could It be because the Engine is still running on 3.5.1?
We are also running 2 clusters with F21 nodes that have the same vdsm
version nummer installed and they don’t have an issue at all; connected to
the same engine.
Kind Regards,
Roel
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3328
days inactive
3328
days old
1 comments
2 participants
participants (2)
-
Nir Soffer -
Roel de Rooy