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_NOT_SUPPORTED(154), Host lago-network-suite-master-host-0 is compatible with versions (3.6,4.0,4.1,4.2) and cannot join Cluster Default which is set to version 4.3. assistance to straighten this up is most welcome. On Wed, Feb 7, 2018 at 2:06 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
2018-02-07 12:58 GMT+01:00 Dan Kenigsberg <danken@redhat.com>:
On 02/07/2018 08:46 AM, Dan Kenigsberg wrote:
On Tue, Feb 6, 2018 at 10:28 PM, Francesco Romani <fromani@redhat.com> 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/#/c/87070/
2. branched out ovirt-4.2 from git master
3. merged https://gerrit.ovirt.org/#/c/87181/ to add support for 4.3 level
4. createed and pushed the tag v4.30.0 from master, to make sure the version number is greater of the stable versions, and to (somehow :)) align with oVirt versioning
5. tested make dist/make rpm on both new branch ovirt-4.2 and master, both looks good and use the right version
Maintainers, please check it looks right for you before merging any new patch to master branch.
Please let me know about any issue! Thank you Francesco (and Sandro).
Any idea why http://plain.resources.ovirt.o rg/pub/ovirt-4.2-snapshot/rpm/el7/noarch/ still does not hold any vdsm-4.20 , and http://plain.resources.ovirt.org/pub/ovirt-master-snapshot/r
On Wed, Feb 7, 2018 at 10:14 AM, Francesco Romani <fromani@redhat.com> wrote: pm/el7/noarch/
does not have the new vdsm-4.30 ?
?
Uhm, maybe related to CQ (Change Queue), because git state looks ok, one data point: http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-on- demand-el7-x86_64/772/artifact/exported-artifacts/ built from this patch https://gerrit.ovirt.org/#/c/87213/
in turn based on top of current master
Maybe Barak knows? Making GQ tick is the intention of the jenkins patch, isn't it?
I think it may be caused by a failure trying to build on fcraw for s390x. I removed the failing jobs until we fix the issue on jenkins side.
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>