On Wed, Dec 12, 2018 at 10:32 AM Eyal Edri <eedri@redhat.com> wrote:

On Tue, Dec 11, 2018 at 9:41 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Il giorno mar 11 dic 2018 alle ore 08:36 Dan Kenigsberg <danken@redhat.com> ha scritto:

On Tue, Dec 11, 2018 at 9:15 AM Dan Kenigsberg <danken@redhat.com> wrote:

On Tue, Dec 11, 2018 at 8:57 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Il giorno lun 10 dic 2018 alle ore 19:42 Dan Kenigsberg <danken@redhat.com> ha scritto:

On Mon, 10 Dec 2018, 19:17 Dominik Holler <dholler@redhat.com wrote:

On Mon, 10 Dec 2018 12:02:21 -0500
Greg Sheremeta <gshereme@redhat.com> wrote:

> On Mon, Dec 10, 2018 at 11:53 AM Sandro Bonazzola <sbonazzo@redhat.com>
> wrote:
>
> > hi, ovirt-system-tests_compat-4.2-suite-master is failing since November
> > 27 with following error:
> >
> > Error: Fault reason is "Operation Failed". Fault detail is "[Bond name 'bond_fancy0' does not follow naming criteria. For host compatibility version 4.3 or greater, custom bond names must begin with the prefix 'bond'  followed by 'a-z', 'A-Z', '0-9', or '_' characters. For host compatibility version 4.2 and lower, custom bond names must begin with the prefix 'bond' followed by a number.]". HTTP response code is 400.
> >
> >
> > I think that if the scope of the test is to check that 4.2 still works
> > with 4.3 engine, bond_fancy0 works for 4.3 but it's clearly not good for
> > 4.2 and the test needs a fix.
> > 
>

Gal, what is the most correct way to fix this?
Should the BOND_NAME derived from the versioning.cluster_version()?

as https://gerrit.ovirt.org/#/c/95866/ suggested for another reason

Is this covering engine 4.3 with cluster 4.2?

I cannot say that I understand these compat-* suite - we'd need to wait to Gal for that.

But I'm guessing that it would work. Let's see: https://jenkins.ovirt.org/job/ovirt-system-tests_manual/3736/console

This has failed early on deploy of ovirt-host. Any idea why nbdkit* and newer rpm are required but unavailable?

I guess it's the usual issue due to repository blacklisting / whitelisting used by OST.

Adding Galith and Dafna to check this.

I see the patch https://gerrit.ovirt.org/#/c/95866/ passed CI, does it fix the compat suites?

no idea, because compat suite is failing on missing packages.

can we merge it?

yes, please.