failed installation on ubuntu 13.04

[Kim Phillips]

This is on Ubuntu 13.04.

(a) when installing an instance in developer mode, lava-deployment-tool fails to start server automatically:

curl: (7) Failed connect to 127.0.0.1:8000; Connection refused

Presumably related to install_devmode not being found. See attached try-lava.script for details.

(b) documentation issues:

http://lava-deployment-tool.readthedocs.org/en/latest

under 'quickstart' says:

"A development server running on http://localhost:8000 (requires DEBUG set to true in /srv/lava/instances/testinstance/etc/lava-server/settings.conf):

whereas there is no information about non-development mode running on port 80.

(c) quickstart also says:

$ #NOTE: these are equivalent, one just doesn't require lava-deployment-tool
$ ./lava-deployment-tool manage testinstance runserver
$ /srv/lava/instances/testinstance/bin/lava-server manage runserver

so if one tries (a) and it fails as it does above, one naturally tries

./lava-deployment-tool manage testinstance runserver

which - in both development and non-development modes - starts a server on port 8000 that is unusable due to the 404 errors in the script leading to rendering too poor to use.

[Antonio Terceiro (terceiro)]

For me it just works. I would try on Ubuntu 12.04 which is at the moment the only supported platform.

I confirm the problem with `install_devmode: command not found`, but it is innofensive, just annoying. I am pushing a fix for that.

[Kim Phillips (kim-phillips)]

> For me it just works. I would try on Ubuntu 12.04 which is at the moment the only supported platform.

excerpt from [1]:

"Software Requirements
We currently recommmend using Ubuntu 12.04. This tool should work on Ubuntu versions 11.10 (Oneiric) and newer.
If you’d like to help us with other distributions feel free to contact us at linaro-validation (at) lists (dot) linaro (dot) org."

I filed this bug as a response to the invitation in the last sentence, and to improve the odds behind the word 'should' in the second sentence.

My current 'workaround' is to use the cambridge lab server, as - although slower - it's a better option than reverting my development machine's OS.

> I confirm the problem with `install_devmode: command not found`, but it is innofensive, just annoying. I am pushing a fix for that.

ok, thanks.

I still have a problem getting a job to go from 'submitted' state to 'started'. Based on IRC discussions, the scheduler daemon is not starting / empty scheduler log file.

Looking at the log again, could this be the problem?:

FATAL ERROR - The following SQL query failed: CREATE LANGUAGE plpgsql
The error was: language "plpgsql" already exists

Thanks,

Kim

[1] http://lava-deployment-tool.readthedocs.org/en/latest/index.html

[Antonio Terceiro (terceiro)]

On Thu, Aug 29, 2013 at 08:27:57PM -0000, Kim Phillips wrote:
> > For me it just works. I would try on Ubuntu 12.04 which is at the
> moment the only supported platform.
>
> excerpt from [1]:
>
> "Software Requirements
> We currently recommmend using Ubuntu 12.04. This tool should work on Ubuntu versions 11.10 (Oneiric) and newer.
> If you’d like to help us with other distributions feel free to contact us at linaro-validation (at) lists (dot) linaro (dot) org."
>
> I filed this bug as a response to the invitation in the last sentence,
> and to improve the odds behind the word 'should' in the second sentence.
>
> My current 'workaround' is to use the cambridge lab server, as -
> although slower - it's a better option than reverting my development
> machine's OS.

Sure, appreciated for trying.

The problem is, once you decide to use a platform where it "should" work
but is not supported, then you have to help us fix the problems. :-)

> > I confirm the problem with `install_devmode: command not found`, but
> it is innofensive, just annoying. I am pushing a fix for that.
>
> ok, thanks.
>
> I still have a problem getting a job to go from 'submitted' state to
> 'started'. Based on IRC discussions, the scheduler daemon is not
> starting / empty scheduler log file.
>
> Looking at the log again, could this be the problem?:
>
> FATAL ERROR - The following SQL query failed: CREATE LANGUAGE plpgsql
> The error was: language "plpgsql" already exists

I don't think so. I also get this error, and AFAICT it's also
innofensive.

So your problem is that the scheduler is not starting.
lava-deployment-tool will create upstart jobs for all of the components
that need to be started, maybe you can investigate whether there is some
problem with those upstart jobs?

Did you try `start lava` explicitly to see what happens?