canonical-ci-engineering team mailing list archive

[Paul Larson <paul.larson@xxxxxxxxxxxxx>]

Yep, that's the plan. I think Francis was going to do it for some of the
systems he has most of the dealings with.


On Fri, Nov 8, 2013 at 9:49 AM, Evan Dandrea <evan.dandrea@xxxxxxxxxxxxx>wrote:

> On 8 November 2013 14:27, Paul Larson <paul.larson@xxxxxxxxxxxxx> wrote:
> > Here's the quick and dirty script I used on juifeng and
> magners-orchestra to
> > find hardcoded IPs in the logs:
> > find . -maxdepth 2 -iname config.xml -exec egrep
> > "[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+" {} \; -exec sh -c 'dirname {} sed -e
> > "s/^\.\///"' \;
> >
> > You'll want to run it from the /var/lib/jenkins/jobs directory, or change
> > the starting location for find.  I'm sure it could be made a lot nicer if
> > you so desire, but it gets the job done. The way it comes out is that it
> > will print the lines with something that look like an IP in them,
> followed
> > by the job name.
> >
> > I've also attached logs of this on both machines. As you can see, there
> are
> > a LOT of jobs on juifeng that would need to be fixed, including some that
> > specify IP addresses other than the usual 10.9x.x.x ones that we use. I
> know
> > some of these boxes have alternate IP addresses, but is there anything in
> > the configs for services (such as apache) that would require us to
> connect
> > at a specific address?
>
> Thanks Paul!
>
> While the unusual IP addresses are being investigated, can you update
> the jobs discovered by this script to make use of the new hostnames in
> place of the expected IPs, checking to make sure the hostname is
> reachable from that box and maps to the correct IP address?
>
> Who wants to volunteer to do this for the other servers?
>
> Can we get this done before Larry and Rick start disassembling
> equipment tonight?
>