Upgraded to foreman 1.2

[Eyal Edri]

i fixed the 2 slaves time problem.
salve 09 is running puppet and updated, slave 02 is updated with time
but doesn't have puppet installed.



----- Original Message -----
> From: "Eyal Edri" <eedri at redhat.com>
> To: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt at kohlvanwijngaarden.nl>
> Cc: infra at ovirt.org
> Sent: Wednesday, September 4, 2013 10:26:51 AM
> Subject: Re: Upgraded to foreman 1.2
> 
> i took down one ec2 slave - the f18vm02 iirc (from amazon interface),
> since we can handle without it and it costs money if its running (even as
> idle).
> 
> we'll probably remove more ec2 vms as we add more on rackspace.
> 
> e.
> 
> ----- Original Message -----
> > From: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt at kohlvanwijngaarden.nl>
> > To: "Eyal Edri" <eedri at redhat.com>
> > Cc: infra at ovirt.org
> > Sent: Tuesday, September 3, 2013 3:38:42 AM
> > Subject: Re: Upgraded to foreman 1.2
> > 
> > On Sun, Sep 01, 2013 at 12:53:55AM -0400, Eyal Edri wrote:
> > > didn't we deployed ntp on master + slaves via puppet to avoid it?
> > 
> > No, ntp patch is still in review. Main problem was that puppet simply
> > wasn't running. I ran all with noop to ensure nothing was lost, then
> > turned puppet on again. Now there's 2 hosts that need NTP badly (vm02
> > and vm09) and 1 EC2 slave that I can't reach and is also offline in
> > jenkins.
> > 
> > > ----- Original Message -----
> > > > From: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt at kohlvanwijngaarden.nl>
> > > > To: infra at ovirt.org
> > > > Sent: Sunday, September 1, 2013 1:03:56 AM
> > > > Subject: Upgraded to foreman 1.2
> > > > 
> > > > As the subject says, foreman was upgraded to 1.2.
> > > > 
> > > > While upgrading I noticed that our jenkins slaves are out of sync, so
> > > > I'm wondering if there's a specific reason for that.
> > 
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>