thanks for the quick reply and investigation.
Please update me if I can help any further and if you find the cause and
have a patch let me know.
Note that ovirt-engine project is broken and if we cannot find the cause
relatively fast we should consider reverting the patch to allow a new
package to
After running a few OSTs manually, it seems that the patch is the cause.
Investigating...
On Tue, 7 May 2019 at 14:58, Andrej Krejcir wrote:
> Hi,
>
> The issue is probably not caused by the patch.
>
> This log line means that the VM does not exist in the DB:
>
> 2019-05-07 06:02:04,215-04 WARN
On Tue, 7 May 2019, 15:55 Marcin Sobczyk, wrote:
> Hi,
>
> there's one issue with 'python2-enum34' - it's an 'epel' package. I don't
> know if it's going to land in 'base' repository, but until then I think we
> should rely on 'python-enum34'.
> On 5/2/19 6:41 PM, Nir Soffer wrote:
>
>
>
> On
Hi,
The issue is probably not caused by the patch.
This log line means that the VM does not exist in the DB:
2019-05-07 06:02:04,215-04 WARN
[org.ovirt.engine.core.bll.MigrateMultipleVmsCommand]
(EE-ManagedThreadFactory-commandCoordinator-Thread-2) [33485140] Validation
of action
Hi,
there's one issue with 'python2-enum34' - it's an 'epel' package. I
don't know if it's going to land in 'base' repository, but until then I
think we should rely on 'python-enum34'.
On 5/2/19 6:41 PM, Nir Soffer wrote:
On Thu, May 2, 2019 at 7:29 PM Dan Kenigsberg
Hi,
We are failing test upgrade_hosts on upgrade-from-release-suite-master.
>From the logs I can see that we are calling migrate vm when we have only
one host and the vm seem to have been shut down before the maintenance call
is issued.
Can you please look into this?
suspected patch reported as
https://gerrit.ovirt.org/#/c/99729/
On Tue, May 7, 2019 at 12:53 PM Nir Soffer wrote:
> On Tue, May 7, 2019 at 7:16 AM Galit Rosenthal
> wrote:
>
>> By default, the SD type is set to V5.
>> and in the test, there was a condition when version < 4.1 was set to V3.
>> We added a fix on
On Tue, May 7, 2019 at 7:16 AM Galit Rosenthal wrote:
> By default, the SD type is set to V5.
> and in the test, there was a condition when version < 4.1 was set to V3.
> We added a fix on 4.1<=versions <=4.2 it will set to V4
>
Sounds good. Can you link to the patches fixing this?
On Tue,