On 03/12/2014 10:45 PM, ybronhei wrote:
On 03/12/2014 04:33 PM, Itamar Heim wrote:
On 03/12/2014 04:32 PM, ybronhei wrote:
On 03/12/2014 04:25 PM, Dan Kenigsberg wrote:
On Wed, Mar 12, 2014 at 10:15:21AM +0200, Itamar Heim wrote:
On 03/12/2014 10:11 AM, Sven Kieske wrote: >=20 >=20 > Am 11.03.2014 17:38, schrieb Itamar Heim: >>=20 >> i understood this to "you can't use 4.14 with 3.4.0". >=20 > Well I examined BZ 1067096 again, this is what did not work: >=20 > Steps to Reproduce: > 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 > 2. Add node (vdsm 4.14) >=20 > Actual results: > Host is installed with VDSM version (4.14) and cannot join = cluster > which > is compatible with VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10]. >=20 > Pay attention to the engine version, it states 3.3. not 3.4.0 >=20 > So my conclusion is, you can't install vdsm 4.14. when you want > to use engine 3.3. >=20 > Am I reading something wrong? >=20 > Here's the link again: > https://bugzilla.redhat.com/show_bug.cgi?id=3D1067096#c0 >=20 =20 this can be fixed via engine config, but is not supposed to be needed, as vdsm is supposed to have vdsm/dsaversion.py.in: 'supportedENGINEs': ['3.0', '3.1', = '3.2', '3.3', '3.4'], =20 danken/eli - thoughts? =20 I do not really understand why we have this recurrent Engine bug, = of ignoring supportedENGINEs; I think Yaniv does. =20 =20 i recall asking for detailed explanation for why do we have 3 = different restrictions , one for supportedEngines, one for the allowed vdsm versions, and one for the cluster level? =20 if vdsm version is supported why isn't it in engine's capabilities = yet? =20 because its a vdsm version which was released after that engine was released, hence the vdsm package has to declare its supporting the =
--Apple-Mail=_DBDEE8BE-C036-4EB7-8792-8529E5E0E9DD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Mar 12, 2014, at 5:14 PM, Itamar Heim <iheim@redhat.com> wrote: old
engine. =20 =20 so its an hack to allow users to add beta vdsm version to new engine release?.. sounds like that =20 no. its to add the next release of vdsm to a previously released = engine. but that's not supposed to be an issue, since its supposed to = already report the previous version of engine (which it does) =20 =20 please reopen if it reproduced =20
=20 the issue was verified in https://bugzilla.redhat.com/show_bug.cgi?id=3D1016461 , please = reopen if it still appears =20 =20 =20 =20 =20 =20 =20
I do have an issue still with this. When I try to change compatibility version at the datacenter level it = behaves as expected, i.e. warns me to change the cluster level first. I = see a matching log entry in the engine log. However when I try to change = the compatibility version at the cluster level the edit cluster dialog = box just hangs there. There are no log entries in the engine log. The = dialog box goes away when I click cancel. If I select 3.2 or 3.3 and = click OK nothing happens. This occurs either during normal running or = with hosts in maintenance mode. I would like to change to 3.3. Can you direct me to the sql table or cmd = line by any chance.=20 Is this a known problem or something specific to my special setup. = Actually my setup is pretty plain, see below or original post in this = thread. Engine 3.3.4-1.el6 CO6.5 Nodes are 3.0.4-1.0.201401291204.el6 Storage is SAN --Apple-Mail=_DBDEE8BE-C036-4EB7-8792-8529E5E0E9DD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: = after-white-space;"><br><div><div><div>On Mar 12, 2014, at 5:14 PM, = Itamar Heim <<a = href=3D"mailto:iheim@redhat.com">iheim@redhat.com</a>> = wrote:</div><br class=3D"Apple-interchange-newline"><blockquote = type=3D"cite"><div style=3D"font-size: 12px; font-style: normal; = font-variant: normal; font-weight: normal; letter-spacing: normal; = line-height: normal; orphans: auto; text-align: start; text-indent: 0px; = text-transform: none; white-space: normal; widows: auto; word-spacing: = 0px; -webkit-text-stroke-width: 0px;">On 03/12/2014 10:45 PM, ybronhei = wrote:<br><blockquote type=3D"cite">On 03/12/2014 04:33 PM, Itamar Heim = wrote:<br><blockquote type=3D"cite">On 03/12/2014 04:32 PM, ybronhei = wrote:<br><blockquote type=3D"cite">On 03/12/2014 04:25 PM, Dan = Kenigsberg wrote:<br><blockquote type=3D"cite">On Wed, Mar 12, 2014 at = 10:15:21AM +0200, Itamar Heim wrote:<br><blockquote type=3D"cite">On = 03/12/2014 10:11 AM, Sven Kieske wrote:<br><blockquote = type=3D"cite"><br><br>Am 11.03.2014 17:38, schrieb Itamar = Heim:<br><blockquote type=3D"cite"><br>i understood this to "you can't = use 4.14 with 3.4.0".<br></blockquote><br>Well I examined BZ 1067096 = again, this is what did not work:<br><br>Steps to Reproduce:<br>1. = Run Engine 3.3 Compatibility level 3.2 or 3.3<br>2. Add node = (vdsm 4.14)<br><br>Actual results:<br>Host is installed with VDSM = version (4.14) and cannot join cluster<br>which<br>is compatible with = VDSM versions [4.13, 4.9, 4.11, 4.12, 4.10].<br><br>Pay attention to the = engine version, it states 3.3. not 3.4.0<br><br>So my conclusion is, you = can't install vdsm 4.14. when you want<br>to use engine 3.3.<br><br>Am I = reading something wrong?<br><br>Here's the link again:<br><a = href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1067096#c0">https://= bugzilla.redhat.com/show_bug.cgi?id=3D1067096#c0</a><br><br></blockquote><= br>this can be fixed via engine config, but is not supposed to = be<br>needed, as vdsm is supposed to have<br>vdsm/dsaversion.py.in: = 'supportedENGINEs': ['3.0', '3.1', '3.2',<br>'3.3', = '3.4'],<br><br>danken/eli - thoughts?<br></blockquote><br>I do not = really understand why we have this recurrent Engine bug, of<br>ignoring = supportedENGINEs; I think Yaniv does.<br><br></blockquote><br>i recall = asking for detailed explanation for why do we have 3 = different<br>restrictions , one for supportedEngines, one for the = allowed vdsm<br>versions, and one for the cluster level?<br><br>if vdsm = version is supported why isn't it in engine's capabilities = yet?<br></blockquote><br>because its a vdsm version which was released = after that engine was<br>released, hence the vdsm package has to declare = its supporting the old<br>engine.<br><br></blockquote><br>so its an hack = to allow users to add beta vdsm version to new engine<br>release?.. = sounds like that<br></blockquote><br>no. its to add the next release of = vdsm to a previously released engine. but that's not supposed to be an = issue, since its supposed to already report the previous version of = engine (which it does)<br><br><blockquote type=3D"cite"><br>please = reopen if it reproduced<br><br><blockquote type=3D"cite"><blockquote = type=3D"cite"><br>the issue was verified in<br><a = href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1016461">https://bug= zilla.redhat.com/show_bug.cgi?id=3D1016461</a><span = class=3D"Apple-converted-space"> </span>, please reopen if<br>it = still = appears<br><br><br><br></blockquote><br></blockquote><br><br></blockquote>= <br></div></blockquote></div><div><br></div>I do have an issue still = with this.</div><div>When I try to change compatibility version at the = datacenter level it behaves as expected, i.e. warns me to change the = cluster level first. I see a matching log entry in the engine log. = However when I try to change the compatibility version at the cluster = level the edit cluster dialog box just hangs there. There are no log = entries in the engine log. The dialog box goes away when I click cancel. = If I select 3.2 or 3.3 and click OK nothing happens. This occurs either = during normal running or with hosts in maintenance = mode.</div><div><br></div><div>I would like to change to 3.3. Can you = direct me to the sql table or cmd line by any = chance. </div><div><br></div><div>Is this a known problem or = something specific to my special setup. Actually my setup is = pretty plain, see below or original post in this = thread.</div><div><br></div><div>Engine = 3.3.4-1.el6</div><div>CO6.5</div><div>Nodes are = 3.0.4-1.0.201401291204.el6</div><div>Storage is = SAN</div><div><br></div><div><br></div></body></html>= --Apple-Mail=_DBDEE8BE-C036-4EB7-8792-8529E5E0E9DD--