maas-builds team mailing list archive

[Andres Rodriguez <andres.rodriguez@xxxxxxxxxxxxx>]

Hi Raphael,  Gavin,

Just looked into at and there's a few issues:

http://162.213.35.104:8080/job/maas-utopic-trunk/576/console
http://162.213.35.104:8080/job/maas-utopic-trunk/576/artifact/results/artifacts/maas-logs/var/log/maas/regiond.log
http://162.213.35.104:8080/job/maas-utopic-trunk/576/artifact/results/artifacts/maas-logs/var/log/maas/clusterd.log

So, the last issue seems liek the test does not wait long enough for the
images to be present, however, that's caused for other things (see
regiond.log):

1. OSError: [Errno 13] Permission denied: '/etc/maas/regiond.conf'
2. django.db.utils.OperationalError: fe_sendauth: no password supplied
3. exceptions.OSError: [Errno 13] Permission denied:
'/etc/maas/clusterd.conf'

So, by the looks of it, it seems that after the installation goes through
the regiond.conf is not with the correct permissions. Packaging itself does
not configure nor changes the permissions. So questions are:
1. Why are the daemons not creating the configs with correct permissions?
2. What causes the permissions to be changed correctly later on?

Then, after the daemon successfully loads regiond.conf, no password is
supplied to the DB:
3. So, why does the daemon seem not to have the DB password if it was
supposed to be set?

Last, but not least, the regiond is trying to access cluster.conf:
4. Why is the region daemon trying to access cluster.conf ? This should not
be happening at all.

Gavin, can you please look at the above and fix asap?

Thanks.

On Fri, Jul 3, 2015 at 4:35 AM, Raphaël Badin <raphael.badin@xxxxxxxxxxxxx>
wrote:

> Confirmed, a run with upstream/tip and packaging/408 passes.
>
> http://162.213.35.104:8080/job/maas-utopic-trunk-manual/514/console
>
>
> On 07/03/2015 10:14 AM, Raphaël Badin wrote:
>
>> CI is broken since run 566 (567 568 also broke the same way, indicating
>> the breakage is genuine).
>>
>> Run 565: passing
>> Upstream revision: 4064
>> Packaging revision: 408
>>
>> Run 566: broken
>> Upstream revision: 4064
>> Packaging revision: 409
>>
>> I suspect packaging revision 409 is the problem… Gavin, Andres, any idea
>> what the problem might be?
>>
>> Revision 409 is "Use new local configuration support for the cluster."
>> and the CI breakage is that the cluster never connect to the region.
>>
>> The logs are full or stacktraces:
>>
>>
>> http://162.213.35.104:8080/job/maas-utopic-trunk/566/artifact/results/artifacts/maas-logs/var/log/maas/regiond.log
>>
>>
>>
>> http://162.213.35.104:8080/job/maas-utopic-trunk/566/artifact/results/artifacts/maas-logs/var/log/maas/clusterd.log
>>
>>


-- 
Andres Rodriguez
Engineering Manager, MAAS & OIL DevOps
Canonical USA, Inc.