[ovirt-devel] [ovirt-system-tests] ssh to an oVirt VM in Lago

[Valentina Makarova]

Thank you all for your advice!

Now I can ping 192.168.201.213 succesfully, I can get SPICE-connection.
And I want to know your opinion about way to get connection via some test.

I may use a pakamiko only like this :
https://github.com/vmakarova/ovirt-system-tests/commit/
3e9e5ce697da7e0567aaad8397fa886469bc5ae3
Lago also use pakamiko, so there is not new dependencies.

Is this a good way?

Or, may something using lago be better?
For example using lago.ssh.get_ssh_client() as a wrapper like this:
https://github.com/vmakarova/ovirt-system-tests/commit/
855dbdf379730d55daf51851052d71daa45d9a09

Or Is there better way to do this?


And few more questions about tests and ovirt network.

1) This address of vm0 192.168.201.213. What is this addres? Why it is ip
of 'vm0'?
What gave it to vm0 and how the user may to understand that the address
would be that?
There is not this ip in  virsh net-list  and net-dumpxml

2) In test vm_run (004_basic_sanity) we configure interface eth0 on vm0
with ip 192.168.200.200.
But this interface is unreacheble from engine-host.And when I ask vm0 'ip
address' via ssh,
there is not interface eth1 there. What for does test add it, if it does
not work? Should it work?
And why test finished successful if eth0 was not configured according a
start_params?


Sincerely,
Valentina Makarova

2017-05-31 23:06 GMT+03:00 Yaniv Kaul <ykaul at redhat.com>:

>
>
> On Wed, May 31, 2017 at 11:10 AM, Milan Zamazal <mzamazal at redhat.com>
> wrote:
>
>> Nadav Goldin <ngoldin at redhat.com> writes:
>>
>> > I would start first by making sure the VM is booting properly using
>> > SPICE from the GUI, when the tests ends, you should be able to log
>> > into the Engine GUI(run 'lago ovirt status' inside your deployment
>> > directory to get the link, the directory should be something like
>> > ovirt-system-tests/deployment-SUITE-NAME). Then in the GUI, start the
>> > VM and click on 'console', the username/password should be
>> > root/123456.
>>
>> It's actually "cirros"/"cubswin:)".
>>
>> > If it is booting properly - first would be to check if it even gets an
>> > IP(my guess is not - I'm not even sure if dhcp is running in that
>> > layer, maybe we should setup one..).
>>
>> Yes, it should get everything, it's possible to log in there via ssh on
>> my setup.
>>
>> Valentina Makarova <makarovavs07 at gmail.com> writes:
>>
>> > And a second question is about ssh to this vm connection from my
>> laptop's
>> > console.
>> > According run_vm test from  004_basic_sanity.py (
>> > https://github.com/oVirt/ovirt-system-tests/blob/master/
>> basic-suite-master/test-scenarios/004_basic_sanity.py#L385
>> > ) vm0 should contain interface with ip 192.168.200.200, but ping this
>> from
>> > engine (192.168.200.4) Destination Host Unreachable. And 'ping vm0'
>> defined
>> > vm0 as 192.168.201.213 and also couldn't reach vm0.
>>
>> 192.168.201.213 should be working, I can both ping and ssh the
>> corresponding IP on my computer.  Do you run Lago directly on your
>> computer or in a VM?  If you run it on your computer, can't it conflict
>> with another network in your environment?  Maybe checking from inside
>> the VM as described by Nadav can help.
>>
>
> We can add a fake entry in Lago init file just as we do for hosted-engine.
> Most importantly, it'll create a MAC to IP address mapping in libvirt's
> DHCP.
> Of course, then we need to use this MAC.
> I somehow remember doing this at some point but never completing the task
> :(
> Y.
>
>
>>
>> > And in webadmin (https://engine/ovirt-engine/webadmin/#vms) IP Address
>> > field is empty.
>>
>> This is OK, I think ovirt-guest-agent must be installed and running in
>> the VM to report the IP address.  If it is not then the information is
>> missing in the UI but that doesn't mean the network is not working.
>>
>> Regards,
>> Milan
>> _______________________________________________
>> Devel mailing list
>> Devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20170606/5801d35d/attachment-0001.html>