On Mon, Dec 10, 2018 at 11:53 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; 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. >

Not sure about the test, but yes, it needs to be bond[\d+] for 4.2. https://gerrit.ovirt.org/#/c/95163/

> > -- > > SANDRO BONAZZOLA > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://red.ht/sig> > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/PFJ2Y2PD4SI... >

On Mon, 10 Dec 2018, 19:17 Dominik Holler <dholler(a)redhat.com wrote: > On Mon, 10 Dec 2018 12:02:21 -0500 > Greg Sheremeta <gshereme(a)redhat.com&gt; wrote: > > > On Mon, Dec 10, 2018 at 11:53 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; > > 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

Or should we add an extra test which require_version(4,3) with the > fancy bond name? > > > Not sure about the test, but yes, it needs to be bond[\d+] for 4.2. > > https://gerrit.ovirt.org/#/c/95163/ > > > > Yes. > > > > > > > > > -- > > > > > > SANDRO BONAZZOLA > > > > > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > > > > > Red Hat EMEA <https://www.redhat.com/> > > > > > > sbonazzo(a)redhat.com > > > <https://red.ht/sig> > > > _______________________________________________ > > > Devel mailing list -- devel(a)ovirt.org > > > To unsubscribe send an email to devel-leave(a)ovirt.org > > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > > oVirt Code of Conduct: > > > https://www.ovirt.org/community/about/community-guidelines/ > > > List Archives: > > > > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/PFJ2Y2PD4SI... > > > > > > > > >

On Tue, Dec 11, 2018 at 8:57 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote: > > > Il giorno lun 10 dic 2018 alle ore 19:42 Dan Kenigsberg < > danken(a)redhat.com&gt; ha scritto: > >> >> >> On Mon, 10 Dec 2018, 19:17 Dominik Holler <dholler(a)redhat.com wrote: >> >>> On Mon, 10 Dec 2018 12:02:21 -0500 >>> Greg Sheremeta <gshereme(a)redhat.com&gt; wrote: >>> >>> > On Mon, Dec 10, 2018 at 11:53 AM Sandro Bonazzola < >>> sbonazzo(a)redhat.com&gt; >>> > 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

> > >> >> Or should we add an extra test which require_version(4,3) with the >>> fancy bond name? >>> >>> > Not sure about the test, but yes, it needs to be bond[\d+] for 4.2. >>> > https://gerrit.ovirt.org/#/c/95163/ >>> > >>> >>> Yes. >>> >>> > >>> > > >>> > > -- >>> > > >>> > > SANDRO BONAZZOLA >>> > > >>> > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> > > >>> > > Red Hat EMEA <https://www.redhat.com/> >>> > > >>> > > sbonazzo(a)redhat.com >>> > > <https://red.ht/sig> >>> > > _______________________________________________ >>> > > Devel mailing list -- devel(a)ovirt.org >>> > > To unsubscribe send an email to devel-leave(a)ovirt.org >>> > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> > > oVirt Code of Conduct: >>> > > https://www.ovirt.org/community/about/community-guidelines/ >>> > > List Archives: >>> > > >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/PFJ2Y2PD4SI... >>> > > >>> > >>> > >>> >>> > > -- > > SANDRO BONAZZOLA > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > <https://red.ht/sig> >

Il giorno mar 11 dic 2018 alle ore 08:36 Dan Kenigsberg <danken(a)redhat.com&gt; ha scritto: > > > On Tue, Dec 11, 2018 at 9:15 AM Dan Kenigsberg <danken(a)redhat.com&gt; wrote: > >> >> >> On Tue, Dec 11, 2018 at 8:57 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; >> wrote: >> >>> >>> >>> Il giorno lun 10 dic 2018 alle ore 19:42 Dan Kenigsberg < >>> danken(a)redhat.com&gt; ha scritto: >>> >>>> >>>> >>>> On Mon, 10 Dec 2018, 19:17 Dominik Holler <dholler(a)redhat.com wrote: >>>> >>>>> On Mon, 10 Dec 2018 12:02:21 -0500 >>>>> Greg Sheremeta <gshereme(a)redhat.com&gt; wrote: >>>>> >>>>> > On Mon, Dec 10, 2018 at 11:53 AM Sandro Bonazzola < >>>>> sbonazzo(a)redhat.com&gt; >>>>> > 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.

> > *07:19:43* + yum -y install ovirt-host*07:19:43* Error: Package: 1:virt-v2v-1.38.2-12.el7_6.1.x86_64 (alocalsync)*07:19:43* Requires: nbdkit-plugin-python2*07:19:43* Error: Package: elfutils-0.172-2.el7.x86_64 (alocalsync)*07:19:43* Requires: libdw.so.1(ELFUTILS_0.171)(64bit)*07:19:43* Error: Package: libvirt-client-4.5.0-10.el7_6.3.x86_64 (alocalsync)*07:19:43* Requires: libvirt-bash-completion = 4.5.0-10.el7_6.3*07:19:43* Error: Package: 1:openssl-1.0.2k-16.el7.x86_64 (alocalsync)*07:19:43* Requires: openssl-libs(x86-64) = 1:1.0.2k-16.el7*07:19:43* Installed: 1:openssl-libs-1.0.2k-12.el7.x86_64 (installed)*07:19:43* openssl-libs(x86-64) = 1:1.0.2k-12.el7*07:19:43* Error: Package: cryptsetup-2.0.3-3.el7.x86_64 (alocalsync)*07:19:43* Requires: cryptsetup-libs(x86-64) = 2.0.3-3.el7*07:19:43* Installed: cryptsetup-libs-1.7.4-4.el7.x86_64 (installed)*07:19:43* cryptsetup-libs(x86-64) = 1.7.4-4.el7*07:19:43* Error: Package: libsemanage-python-2.5-14.el7.x86_64 (alocalsync)*07:19:43* Requires: libsemanage = 2.5-14.el7*07:19:43* Installed: libsemanage-2.5-11.el7.x86_64 (installed)*07:19:43* libsemanage = 2.5-11.el7*07:19:43* Error: Package: libblockdev-crypto-2.18-3.el7.x86_64 (alocalsync)*07:19:43* Requires: libcryptsetup.so.12()(64bit)*07:19:43* Error: Package: kernel-3.10.0-957.1.3.el7.x86_64 (alocalsync)*07:19:43* Requires: linux-firmware >= 20180911-68*07:19:43* Available: linux-firmware-20180220-62.2.git6d51311.el7_5.noarch (alocalsync)*07:19:43* linux-firmware = 20180220-62.2.git6d51311.el7_5*07:19:43* Error: Package: setools-libs-3.3.8-4.el7.x86_64 (alocalsync)*07:19:43* Requires: libselinux >= 2.5-14.1*07:19:43* Installed: libselinux-2.5-12.el7.x86_64 (installed)*07:19:43* libselinux = 2.5-12.el7*07:19:43* Error: Package: 7:device-mapper-event-1.02.149-8.el7.x86_64 (alocalsync)*07:19:43* Requires: device-mapper = 7:1.02.149-8.el7*07:19:43* Installed: 7:device-mapper-1.02.146-4.el7.x86_64 (installed)*07:19:43* device-mapper = 7:1.02.146-4.el7*07:19:43* Error: kernel conflicts with selinux-policy-targeted-3.13.1-192.el7_5.3.noarch*07:19:43* Error: Package: setools-libs-3.3.8-4.el7.x86_64 (alocalsync)*07:19:43* Requires: libsepol >= 2.5-10*07:19:43* Installed: libsepol-2.5-8.1.el7.x86_64 (installed)*07:19:43* libsepol = 2.5-8.1.el7*07:19:43* Error: Package: elfutils-0.172-2.el7.x86_64 (alocalsync)*07:19:43* Requires: elfutils-libs(x86-64) = 0.172-2.el7*07:19:43* Installed: elfutils-libs-0.170-4.el7.x86_64 (installed)*07:19:43* elfutils-libs(x86-64) = 0.170-4.el7*07:19:43* Error: Package: glib-networking-2.56.1-1.el7.x86_64 (alocalsync)*07:19:43* Requires: glib2(x86-64) >= 2.55.1*07:19:43* Installed: glib2-2.54.2-2.el7.x86_64 (installed)*07:19:43* glib2(x86-64) = 2.54.2-2.el7*07:19:43* Error: Package: 1:librados2-10.2.5-4.el7.x86_64 (alocalsync)*07:19:43* Requires: libboost_random-mt.so.1.53.0()(64bit)*07:19:43* Error: Package: 1:librbd1-10.2.5-4.el7.x86_64 (alocalsync)*07:19:43* Requires: libboost_iostreams-mt.so.1.53.0()(64bit)*07:19:43* Error: Package: cryptsetup-2.0.3-3.el7.x86_64 (alocalsync)*07:19:43* Requires: libcryptsetup.so.12(CRYPTSETUP_2.0)(64bit)*07:19:43* Error: Package: libblockdev-crypto-2.18-3.el7.x86_64 (alocalsync)*07:19:43* Requires: libcryptsetup.so.12(CRYPTSETUP_2.0)(64bit)*07:19:43* Error: Package: policycoreutils-python-2.5-29.el7.x86_64 (alocalsync)*07:19:43* Requires: policycoreutils = 2.5-29.el7*07:19:43* Installed: policycoreutils-2.5-22.el7.x86_64 (installed)*07:19:43* policycoreutils = 2.5-22.el7*07:19:43* Error: Package: sos-3.6-11.el7.centos.noarch (alocalsync)*07:19:43* Requires: python2-futures*07:19:43* Error: Package: cryptsetup-2.0.3-3.el7.x86_64 (alocalsync)*07:19:43* Requires: libcryptsetup.so.12()(64bit)*07:19:43* Error: Package: rpm-build-4.11.3-35.el7.x86_64 (alocalsync)*07:19:43* Requires: rpm = 4.11.3-35.el7*07:19:43* Installed: rpm-4.11.3-32.el7.x86_64 (installed)*07:19:43* rpm = 4.11.3-32.el7*07:19:43* Error: Package: elfutils-0.172-2.el7.x86_64 (alocalsync)*07:19:43* Requires: elfutils-libelf(x86-64) = 0.172-2.el7*07:19:43* Installed: elfutils-libelf-0.170-4.el7.x86_64 (installed)*07:19:43* elfutils-libelf(x86-64) = 0.170-4.el7*07:19:43* Error: Package: 1:virt-v2v-1.38.2-12.el7_6.1.x86_64 (alocalsync)*07:19:43* Requires: nbdkit-plugin-vddk*07:19:43* Error: Package: 1:librbd1-10.2.5-4.el7.x86_64 (alocalsync)*07:19:43* Requires: libboost_random-mt.so.1.53.0()(64bit)*07:19:43* Error: Package: 1:virt-v2v-1.38.2-12.el7_6.1.x86_64 (alocalsync)*07:19:43* Requires: nbdkit*07:19:43* Error: Package: 1:librados2-10.2.5-4.el7.x86_64 (alocalsync)*07:19:43* Requires: libboost_iostreams-mt.so.1.53.0()(64bit) > > >> >> >>> >>> >>>> >>>> Or should we add an extra test which require_version(4,3) with the >>>>> fancy bond name? >>>>> >>>>> > Not sure about the test, but yes, it needs to be bond[\d+] for 4.2. >>>>> > https://gerrit.ovirt.org/#/c/95163/ >>>>> > >>>>> >>>>> Yes. >>>>> >>>>> > >>>>> > > >>>>> > > -- >>>>> > > >>>>> > > SANDRO BONAZZOLA >>>>> > > >>>>> > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>>>> > > >>>>> > > Red Hat EMEA <https://www.redhat.com/> >>>>> > > >>>>> > > sbonazzo(a)redhat.com >>>>> > > <https://red.ht/sig> >>>>> > > _______________________________________________ >>>>> > > Devel mailing list -- devel(a)ovirt.org >>>>> > > To unsubscribe send an email to devel-leave(a)ovirt.org >>>>> > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>>>> > > oVirt Code of Conduct: >>>>> > > https://www.ovirt.org/community/about/community-guidelines/ >>>>> > > List Archives: >>>>> > > >>>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/PFJ2Y2PD4SI... >>>>> > > >>>>> > >>>>> > >>>>> >>>>> >>> >>> -- >>> >>> SANDRO BONAZZOLA >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA <https://www.redhat.com/> >>> >>> sbonazzo(a)redhat.com >>> <https://red.ht/sig> >>> >> -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/FHAV7ZZMPSB...

On Wed, Dec 12, 2018 at 10:32 AM Eyal Edri <eedri(a)redhat.com&gt; wrote: > > > On Tue, Dec 11, 2018 at 9:41 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; > wrote: > >> >> >> Il giorno mar 11 dic 2018 alle ore 08:36 Dan Kenigsberg < >> danken(a)redhat.com&gt; ha scritto: >> >>> >>> >>> On Tue, Dec 11, 2018 at 9:15 AM Dan Kenigsberg <danken(a)redhat.com&gt; >>> wrote: >>> >>>> >>>> >>>> On Tue, Dec 11, 2018 at 8:57 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; >>>> wrote: >>>> >>>>> >>>>> >>>>> Il giorno lun 10 dic 2018 alle ore 19:42 Dan Kenigsberg < >>>>> danken(a)redhat.com&gt; ha scritto: >>>>> >>>>>> >>>>>> >>>>>> On Mon, 10 Dec 2018, 19:17 Dominik Holler <dholler(a)redhat.com wrote: >>>>>> >>>>>>> On Mon, 10 Dec 2018 12:02:21 -0500 >>>>>>> Greg Sheremeta <gshereme(a)redhat.com&gt; wrote: >>>>>>> >>>>>>> > On Mon, Dec 10, 2018 at 11:53 AM Sandro Bonazzola < >>>>>>> sbonazzo(a)redhat.com&gt; >>>>>>> > 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.