Re: EL6.5 availability on slaves
That's what I meant with downtime. Just so the Jenkins master doesn't
try to use it while upgrading.
I can do it the upgrade, but do we announce it?
Not sure about the labels though. Won't you need to walk through all the
job configurations to see if it's used anywhere?
On Tue, Dec 03, 2013 at 08:47:52AM -0500, Eyal Edri wrote:
Not sure it needs a specific downtime, you can just take off one
slave at a time.
Personally I'm not sure i'll have to do that soon, so anyone from infra can take
lead on it.
Eyal.
----- Original Message -----
> From: "Ewoud Kohl van Wijngaarden"
<ewoud+ovirt(a)kohlvanwijngaarden.nl>
> To: infra(a)ovirt.org
> Sent: Monday, December 2, 2013 8:50:21 PM
> Subject: Re: EL6.5 availability on slaves
>
> On Mon, Dec 02, 2013 at 06:20:53PM +0000, Dan Kenigsberg wrote:
> > Finally,
> >
http://mirror.centos.org/centos-6/6.5/os/x86_64/Packages/libvirt-0.10.2-2...
> > is available to users so I fell comfortable enough to pull
> > http://gerrit.ovirt.org/19545
> >
> > But this causes failures like
> >
http://jenkins.ovirt.org/job/vdsm_master_install_rpm_sanity_gerrit/label=...
> > as our guest is not yet updated.
> >
> > Would you rename centos64 slave to "centos6" and update its content
to
> > el6.5?
> >
> > Other patches are pending on that (lvm2, iscsi-initiator, maybe others).
>
> I was thinking the exact same thing about updates. Can we just schedule
> downtime in jenkins, yum update, reboot and end the downtime?
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>