Re: [Users] affects of changing compatibility setting on running cluster
- Original Message - > From: "Charles Weber" > To: "Tomas Jelinek" > Cc: "Omer Frenkel" , users@ovirt.org, "Sven Kieske" > > Sent: Monday, March 17, 2014 8:44:09 PM > Subject: Re: [Users] affects of changing compatibility setting on running > cluster > > > On Mar 17, 2014, at 4:41 AM, Tomas Jelinek wrote: > > > > > > > - Original Message - > >> From: "Omer Frenkel" > >> To: "Itamar Heim" , "Tomas Jelinek" > >> > >> Cc: "Charles Weber" , "ybronhei" > >> , "Dan Kenigsberg" , > >> users@ovirt.org, "Eli Mesika" , "Sven Kieske" > >> > >> Sent: Sunday, March 16, 2014 10:04:12 AM > >> Subject: Re: [Users] affects of changing compatibility setting on running > >> cluster > >> > >> > >> > >> ----- Original Message - > >>> From: "Itamar Heim" > >>> To: "Charles Weber" > >>> Cc: "ybronhei" , "Dan Kenigsberg" > >>> , > >>> users@ovirt.org, "Eli Mesika" > >>> , "Sven Kieske" , "Omer > >>> Frenkel" > >>> > >>> Sent: Friday, March 14, 2014 12:58:57 AM > >>> Subject: Re: [Users] affects of changing compatibility setting on running > >>> cluster > >>> > >>> On 03/13/2014 05:33 PM, Charles Weber wrote: > >>>> > >>>> On Mar 12, 2014, at 5:14 PM, Itamar Heim >>>> <mailto:ih...@redhat.com>> wrote: > >>>> > >>>>> 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: > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>> Am 11.03.2014 17:38, schrieb Itamar Heim: > >>>>>>>>>>>> > >>>>>>>>>>>> i understood this to "you can't use 4.14 with 3.4.0". > >>>>>>>>>>> > >>>>>>>>>>> Well I examined BZ 1067096 again, this is what did not work: > >>>>>>>>>>> > >>>>>>>>>>> Steps to Reproduce: > >>>>>>>>>>> 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 > >>>>>>>>>>> 2. Add node (vdsm 4.14) > >>>>>>>>>>> > >>>>>>>>>>> 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]. > >>>>>>>>>>> > >>>>>>>>>>> Pay attention to the engine version, it states 3.3. not 3.4.0 > >>>>>>>>>>> > >>>>>>>>>>> So my conclusion is, you can't install vdsm 4.14. when you want > >>>>>>>>>>> to use engine 3.3. > >>>>>>>>>>> > >>>>>>>>>>> Am I reading something wrong? > >>>>>>>>>>> > >>>>>>>>>>> Here's the link again: > >>>>>>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 > >>>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> 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'], > >>>>>>>>>
Re: [Users] affects of changing compatibility setting on running cluster
On Mar 17, 2014, at 4:41 AM, Tomas Jelinek wrote: > > > - Original Message - >> From: "Omer Frenkel" >> To: "Itamar Heim" , "Tomas Jelinek" >> Cc: "Charles Weber" , "ybronhei" , >> "Dan Kenigsberg" , >> users@ovirt.org, "Eli Mesika" , "Sven Kieske" >> >> Sent: Sunday, March 16, 2014 10:04:12 AM >> Subject: Re: [Users] affects of changing compatibility setting on running >> cluster >> >> >> >> - Original Message - >>> From: "Itamar Heim" >>> To: "Charles Weber" >>> Cc: "ybronhei" , "Dan Kenigsberg" , >>> users@ovirt.org, "Eli Mesika" >>> , "Sven Kieske" , "Omer Frenkel" >>> >>> Sent: Friday, March 14, 2014 12:58:57 AM >>> Subject: Re: [Users] affects of changing compatibility setting on running >>> cluster >>> >>> On 03/13/2014 05:33 PM, Charles Weber wrote: >>>> >>>> On Mar 12, 2014, at 5:14 PM, Itamar Heim >>> <mailto:ih...@redhat.com>> wrote: >>>> >>>>> 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: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Am 11.03.2014 17:38, schrieb Itamar Heim: >>>>>>>>>>>> >>>>>>>>>>>> i understood this to "you can't use 4.14 with 3.4.0". >>>>>>>>>>> >>>>>>>>>>> Well I examined BZ 1067096 again, this is what did not work: >>>>>>>>>>> >>>>>>>>>>> Steps to Reproduce: >>>>>>>>>>> 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 >>>>>>>>>>> 2. Add node (vdsm 4.14) >>>>>>>>>>> >>>>>>>>>>> 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]. >>>>>>>>>>> >>>>>>>>>>> Pay attention to the engine version, it states 3.3. not 3.4.0 >>>>>>>>>>> >>>>>>>>>>> So my conclusion is, you can't install vdsm 4.14. when you want >>>>>>>>>>> to use engine 3.3. >>>>>>>>>>> >>>>>>>>>>> Am I reading something wrong? >>>>>>>>>>> >>>>>>>>>>> Here's the link again: >>>>>>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 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'], >>>>>>>>>> >>>>>>>>>> danken/eli - thoughts? >>>>>>>>> >>>>>>>>> I do not really understand why we have this recurrent Engine bug, of >>>>>>>>> ignoring supportedENGINEs; I think Yaniv does. >>>>>>>>> >>>>>>>> >>>>>>>> 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? >>>>>>>> >>>>>>>> if vdsm version is supported why isn't it in engine's capabilities >>>>>>
Re: [Users] affects of changing compatibility setting on running cluster
- Original Message - > From: "Omer Frenkel" > To: "Itamar Heim" , "Tomas Jelinek" > Cc: "Charles Weber" , "ybronhei" , > "Dan Kenigsberg" , > users@ovirt.org, "Eli Mesika" , "Sven Kieske" > > Sent: Sunday, March 16, 2014 10:04:12 AM > Subject: Re: [Users] affects of changing compatibility setting on running > cluster > > > > - Original Message - > > From: "Itamar Heim" > > To: "Charles Weber" > > Cc: "ybronhei" , "Dan Kenigsberg" , > > users@ovirt.org, "Eli Mesika" > > , "Sven Kieske" , "Omer Frenkel" > > > > Sent: Friday, March 14, 2014 12:58:57 AM > > Subject: Re: [Users] affects of changing compatibility setting on running > > cluster > > > > On 03/13/2014 05:33 PM, Charles Weber wrote: > > > > > > On Mar 12, 2014, at 5:14 PM, Itamar Heim > > <mailto:ih...@redhat.com>> wrote: > > > > > >> 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: > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> Am 11.03.2014 17:38, schrieb Itamar Heim: > > >>>>>>>>> > > >>>>>>>>> i understood this to "you can't use 4.14 with 3.4.0". > > >>>>>>>> > > >>>>>>>> Well I examined BZ 1067096 again, this is what did not work: > > >>>>>>>> > > >>>>>>>> Steps to Reproduce: > > >>>>>>>> 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 > > >>>>>>>> 2. Add node (vdsm 4.14) > > >>>>>>>> > > >>>>>>>> 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]. > > >>>>>>>> > > >>>>>>>> Pay attention to the engine version, it states 3.3. not 3.4.0 > > >>>>>>>> > > >>>>>>>> So my conclusion is, you can't install vdsm 4.14. when you want > > >>>>>>>> to use engine 3.3. > > >>>>>>>> > > >>>>>>>> Am I reading something wrong? > > >>>>>>>> > > >>>>>>>> Here's the link again: > > >>>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 > > >>>>>>>> > > >>>>>>> > > >>>>>>> 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'], > > >>>>>>> > > >>>>>>> danken/eli - thoughts? > > >>>>>> > > >>>>>> I do not really understand why we have this recurrent Engine bug, of > > >>>>>> ignoring supportedENGINEs; I think Yaniv does. > > >>>>>> > > >>>>> > > >>>>> 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? > > >>>>> > > >>>>> if vdsm version is supported why isn't it in engine's capabilities > > >>>>> yet? > > >>>> > > >>>> because its a vdsm version which was released after that engine was > > >>>> released, hence the vdsm package has to declare its supporting the old > > >>>> engine. > > >
Re: [Users] affects of changing compatibility setting on running cluster
- Original Message - > From: "Itamar Heim" > To: "Charles Weber" > Cc: "ybronhei" , "Dan Kenigsberg" , > users@ovirt.org, "Eli Mesika" > , "Sven Kieske" , "Omer Frenkel" > > Sent: Friday, March 14, 2014 12:58:57 AM > Subject: Re: [Users] affects of changing compatibility setting on running > cluster > > On 03/13/2014 05:33 PM, Charles Weber wrote: > > > > On Mar 12, 2014, at 5:14 PM, Itamar Heim > <mailto:ih...@redhat.com>> wrote: > > > >> 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: > >>>>>>>> > >>>>>>>> > >>>>>>>> Am 11.03.2014 17:38, schrieb Itamar Heim: > >>>>>>>>> > >>>>>>>>> i understood this to "you can't use 4.14 with 3.4.0". > >>>>>>>> > >>>>>>>> Well I examined BZ 1067096 again, this is what did not work: > >>>>>>>> > >>>>>>>> Steps to Reproduce: > >>>>>>>> 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 > >>>>>>>> 2. Add node (vdsm 4.14) > >>>>>>>> > >>>>>>>> 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]. > >>>>>>>> > >>>>>>>> Pay attention to the engine version, it states 3.3. not 3.4.0 > >>>>>>>> > >>>>>>>> So my conclusion is, you can't install vdsm 4.14. when you want > >>>>>>>> to use engine 3.3. > >>>>>>>> > >>>>>>>> Am I reading something wrong? > >>>>>>>> > >>>>>>>> Here's the link again: > >>>>>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 > >>>>>>>> > >>>>>>> > >>>>>>> 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'], > >>>>>>> > >>>>>>> danken/eli - thoughts? > >>>>>> > >>>>>> I do not really understand why we have this recurrent Engine bug, of > >>>>>> ignoring supportedENGINEs; I think Yaniv does. > >>>>>> > >>>>> > >>>>> 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? > >>>>> > >>>>> if vdsm version is supported why isn't it in engine's capabilities yet? > >>>> > >>>> because its a vdsm version which was released after that engine was > >>>> released, hence the vdsm package has to declare its supporting the old > >>>> engine. > >>>> > >>> > >>> so its an hack to allow users to add beta vdsm version to new engine > >>> release?.. sounds like that > >> > >> 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) > >> > >>> > >>> please reopen if it reproduced > >>> > >>>>> > >>>>> the issue was verified in > >>>>> https://bugzilla.redhat.com/show_bug.cgi?id=1016461, please reopen if > >>>>> it still appears > >>>>> > >>>>> > >>>>> > >>>> > >>> > >>> > >> > > > > 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. > > do not hack the db for such a change, you may skip important upgrade > logic/validation. > > > > > 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. > > sounds like a bug, at least for not telling you what is the error. > omer - thoughts? > if nothing happens when clicking ok it's usually some validation in the dialog, can you check there is nothing highlighted in red (check also other tabs in the dialog)? adding Tomas, might have a better idea. you can try updating using rest api (change user/pass and cluster uuid): curl -X PUT -H "Accept: application/xml" -H "Content-Type: application/xml" -u "admin@internal:password" "http://localhost:8080/api/clusters/dd746d43-4bd1-46aa-b97b-b7bad3f2e498"; -d "" > > > > Engine 3.3.4-1.el6 > > CO6.5 > > Nodes are 3.0.4-1.0.201401291204.el6 > > Storage is SAN > > > > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
On 03/13/2014 05:33 PM, Charles Weber wrote: On Mar 12, 2014, at 5:14 PM, Itamar Heim mailto:ih...@redhat.com>> wrote: 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: Am 11.03.2014 17:38, schrieb Itamar Heim: i understood this to "you can't use 4.14 with 3.4.0". Well I examined BZ 1067096 again, this is what did not work: Steps to Reproduce: 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 2. Add node (vdsm 4.14) 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]. Pay attention to the engine version, it states 3.3. not 3.4.0 So my conclusion is, you can't install vdsm 4.14. when you want to use engine 3.3. Am I reading something wrong? Here's the link again: https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 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'], danken/eli - thoughts? I do not really understand why we have this recurrent Engine bug, of ignoring supportedENGINEs; I think Yaniv does. 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? if vdsm version is supported why isn't it in engine's capabilities yet? because its a vdsm version which was released after that engine was released, hence the vdsm package has to declare its supporting the old engine. so its an hack to allow users to add beta vdsm version to new engine release?.. sounds like that 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) please reopen if it reproduced the issue was verified in https://bugzilla.redhat.com/show_bug.cgi?id=1016461, please reopen if it still appears 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. do not hack the db for such a change, you may skip important upgrade logic/validation. 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. sounds like a bug, at least for not telling you what is the error. omer - thoughts? Engine 3.3.4-1.el6 CO6.5 Nodes are 3.0.4-1.0.201401291204.el6 Storage is SAN ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
On Mar 12, 2014, at 5:14 PM, Itamar Heim wrote: > 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: >>> >>> >>> Am 11.03.2014 17:38, schrieb Itamar Heim: i understood this to "you can't use 4.14 with 3.4.0". >>> >>> Well I examined BZ 1067096 again, this is what did not work: >>> >>> Steps to Reproduce: >>> 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 >>> 2. Add node (vdsm 4.14) >>> >>> 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]. >>> >>> Pay attention to the engine version, it states 3.3. not 3.4.0 >>> >>> So my conclusion is, you can't install vdsm 4.14. when you want >>> to use engine 3.3. >>> >>> Am I reading something wrong? >>> >>> Here's the link again: >>> https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 >>> >> >> 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'], >> >> danken/eli - thoughts? > > I do not really understand why we have this recurrent Engine bug, of > ignoring supportedENGINEs; I think Yaniv does. > 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? if vdsm version is supported why isn't it in engine's capabilities yet? >>> >>> because its a vdsm version which was released after that engine was >>> released, hence the vdsm package has to declare its supporting the old >>> engine. >>> >> >> so its an hack to allow users to add beta vdsm version to new engine >> release?.. sounds like that > > 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) > >> >> please reopen if it reproduced >> the issue was verified in https://bugzilla.redhat.com/show_bug.cgi?id=1016461 , please reopen if it still appears >>> >> >> > 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. 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 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
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: Am 11.03.2014 17:38, schrieb Itamar Heim: i understood this to "you can't use 4.14 with 3.4.0". Well I examined BZ 1067096 again, this is what did not work: Steps to Reproduce: 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 2. Add node (vdsm 4.14) 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]. Pay attention to the engine version, it states 3.3. not 3.4.0 So my conclusion is, you can't install vdsm 4.14. when you want to use engine 3.3. Am I reading something wrong? Here's the link again: https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 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'], danken/eli - thoughts? I do not really understand why we have this recurrent Engine bug, of ignoring supportedENGINEs; I think Yaniv does. 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? if vdsm version is supported why isn't it in engine's capabilities yet? because its a vdsm version which was released after that engine was released, hence the vdsm package has to declare its supporting the old engine. so its an hack to allow users to add beta vdsm version to new engine release?.. sounds like that 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) please reopen if it reproduced the issue was verified in https://bugzilla.redhat.com/show_bug.cgi?id=1016461 , please reopen if it still appears ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
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: Am 11.03.2014 17:38, schrieb Itamar Heim: i understood this to "you can't use 4.14 with 3.4.0". Well I examined BZ 1067096 again, this is what did not work: Steps to Reproduce: 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 2. Add node (vdsm 4.14) 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]. Pay attention to the engine version, it states 3.3. not 3.4.0 So my conclusion is, you can't install vdsm 4.14. when you want to use engine 3.3. Am I reading something wrong? Here's the link again: https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 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'], danken/eli - thoughts? I do not really understand why we have this recurrent Engine bug, of ignoring supportedENGINEs; I think Yaniv does. 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? if vdsm version is supported why isn't it in engine's capabilities yet? because its a vdsm version which was released after that engine was released, hence the vdsm package has to declare its supporting the old engine. so its an hack to allow users to add beta vdsm version to new engine release?.. sounds like that please reopen if it reproduced the issue was verified in https://bugzilla.redhat.com/show_bug.cgi?id=1016461 , please reopen if it still appears -- Yaniv Bronhaim. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
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: Am 11.03.2014 17:38, schrieb Itamar Heim: i understood this to "you can't use 4.14 with 3.4.0". Well I examined BZ 1067096 again, this is what did not work: Steps to Reproduce: 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 2. Add node (vdsm 4.14) 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]. Pay attention to the engine version, it states 3.3. not 3.4.0 So my conclusion is, you can't install vdsm 4.14. when you want to use engine 3.3. Am I reading something wrong? Here's the link again: https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 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'], danken/eli - thoughts? I do not really understand why we have this recurrent Engine bug, of ignoring supportedENGINEs; I think Yaniv does. 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? if vdsm version is supported why isn't it in engine's capabilities yet? because its a vdsm version which was released after that engine was released, hence the vdsm package has to declare its supporting the old engine. the issue was verified in https://bugzilla.redhat.com/show_bug.cgi?id=1016461 , please reopen if it still appears ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
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: Am 11.03.2014 17:38, schrieb Itamar Heim: i understood this to "you can't use 4.14 with 3.4.0". Well I examined BZ 1067096 again, this is what did not work: Steps to Reproduce: 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 2. Add node (vdsm 4.14) 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]. Pay attention to the engine version, it states 3.3. not 3.4.0 So my conclusion is, you can't install vdsm 4.14. when you want to use engine 3.3. Am I reading something wrong? Here's the link again: https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 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'], danken/eli - thoughts? I do not really understand why we have this recurrent Engine bug, of ignoring supportedENGINEs; I think Yaniv does. 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? if vdsm version is supported why isn't it in engine's capabilities yet? the issue was verified in https://bugzilla.redhat.com/show_bug.cgi?id=1016461 , please reopen if it still appears -- Yaniv Bronhaim. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
On Wed, Mar 12, 2014 at 10:15:21AM +0200, Itamar Heim wrote: > On 03/12/2014 10:11 AM, Sven Kieske wrote: > > > > > >Am 11.03.2014 17:38, schrieb Itamar Heim: > >> > >>i understood this to "you can't use 4.14 with 3.4.0". > > > >Well I examined BZ 1067096 again, this is what did not work: > > > >Steps to Reproduce: > >1. Run Engine 3.3 Compatibility level 3.2 or 3.3 > >2. Add node (vdsm 4.14) > > > >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]. > > > >Pay attention to the engine version, it states 3.3. not 3.4.0 > > > >So my conclusion is, you can't install vdsm 4.14. when you want > >to use engine 3.3. > > > >Am I reading something wrong? > > > >Here's the link again: > >https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 > > > > 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'], > > danken/eli - thoughts? I do not really understand why we have this recurrent Engine bug, of ignoring supportedENGINEs; I think Yaniv does. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
On 03/12/2014 10:11 AM, Sven Kieske wrote: Am 11.03.2014 17:38, schrieb Itamar Heim: i understood this to "you can't use 4.14 with 3.4.0". Well I examined BZ 1067096 again, this is what did not work: Steps to Reproduce: 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 2. Add node (vdsm 4.14) 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]. Pay attention to the engine version, it states 3.3. not 3.4.0 So my conclusion is, you can't install vdsm 4.14. when you want to use engine 3.3. Am I reading something wrong? Here's the link again: https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 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'], danken/eli - thoughts? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
Am 11.03.2014 17:38, schrieb Itamar Heim: > > i understood this to "you can't use 4.14 with 3.4.0". Well I examined BZ 1067096 again, this is what did not work: Steps to Reproduce: 1. Run Engine 3.3 Compatibility level 3.2 or 3.3 2. Add node (vdsm 4.14) 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]. Pay attention to the engine version, it states 3.3. not 3.4.0 So my conclusion is, you can't install vdsm 4.14. when you want to use engine 3.3. Am I reading something wrong? Here's the link again: https://bugzilla.redhat.com/show_bug.cgi?id=1067096#c0 -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
On 03/11/2014 05:35 PM, Sven Kieske wrote: Sorry, I just read to quick over the BZ, you're right :) Would it be worth backporting this to 3.3.5 ? If I understand this correctly you are not able to use vdsm 4.14 with any ovirt-engine version < 3.4.0 ? i understood this to "you can't use 4.14 with 3.4.0". at least then ovirt-engine 3.3.x shouldn't try to deploy vdsm 4.14 on hosts. it should. Am 11.03.2014 15:58, schrieb Itamar Heim: seems 3.4.0 to me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
Sorry, I just read to quick over the BZ, you're right :) Would it be worth backporting this to 3.3.5 ? If I understand this correctly you are not able to use vdsm 4.14 with any ovirt-engine version < 3.4.0 ? at least then ovirt-engine 3.3.x shouldn't try to deploy vdsm 4.14 on hosts. Am 11.03.2014 15:58, schrieb Itamar Heim: > seems 3.4.0 to me -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
On 03/11/2014 04:54 PM, Sven Kieske wrote: This is a known bug: https://bugzilla.redhat.com/show_bug.cgi?id=1067096 this was retargeted to 3.4.1 seems 3.4.0 to me I suspect to much automation, as this should maybe block the 3.4 GA release? Am 11.03.2014 15:22, schrieb Itamar Heim: On 03/06/2014 04:59 PM, Charles Weber wrote: Hi everyone, I believe I need to change my cluster compatibility level and would like to know if I can do this ona live cluster or if I have to change everything to maintenance mode first. I ran engine setup and upgraded to current engine level then tried to add a new node using the 3.3.4 el6 iso. This resulted in an error: Host x.x.x.x is installed with VDSM version (4.14) and cannot join cluster Default which is compatible with VDSM versions [4.13,4.9,4.11,4.12,4.10]. My current versions are: Engine 3.3.4-1.el6 at compatibiltiy version 3.2 2 Nodes running CentOS 6.4 with VDSM 4.10.3-0.36.23.el6 Am I correct that I need to change the compatibility version to 3.3? This has some production VMs, do I need to turn everything off first or is this a non-interruptive change? How will this upgrade affect my current 2 hosts at their version? My original idea was to migrate working VMs to new ovirt ISO node and then re-install original nodes to the same version off the 3.3.4 el6 iso. I appreciate any advice. Chuck ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users actually no. this sounds like a bug in VDSM 4.14 not updated to report compatibility with ovirt-engine 3.3 danken? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
This is a known bug: https://bugzilla.redhat.com/show_bug.cgi?id=1067096 this was retargeted to 3.4.1 I suspect to much automation, as this should maybe block the 3.4 GA release? Am 11.03.2014 15:22, schrieb Itamar Heim: > On 03/06/2014 04:59 PM, Charles Weber wrote: >> Hi everyone, >> I believe I need to change my cluster compatibility level and would >> like to know if I can do this ona live cluster or if I have to change >> everything to maintenance mode first. >> >> I ran engine setup and upgraded to current engine level then tried to >> add a new node using the 3.3.4 el6 iso. This resulted in an error: >> >> Host x.x.x.x is installed with VDSM version (4.14) and cannot join >> cluster Default which is compatible with VDSM versions >> [4.13,4.9,4.11,4.12,4.10]. >> >> My current versions are: >> Engine 3.3.4-1.el6 at compatibiltiy version 3.2 >> >> 2 Nodes running CentOS 6.4 with VDSM 4.10.3-0.36.23.el6 >> >> Am I correct that I need to change the compatibility version to 3.3? >> This has some production VMs, do I need to turn everything off first >> or is this a non-interruptive change? >> How will this upgrade affect my current 2 hosts at their version? >> >> My original idea was to migrate working VMs to new ovirt ISO node and >> then re-install original nodes to the same version off the 3.3.4 el6 iso. >> >> I appreciate any advice. >> Chuck >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > > actually no. this sounds like a bug in VDSM 4.14 not updated to report > compatibility with ovirt-engine 3.3 > danken? > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > > -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] affects of changing compatibility setting on running cluster
On 03/06/2014 04:59 PM, Charles Weber wrote: Hi everyone, I believe I need to change my cluster compatibility level and would like to know if I can do this ona live cluster or if I have to change everything to maintenance mode first. I ran engine setup and upgraded to current engine level then tried to add a new node using the 3.3.4 el6 iso. This resulted in an error: Host x.x.x.x is installed with VDSM version (4.14) and cannot join cluster Default which is compatible with VDSM versions [4.13,4.9,4.11,4.12,4.10]. My current versions are: Engine 3.3.4-1.el6 at compatibiltiy version 3.2 2 Nodes running CentOS 6.4 with VDSM 4.10.3-0.36.23.el6 Am I correct that I need to change the compatibility version to 3.3? This has some production VMs, do I need to turn everything off first or is this a non-interruptive change? How will this upgrade affect my current 2 hosts at their version? My original idea was to migrate working VMs to new ovirt ISO node and then re-install original nodes to the same version off the 3.3.4 el6 iso. I appreciate any advice. Chuck ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users actually no. this sounds like a bug in VDSM 4.14 not updated to report compatibility with ovirt-engine 3.3 danken? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] affects of changing compatibility setting on running cluster
Hi everyone, I believe I need to change my cluster compatibility level and would like to know if I can do this ona live cluster or if I have to change everything to maintenance mode first. I ran engine setup and upgraded to current engine level then tried to add a new node using the 3.3.4 el6 iso. This resulted in an error: Host x.x.x.x is installed with VDSM version (4.14) and cannot join cluster Default which is compatible with VDSM versions [4.13,4.9,4.11,4.12,4.10]. My current versions are: Engine 3.3.4-1.el6 at compatibiltiy version 3.2 2 Nodes running CentOS 6.4 with VDSM 4.10.3-0.36.23.el6 Am I correct that I need to change the compatibility version to 3.3? This has some production VMs, do I need to turn everything off first or is this a non-interruptive change? How will this upgrade affect my current 2 hosts at their version? My original idea was to migrate working VMs to new ovirt ISO node and then re-install original nodes to the same version off the 3.3.4 el6 iso. I appreciate any advice. Chuck ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
