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
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
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
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,
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
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
6 matches
Mail list logo
