On Mon, Feb 27, 2017 at 4:03 PM, Eyal Edri <eedri(a)redhat.com> wrote:
On Fri, Feb 24, 2017 at 2:49 PM, Martin Perina <mperina(a)redhat.com> wrote:
> On Fri, Feb 24, 2017 at 11:58 AM, Sahina Bose <sabose(a)redhat.com> wrote:
>> Hi all,
>> The ovirt-engine 4.1 appliance has the Default cluster set to 4.2 and
>> the hyperconverged OST tests fail here as the 4.1 host cannot be added to
>> cluster. (CLUSTER_VERSION_INCOMPATIBLE_WITH_CLUSTER)
>> The appliance is from http://resources.ovirt.org/rep
> This is the tested master repository, so it should contain master code
> where 4.2 cluster level is already default. So probably only
> ovirt-engine-appliance version has not yet been bumped to 4.2 ...
> I'm just wondering why we don't have any ovirt-engine-appliance in
> latest 4.1 tested repo:
We can't publish appliance to tested repo if its not tested/verified.
The correct thing to do is to make appliance build from tested repo and
then run the HE/HC suite and only if it pass publish it to verified tested
I don't think we're there yet, but there is some progress.
Maybe Sandro can update on current status.
No update yet. We're out of capacity to handle more automation until 4.0.7,
and 4.1.1 are out.
>> Has the default cluster level been changed in an updated appliance?
>> Test results at http://jenkins.ovirt.org/view/oVirt
>> Devel mailing list
> Devel mailing list
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018 <+972%209-769-2018>
irc: eedri (on #tlv #rhev-dev #rhev-integ)
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com