jenkins network (?) failure on fc19 slave

[Eyal Edri]

----- Original Message -----
> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> To: "Eyal Edri" <eedri at redhat.com>, "ybronhei" <ybronhei at redhat.com>, "David Caro Estevez" <dcaroest at redhat.com>
> Cc: "Dan Kenigsberg" <danken at redhat.com>, infra at ovirt.org
> Sent: Tuesday, March 18, 2014 12:25:31 PM
> Subject: Re: jenkins network (?) failure on fc19 slave
> 
> Il 18/03/2014 11:06, Eyal Edri ha scritto:
> > 
> > 
> > ----- Original Message -----
> >> From: "ybronhei" <ybronhei at redhat.com>
> >> To: "Eyal Edri" <eedri at redhat.com>, "Dan Kenigsberg" <danken at redhat.com>
> >> Cc: infra at ovirt.org
> >> Sent: Tuesday, March 18, 2014 11:50:11 AM
> >> Subject: Re: jenkins network (?) failure on fc19 slave
> >>
> >> On 03/18/2014 11:09 AM, Eyal Edri wrote:
> >>>
> >>>
> >>> ----- Original Message -----
> >>>> From: "Dan Kenigsberg" <danken at redhat.com>
> >>>> To: "Francesco Romani" <fromani at redhat.com>
> >>>> Cc: infra at ovirt.org
> >>>> Sent: Tuesday, March 18, 2014 1:40:02 AM
> >>>> Subject: Re: jenkins network (?) failure on fc19 slave
> >>>>
> >>>> On Mon, Mar 17, 2014 at 04:42:31AM -0400, Francesco Romani wrote:
> >>>>> ----- Original Message -----
> >>>>>> From: "Francesco Romani" <fromani at redhat.com>
> >>>>>> To: infra at ovirt.org
> >>>>>> Sent: Monday, March 17, 2014 9:28:34 AM
> >>>>>> Subject: jenkins network (?) failure on fc19 slave
> >>>>>>
> >>>>>> Hi everyone
> >>>>>>
> >>>>>> I'm trying tu understand what makes jenkins tests fails on
> >>>>>>
> >>>>>> http://gerrit.ovirt.org/#/c/21792/8
> >>>>>>
> >>>>>> It seems the only error is the following
> >>>>>>
> >>>>>> http://jenkins.ovirt.org/job/vdsm_master_install_rpm_sanity_gerrit/label=fedora19/383/console
> >>>>>>
> >>>>>> any ideas about how to fix this? Code seems OK.
> >>>>>
> >>>>> Same for http://gerrit.ovirt.org/#/c/21790/7
> >>>>>
> >>>>> on the page
> >>>>> http://jenkins.ovirt.org/job/vdsm_master_install_rpm_sanity_gerrit/label=fedora19/384/console
> >>>>>
> >>>>> the root cause seems to be
> >>>>>
> >>>>> http://ovirt.org/releases/alpha/rpm/Fedora/19/repodata/repomd.xml:
> >>>>> [Errno
> >>>>> 14] HTTP Error 404 - Not Found
> >>>>
> >>>> It's *a* problem, but not *the* problem.
> >>>>
> >>>>      No package
> >>>>      /home/jenkins/workspace/vdsm_master_install_rpm_sanity_gerrit/label/fedora19/rpms/vdsm-4.13.*
> >>>>      available.
> >>>>
> >>>> *The* problem is that the job looks for 4.13.*, while we're deep into
> >>>> 4.14
> >>>> land. Puritans would curse me, but I would not mind f someone (hint
> >>>> hint)
> >>>> adds
> >>>
> >>> fixed. but still failing on missing gluster pkg:
> >>>
> >>>
> >>> ---> Package vdsm-python-zombiereaper.noarch 0:4.14.1-40.git12b7664.el6
> >>> will be installed
> >>> ---> Package vdsm-reg.noarch 0:4.14.1-40.git12b7664.el6 will be installed
> >>> ---> Package vdsm-tests.noarch 0:4.14.1-40.git12b7664.el6 will be
> >>> installed
> >>> ---> Package vdsm-xmlrpc.noarch 0:4.14.1-40.git12b7664.el6 will be
> >>> installed
> >>> ---> Package vdsm-yajsonrpc.noarch 0:4.14.1-40.git12b7664.el6 will be
> >>> installed
> >>> --> Finished Dependency Resolution
> >>> Error: Package: vdsm-4.14.1-40.git12b7664.el6.x86_64
> >>> (/vdsm-4.14.1-40.git12b7664.el6.x86_64)
> >>>             Requires: glusterfs >= 3.4.2
> >> change the gluster.repo to point :
> >>
> >> http://download.gluster.org/pub/gluster/glusterfs/3.4/3.4.2/EPEL.repo/epel-$releasever/noarch
> > 
> > Sandro - do you use these for repo closure on 3.4/master ?
> 
> no, we use latest:
> http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/epel-$releasever/noarch
> as in ovirt-release rpm.
> (maps to
> Added check-glusterfs-epel-noarch repo from
> http://download.gluster.org//pub/gluster/glusterfs/LATEST/EPEL.repo/epel-6.4/noarch
> )
> 
> 
> 
> > dcaro - we we manage these via puppet? i couldn't find it on the puppet
> > repo.

dcaro/ewoud - can you confirm / provide info on how we manage this repo (if at all) via puppet?

> > 
> >>
> >> guess it's set to 3.4.1
> >>
> >>>             Installed: glusterfs-3.4.1-3.el6.x86_64 (@glusterfs-epel)
> >>>                 glusterfs = 3.4.1-3.el6
> >>>             Available: glusterfs-3.4.0-8.el6.x86_64 (ovirt-stable)
> >>>                 glusterfs = 3.4.0-8.el6
> >>>             Available: glusterfs-3.4.0.36rhs-1.el6.x86_64 (base)
> >>>                 glusterfs = 3.4.0.36rhs-1.el6
> >>>             Available: glusterfs-3.4.0.57rhs-1.el6_5.x86_64 (updates)
> >>>                 glusterfs = 3.4.0.57rhs-1.el6_5
> >>>   You could try using --skip-broken to work around the problem
> >>>   You could try running: rpm -Va --nofiles --nodigest
> >>> Build step 'Execute shell' marked build as failure
> >>> Build step 'Groovy Postbuild' marked build as failure
> >>> Performing Post build task...
> >>>> a `make rpm-install` target, to simplify the installation of minimal
> >>>> working
> >>>> set of Vdsm rpms.
> >>>> _______________________________________________
> >>>> Infra mailing list
> >>>> Infra at ovirt.org
> >>>> http://lists.ovirt.org/mailman/listinfo/infra
> >>>>
> >>> _______________________________________________
> >>> Infra mailing list
> >>> Infra at ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/infra
> >>>
> >>
> >>
> >> --
> >> Yaniv Bronhaim.
> >>
> 
> 
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>