I think it was agreed to drop fcraw support from CI due to its instability, any need for this ticket or we can close it?

I think we have several issues:

mismatch for fcraw and fc28 - why not rename fcraw to fc28 - same name used in fedora build system?

We stick to the names of the package repos - rawhide is a moving target, always pointing to the latest. If you look at the repos you'lll see they are a mix of fc27 and fc28 packages atm.

So we need to:

remove fcraw from vdsm project
prepare vdsm automation for fcraw
enable fcraw when the build is stable

Yep, this is like porting vdsm to a new platform - dependencies should be taken care of first...

I fix the missing ovirt-imageio-common package, see:
https://gerrit.ovirt.org/#/c/87034/

But now it fails with mom:
nothing provides mom >= 0.5.8 needed by
vdsm-4.20.17-29.git89eb77538.fc28.x86_64

We are not ready yet for fcraw.
I disabled the job again, will give us more time until jenkins
configuration changes.

On Thu, Feb 1, 2018 at 6:22 PM Nir Soffer <nsoffer@redhat.com> wrote:

> We require the package:
>
> $ grep ovirt-imageio-common automation/check-patch.packages.fcraw
> ovirt-imageio-common
>
> Here are few failing builds, we have more:
>
>
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/95/consoleFull
>
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/97/consoleFull
>
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-fcraw-x86_64/96/consoleFull
>
> 00:03:25.311 =================================== FAILURES ===================================00:03:25.311 _________________________ test_import[vdsm.kvm2ovirt] __________________________00:03:25.312 00:03:25.312 name = 'vdsm.kvm2ovirt'00:03:25.312 00:03:25.312 @pytest.mark.parametrize("name", find_modules())00:03:25.312 def test_import(name):00:03:25.313 try:00:03:25.313 > importlib.import_module(name)00:03:25.313 00:03:25.313 check_imports.py:61: 00:03:25.313 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 00:03:25.314 /usr/lib64/python2.7/importlib/_init_.py:37: in import_module*00:03:25.314* _import_(name)00:03:25.314 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 00:03:25.315 00:03:25.315 from _future_ import absolute_import*00:03:25.315* 00:03:25.315 import argparse*00:03:25.315* from contextlib import contextmanager*00:03:25.315* import itertools*00:03:25.315* import sys*00:03:25.316* import threading*00:03:25.316* 00:03:25.316 > from ovirt_imageio_common import directio*00:03:25.316* E ImportError: No module named ovirt_imageio_common*00:03:25.316* 00:03:25.316 ../lib/vdsm/kvm2ovirt.py:28: ImportError*00:03:25.317* ========== 1 failed, 376 passed, 1 skipped, 1 xfailed in 3.25 seconds ==========
>
>
>
>

With the tested repo, the build fails with:

00:00:40.184 http://resources.ovirt.org/repos/ovirt/tested/master/rpm/fcraw/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found

We don't have fcraw, we have fc28:
http://resources.ovirt.org/repos/ovirt/tested/master/rpm/fc28/

And you can find ovirt-imageio-common there:
http://resources.ovirt.org/repos/ovirt/tested/master/rpm/fc28/noarch/ovirt-imageio-common-1.2.0-1.fc28.noarch.rpm

I think we have several issues:

• mismatch for fcraw and fc28 - why not rename fcraw to fc28 - same name used in fedora build system?

• the fcraw job was added to the vdsm project before vdsm automation was ready

• the fcraw job was disiabled in jenkins - each time jenkins is restarted or upgraded, the job is enabled again, and builds starts to break

So we need to:

• remove fcraw from vdsm project

• prepare vdsm automation for fcraw

• enable fcraw when the build is stable

The package comes from http://resources.ovirt.org.

Looking at vdsm automation:

$ for f in automation/check-patch.repos.fc*; do echo $f; cat $f; echo; done
automation/check-patch.repos.fc26
tested,http://resources.ovirt.org/repos/ovirt/tested/master/rpm/$distro
ovirt-snapshot-static,http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/$distro
ovirt-ci-tools,http://resources.ovirt.org/repos/ci-tools/$distro
lago,http://resources.ovirt.org/repos/lago/stable/0.0/rpm/$distro
virt-preview,http://fedorapeople.org/groups/virt/virt-preview/fedora-$releasever/$basearch

automation/check-patch.repos.fc27
tested,http://resources.ovirt.org/repos/ovirt/tested/master/rpm/$distro
virt-preview,http://fedorapeople.org/groups/virt/virt-preview/fedora-$releasever/$basearch

automation/check-patch.repos.fcraw
virt-preview,http://fedorapeople.org/groups/virt/virt-preview/fedora-$releasever/$basearch

Looks like our fcraw repos is wrong. Trying to use the fc27 version...

is there a repo configured where the package would come from? Can you try manually setting up the environment with mock_runner and check if the package is available?