Re: jenkins really broken right now
On Wed, Mar 28, 2012, Alexander Sack wrote: > The builds went through _after_ i disabled the git proxy > setting. Before that kernel_cloud builds failed after we shut down the > old instance. Right; and the proxy setting was also bogusly pointing at the internal EC2 IP which is why it kept pointing at the old instance; when we set it up again we should use ci.linaro.org as hostname for the proxy, this will resolve to the internal EC2 IP when queried from within EC2. -- Loïc Minier ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: jenkins really broken right now
On Wed, 28 Mar 2012 13:05:21 +0300 Paul Sokolovsky wrote: > Hello, > > On Tue, 27 Mar 2012 17:06:53 -0600 > John Rigby wrote: > > > On Tue, Mar 27, 2012 at 4:55 PM, Loïc Minier > > wrote: > > > On Tue, Mar 27, 2012, John Rigby wrote: > > >> Looks like initial git clones always fail. I tried a simple job > > >> that just trys to run git and it fails. > > > > > > Alexander noticed too; new ci.linaro.org setup was launching jobs > > > which were actually pointing at old ci.linaro.org setup as web > > > proxy. When the old instance was shut down, it exposed the > > > problem. Problem is that new instance doesn't have squid > > > installed/configured. We need to restore the config and any other > > > missing bits. > > > > > > > My jobs seem to be working again, I guess without the proxy for now > > but working none the less. Thanks to all for fixing this. > [] > But well, new instance couldn't automatically use squid on the old - > old had his IP/domain name changed, so stale config wouldn't explain > it. I also thought that Loic might have restarted the old instance, > bit it wasn't, so doesn't explain why builds went thru. So, maybe > it's not squid after all. We'll be looking into the issue immediately. Ok, it turns out that the cache was accessed as internal EC2 IP, "http://ip-10-195-115-143.ec2.internal:3128";. So, mystery off, the issue fully understood and confirmed. -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: jenkins really broken right now
On Wed, Mar 28, 2012 at 01:05:21PM +0300, Paul Sokolovsky wrote: > Hello, > > On Tue, 27 Mar 2012 17:06:53 -0600 > John Rigby wrote: > > > On Tue, Mar 27, 2012 at 4:55 PM, Loïc Minier > > wrote: > > > On Tue, Mar 27, 2012, John Rigby wrote: > > >> Looks like initial git clones always fail. I tried a simple job > > >> that just trys to run git and it fails. > > > > > > Alexander noticed too; new ci.linaro.org setup was launching jobs > > > which were actually pointing at old ci.linaro.org setup as web > > > proxy. When the old instance was shut down, it exposed the > > > problem. Problem is that new instance doesn't have squid > > > installed/configured. We need to restore the config and any other > > > missing bits. > > > > > > > My jobs seem to be working again, I guess without the proxy for now > > but working none the less. Thanks to all for fixing this. > > > Oh my, that's why I wanted Deepti to have another look before stopping > the old instance. But as she went on a leave, I had a look myself, > noted the squid difference and explicitly wrote it off as not in use. > But well, new instance couldn't automatically use squid on the old - > old had his IP/domain name changed, so stale config wouldn't explain > it. I also thought that Loic might have restarted the old instance, bit > it wasn't, so doesn't explain why builds went thru. So, maybe it's not > squid after all. We'll be looking into the issue immediately. The builds went through _after_ i disabled the git proxy setting. Before that kernel_cloud builds failed after we shut down the old instance. -- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: jenkins really broken right now
Hello, On Tue, 27 Mar 2012 17:06:53 -0600 John Rigby wrote: > On Tue, Mar 27, 2012 at 4:55 PM, Loïc Minier > wrote: > > On Tue, Mar 27, 2012, John Rigby wrote: > >> Looks like initial git clones always fail. I tried a simple job > >> that just trys to run git and it fails. > > > > Alexander noticed too; new ci.linaro.org setup was launching jobs > > which were actually pointing at old ci.linaro.org setup as web > > proxy. When the old instance was shut down, it exposed the > > problem. Problem is that new instance doesn't have squid > > installed/configured. We need to restore the config and any other > > missing bits. > > > > My jobs seem to be working again, I guess without the proxy for now > but working none the less. Thanks to all for fixing this. Oh my, that's why I wanted Deepti to have another look before stopping the old instance. But as she went on a leave, I had a look myself, noted the squid difference and explicitly wrote it off as not in use. But well, new instance couldn't automatically use squid on the old - old had his IP/domain name changed, so stale config wouldn't explain it. I also thought that Loic might have restarted the old instance, bit it wasn't, so doesn't explain why builds went thru. So, maybe it's not squid after all. We'll be looking into the issue immediately. -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: jenkins really broken right now
On Tue, Mar 27, 2012 at 4:55 PM, Loïc Minier wrote: > On Tue, Mar 27, 2012, John Rigby wrote: >> Looks like initial git clones always fail. I tried a simple job that >> just trys to run git and it fails. > > Alexander noticed too; new ci.linaro.org setup was launching jobs which > were actually pointing at old ci.linaro.org setup as web proxy. When > the old instance was shut down, it exposed the problem. Problem is > that new instance doesn't have squid installed/configured. We need to > restore the config and any other missing bits. > My jobs seem to be working again, I guess without the proxy for now but working none the less. Thanks to all for fixing this. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: jenkins really broken right now
On Tue, Mar 27, 2012, John Rigby wrote: > Looks like initial git clones always fail. I tried a simple job that > just trys to run git and it fails. Alexander noticed too; new ci.linaro.org setup was launching jobs which were actually pointing at old ci.linaro.org setup as web proxy. When the old instance was shut down, it exposed the problem. Problem is that new instance doesn't have squid installed/configured. We need to restore the config and any other missing bits. -- Loïc Minier ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
jenkins really broken right now
Looks like initial git clones always fail. I tried a simple job that just trys to run git and it fails. ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
