<p dir="ltr"></p>
<p dir="ltr">On Sep 30, 2016 2:17 PM, "Nicolas Ecarnot" <<a href="mailto:nicolas@ecarnot.net">nicolas@ecarnot.net</a>> wrote:<br>
><br>
> Le 30/09/2016 à 11:04, Nicolas Ecarnot a écrit :<br>
>><br>
>> Hello,<br>
>><br>
>> After having succeed in installing Lago and running a very basic oVirt<br>
>> 3.6 on a 4G RAM system, I now start it from scratch on a new 64G real<br>
>> server.<br>
>><br>
>> Following the same path, but with some better knowledge, I'm facing some<br>
>> similar issues, and not understanding how I coped with them previously :<br>
>><br>
>> On the deploy stage, the VMs are trying to chat with the repository<br>
>> server on the 8585 port.<br>
>><br>
>> Digging around, I see that there should be an http server listening on<br>
>> tcp/8585, as I can see here :<br>
>><br>
>> /usr/lib/python2.7/site-packages/ovirtlago/constants.py<br>
>><br>
>> LIBEXEC_DIR = '/usr/libexec/ovirtlago/'<br>
>> DATA_DIR = '/usr/share/ovirtlago/'<br>
>> ANSWER_FILES_DIR = os.path.join(DATA_DIR, 'config', 'answer-files')<br>
>><br>
>> REPO_SERVER_PORT = 8585<br>
>> ENGINE_USER = 'admin@internal'<br>
>> ENGINE_PASSWORD = '123'<br>
>><br>
>><br>
>> But the problem is that :<br>
>><br>
>> root@serv-hv-dev02:/usr/lib/python2.7/site-packages/ovirtlago# LANG=C ls<br>
>> -la /usr/libexec/ovirtlago/<br>
>> ls: cannot access '/usr/libexec/ovirtlago/': No such file or directory<br>
>><br>
>> And I get the same error on my previous tiny server.<br>
>><br>
>> So, I have no clue how I got past it previously, and no idea how to<br>
>> solve that.<br>
>><br>
>> The only thing I changed between the two servers is that on the new one,<br>
>> I installed :<br>
>> yum install -y <a href="http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm">http://resources.ovirt.org/pub/yum-repo/ovirt-release40.rpm</a><br>
>><br>
>> when I installed release36 on the first one.<br>
>><br>
>> This is no firewall error as stated below.<br>
>> Some pieces seem to be missing.<br>
>><br>
><br>
> 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.<br>
><br>
> What<br>
> is<br>
> happening<br>
> ?</p>
<p dir="ltr">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'. <br>
Or you can enable the regular repos of the VMs and exclude the internal ones when calling yum commands. <br>
Y.<br>
><br>
> -- <br>
> Nicolas ECARNOT<br>
> _______________________________________________<br>
> lago-devel mailing list<br>
> <a href="mailto:lago-devel@ovirt.org">lago-devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/lago-devel">http://lists.ovirt.org/mailman/listinfo/lago-devel</a><br></p>