On Sep 30, 2016 2:17 PM, "Nicolas Ecarnot" <nicolas@ecarnot.net> wrote:
>
> Le 30/09/2016 à 11:04, Nicolas Ecarnot a écrit :
>>
>> Hello,
>>
>> After having succeed in installing Lago and running a very basic oVirt
>> 3.6 on a 4G RAM system, I now start it from scratch on a new 64G real
>> server.
>>
>> Following the same path, but with some better knowledge, I'm facing some
>> similar issues, and not understanding how I coped with them previously :
>>
>> On the deploy stage, the VMs are trying to chat with the repository
>> server on the 8585 port.
>>
>> Digging around, I see that there should be an http server listening on
>> tcp/8585, as I can see here :
>>
>> /usr/lib/python2.7/site-packages/ovirtlago/constants.py
>>
>> LIBEXEC_DIR = '/usr/libexec/ovirtlago/'
>> DATA_DIR = '/usr/share/ovirtlago/'
>> ANSWER_FILES_DIR = os.path.join(DATA_DIR, 'config', 'answer-files')
>>
>> REPO_SERVER_PORT = 8585
>> ENGINE_USER = 'admin@internal'
>> ENGINE_PASSWORD = '123'
>>
>>
>> But the problem is that :
>>
>> root@serv-hv-dev02:/usr/lib/python2.7/site-packages/ovirtlago# LANG=C ls
>> -la /usr/libexec/ovirtlago/
>> ls: cannot access '/usr/libexec/ovirtlago/': No such file or directory
>>
>> And I get the same error on my previous tiny server.
>>
>> So, I have no clue how I got past it previously, and no idea how to
>> solve that.
>>
>> The only thing I changed between the two servers is that on the new one,
>> I installed :
>> yum install -y http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm
>>
>> when I installed release36 on the first one.
>>
>> This is no firewall error as stated below.
>> Some pieces seem to be missing.
>>
>
> Wow, I'm getting puzzled : Without changing anything, just destroying the deployed prefix, then running again, everything seem to have worked, though I've been doing the exact same thing maybe 7 times before.
>
> What
> is
> happening
> ?

When lago is executing a suite, it is making sure the web server is running and serving the repo. When it's not, if you wish to run it outside the suite, execute 'lago ovirt serve'.
Or you can enable the regular repos of the VMs and exclude the internal ones when calling yum commands.
Y.
>
> --
> Nicolas ECARNOT
> _______________________________________________
> lago-devel mailing list
> lago-devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/lago-devel