off topic = newbie with bugzilla, gerrit and ovirt VDSM 4.14
Hi, I have a problem with an automatic yum vdsm upgrade (4.13 to 4.14) on ovirt 3.3 : 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]. I am searching the solution and one of them (from bz Bug 1083008 ) points to gerrit site(http://gerrit.ovirt.org/#/c/23456/) I do not have any experience in solving bugs, neither bz, gerrit, github.... How to initialize in this world and solve the ovirt problem ? another thing : does downgrade or remove vdms package excludes the installed virtual machines ? I know about ovirt 3.4 is the new release, but I want to learn how to solve some bugs when new releases is not launched; (off course I am afraid to upgrade to ovirt 3.4 too :) ) Tamer
On Wed, Apr 09, 2014 at 11:06:44AM -0300, Tamer Lima wrote:
Hi,
I have a problem with an automatic yum vdsm upgrade (4.13 to 4.14) on ovirt 3.3 : 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].
I am searching the solution and one of them (from bz Bug 1083008 ) points to gerrit site(http://gerrit.ovirt.org/#/c/23456/)
I do not have any experience in solving bugs, neither bz, gerrit, github.... How to initialize in this world and solve the ovirt problem ?
another thing : does downgrade or remove vdms package excludes the installed virtual machines ?
I know about ovirt 3.4 is the new release, but I want to learn how to solve some bugs when new releases is not launched;
(off course I am afraid to upgrade to ovirt 3.4 too :) )
Which exact version of Engine do you have? We have a recurrent bug of Engine not honoring Vdsm's supportedENGINEs. (Cf. Bug 1016461 - [vdsm] engine fails to add host with vdsm version 4.13.0) The simplest hack to do is to add 4.14 to SupportedVDSMVersions in Engines database. Eli and Yair could give the exact command line for that. I believe that there's work to fix this properly on Engine's side. Dan.
hi, I have now ovirt 3.4 with vdsm 4.14 Well, my question is not exactly how to solve an specific problem. In fact, what I want is learn how to apply the corrections proposed on bugzila, gerrit, etc. Or this is only for ovirt internal developers ? thanks tamer On Thu, Apr 10, 2014 at 8:28 AM, Dan Kenigsberg <danken@redhat.com> wrote:
On Wed, Apr 09, 2014 at 11:06:44AM -0300, Tamer Lima wrote:
Hi,
I have a problem with an automatic yum vdsm upgrade (4.13 to 4.14) on ovirt 3.3 : 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].
I am searching the solution and one of them (from bz Bug 1083008 ) points to gerrit site(http://gerrit.ovirt.org/#/c/23456/)
I do not have any experience in solving bugs, neither bz, gerrit, github.... How to initialize in this world and solve the ovirt problem ?
another thing : does downgrade or remove vdms package excludes the installed virtual machines ?
I know about ovirt 3.4 is the new release, but I want to learn how to solve some bugs when new releases is not launched;
(off course I am afraid to upgrade to ovirt 3.4 too :) )
Which exact version of Engine do you have? We have a recurrent bug of Engine not honoring Vdsm's supportedENGINEs. (Cf. Bug 1016461 - [vdsm] engine fails to add host with vdsm version 4.13.0)
The simplest hack to do is to add 4.14 to SupportedVDSMVersions in Engines database. Eli and Yair could give the exact command line for that.
I believe that there's work to fix this properly on Engine's side.
Dan.
On 04/10/2014 11:04 PM, Tamer Lima wrote:
hi,
I have now ovirt 3.4 with vdsm 4.14
danken - the bug you referenced is fixed in 3.3, yet recurs in 3.4?
Well, my question is not exactly how to solve an specific problem. In fact, what I want is learn how to apply the corrections proposed on bugzila, gerrit, etc. Or this is only for ovirt internal developers ? thanks
we'll be happy if you try. this would be the starting point. if anything is not clear, ask, and we should probably add it there: http://www.ovirt.org/Develop
tamer
On Thu, Apr 10, 2014 at 8:28 AM, Dan Kenigsberg <danken@redhat.com <mailto:danken@redhat.com>> wrote:
On Wed, Apr 09, 2014 at 11:06:44AM -0300, Tamer Lima wrote: > Hi, > > I have a problem with an automatic yum vdsm upgrade (4.13 to 4.14) on > ovirt 3.3 : 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]. > > I am searching the solution and one of them (from bz Bug 1083008 ) points > to gerrit site(http://gerrit.ovirt.org/#/c/23456/) > > I do not have any experience in solving bugs, neither bz, gerrit, > github.... > How to initialize in this world and solve the ovirt problem ? > > another thing : does downgrade or remove vdms package excludes the > installed virtual machines ? > > > I know about ovirt 3.4 is the new release, but I want to learn how to solve > some bugs when new releases is not launched; > > (off course I am afraid to upgrade to ovirt 3.4 too :) )
Which exact version of Engine do you have? We have a recurrent bug of Engine not honoring Vdsm's supportedENGINEs. (Cf. Bug 1016461 - [vdsm] engine fails to add host with vdsm version 4.13.0)
The simplest hack to do is to add 4.14 to SupportedVDSMVersions in Engines database. Eli and Yair could give the exact command line for that.
I believe that there's work to fix this properly on Engine's side.
Dan.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Fri, Apr 11, 2014 at 04:06:48PM +0300, Itamar Heim wrote:
On 04/10/2014 11:04 PM, Tamer Lima wrote:
hi,
I have now ovirt 3.4 with vdsm 4.14
danken - the bug you referenced is fixed in 3.3, yet recurs in 3.4?
I have very little explanations. The bug was hidden by an ad-hoc patch, adding "4.13" to SupportedVDSMVersions. I hope that Yaniv, Yair or Eli have better knowledge about the real fix, of honoring vdsm's supportedENGINEs again.
Well, my question is not exactly how to solve an specific problem. In fact, what I want is learn how to apply the corrections proposed on bugzila, gerrit, etc. Or this is only for ovirt internal developers ? thanks
we'll be happy if you try. this would be the starting point. if anything is not clear, ask, and we should probably add it there: http://www.ovirt.org/Develop
On 04/11/2014 06:24 PM, Dan Kenigsberg wrote:
On Fri, Apr 11, 2014 at 04:06:48PM +0300, Itamar Heim wrote:
On 04/10/2014 11:04 PM, Tamer Lima wrote:
hi,
I have now ovirt 3.4 with vdsm 4.14
danken - the bug you referenced is fixed in 3.3, yet recurs in 3.4?
I have very little explanations.
The bug was hidden by an ad-hoc patch, adding "4.13" to SupportedVDSMVersions. I hope that Yaniv, Yair or Eli have better knowledge about the real fix, of honoring vdsm's supportedENGINEs again.
Hey Tamer, actually, as dan stated, this is a bug that we currently work on. please check if http://gerrit.ovirt.org/#/c/26061 uses the supportedEngines set as should. with this patch the host should join the cluster properly.
Well, my question is not exactly how to solve an specific problem. In fact, what I want is learn how to apply the corrections proposed on bugzila, gerrit, etc. Or this is only for ovirt internal developers ? thanks
we'll be happy if you try. this would be the starting point. if anything is not clear, ask, and we should probably add it there: http://www.ovirt.org/Develop
-- Yaniv Bronhaim.
On 04/11/2014 06:24 PM, Dan Kenigsberg wrote:
On Fri, Apr 11, 2014 at 04:06:48PM +0300, Itamar Heim wrote:
On 04/10/2014 11:04 PM, Tamer Lima wrote:
hi,
I have now ovirt 3.4 with vdsm 4.14
danken - the bug you referenced is fixed in 3.3, yet recurs in 3.4?
I have very little explanations.
The bug was hidden by an ad-hoc patch, adding "4.13" to SupportedVDSMVersions. I hope that Yaniv, Yair or Eli have better knowledge about the real fix, of honoring vdsm's supportedENGINEs again.
Hey Tamer, until patch [1] will be merge, you can do the following: where your engine is installed connect as root than, "su - postgres" than run, psql [your-table-name, the default is "engine" if you didn't change it] (e.g "psql engine") than run " update vdc_options set option_value = '4.9,4.10,4.11,4.12,4.13,4.14' where option_name = 'SupportedVDSMVersions' " control+d to get out of psql restart engine service, and try to activate the host again this is a workaround to work with current implementation of validate the compatibility of the host to join the cluster. it adds vdsm 4.14 to the supported vdsm versions. please reply with the results regards,
Well, my question is not exactly how to solve an specific problem. In fact, what I want is learn how to apply the corrections proposed on bugzila, gerrit, etc. Or this is only for ovirt internal developers ? thanks
we'll be happy if you try. this would be the starting point. if anything is not clear, ask, and we should probably add it there: http://www.ovirt.org/Develop
-- Yaniv Bronhaim.
participants (4)
-
Dan Kenigsberg -
Itamar Heim -
Tamer Lima -
ybronhei