Re: [ovirt-devel] [vdsm] stable branch ovirt-4.2 created

On 02/07/2018 08:46 AM, Dan Kenigsberg wrote: > On Tue, Feb 6, 2018 at 10:28 PM, Francesco Romani wrote: >> Hi all, >> >> >> With the help of Sandro (many thanks @sbonazzo !), we created minutes >> ago the ovirt-4.2 stable branch: >> >> >> Steps performed: >> >> 1. merged https://gerrit.ovirt.org/

Re: [ovirt-devel] [vdsm] stable branch ovirt-4.2 created

On Wed, Feb 7, 2018 at 10:14 AM, Francesco Romani wrote: > On 02/07/2018 08:46 AM, Dan Kenigsberg wrote: >> On Tue, Feb 6, 2018 at 10:28 PM, Francesco Romani wrote: >>> Hi all, >>> >>> >>> With the help of Sandro (many thanks @sbonazzo !), we created minutes >>> ago the ovirt-4.2 stable branch: >

Re: [ovirt-devel] [vdsm] stable branch ovirt-4.2 created

2018-02-07 12:58 GMT+01:00 Dan Kenigsberg : > On Wed, Feb 7, 2018 at 10:14 AM, Francesco Romani > wrote: > > On 02/07/2018 08:46 AM, Dan Kenigsberg wrote: > >> On Tue, Feb 6, 2018 at 10:28 PM, Francesco Romani > wrote: > >>> Hi all, > >>> > >>> > >>> With the help of Sandro (many thanks @sbonazz

[ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 07-02-2018 ] [ 004_basic_sanity.vm_run ]

Hi, We failed test 004_basic_sanity.vm_run in the upgrade from release suite. the reason we failed to run the vm is that the host was filtered from selection for vm. Please also notice other errors in the log relating to network sync failing. *Link and headline of suspected pat

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 07-02-2018 ] [ 004_basic_sanity.vm_run ]

On Wed, Feb 7, 2018 at 2:30 PM, Dafna Ron wrote: > Hi, > > We failed test 004_basic_sanity.vm_run in the upgrade from release suite. > the reason we failed to run the vm is that the host was filtered from > selection for vm. > > Please also notice other errors in the log relating to network sync

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 07-02-2018 ] [ 004_basic_sanity.vm_run ]

it did not. This patch did not run on CQ at all because its failing build-artifact jobs Those jobs need to be fixed and patch has to be re-triggered. The two jobs that failed are: http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/3151/

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 07-02-2018 ] [ 004_basic_sanity.vm_run ]

On Wed, Feb 7, 2018 at 3:22 PM, Dafna Ron wrote: > it did not. > This patch did not run on CQ at all because its failing build-artifact jobs > Those jobs need to be fixed and patch has to be re-triggered. > > The two jobs that failed are: > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 07-02-2018 ] [ 004_basic_sanity.vm_run ]

On Wed, Feb 7, 2018 at 5:02 PM Martin Perina wrote: > On Wed, Feb 7, 2018 at 3:22 PM, Dafna Ron wrote: > >> it did not. >> This patch did not run on CQ at all because its failing build-artifact >> jobs >> Those jobs need to be fixed and patch has to be re-triggered. >> >> The two jobs that faile

Re: [ovirt-devel] [vdsm] stable branch ovirt-4.2 created

We still do not have vdsm-4.30 in http://plain.resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/ . Since the current version there does not support 4.3 cluster level, we're constantly getting (EE-ManagedThreadFactory-engineScheduled-Thread-2) [239bce23] EVENT_ID: VDS_CLUSTER_VERSION_NO

Re: [ovirt-devel] [vdsm] stable branch ovirt-4.2 created

2018-02-08 8:17 GMT+01:00 Dan Kenigsberg : > We still do not have vdsm-4.30 in http://plain.resources.ovirt. > org/pub/ovirt-master-snapshot/rpm/el7/noarch/ . Since the current version > there does not support 4.3 cluster level, we're constantly getting > > (EE-ManagedThreadFactory-engineScheduled