- lago-devel - oVirt List Archives

yapf and flake8 are running against each other - and my patch is in the middle.
by Yaniv Kaul 22 Nov '16

22 Nov '16

Seems like there's a disagreement between yapf and flake on styling. See http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/362/console and http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/361/console : *7:24:57* scripts/check_style.sh*07:24:57* yapf 0.7.1*07:25:59* --- lago/templates.py (original)*07:25:59* +++ lago/templates.py (reformatted)*07:25:59* @@ -260,7 +260,6 @@*07:25:59* finally:*07:25:59* response.close()*07:25:59* *07:25:59* -*07:25:59* #: Registry for template providers*07:25:59* _PROVIDERS = {*07:25:59* 'file': FileSystemTemplateProvider,*07:25:59* Yapf failed, make sure to run:*07:25:59* yapf --style .style.yapf --in-place --recursive . vs. *07:13:48* PYTHONPATH=/home/jenkins/workspace/lago_master_check-patch-el7-x86_64/lago python /home/jenkins/workspace/lago_master_check-patch-el7-x86_64/lago/tests/venv/bin/flake8*07:13:52* ./lago/templates.py:264:1: E305 expected 2 blank lines after class or function definition, found 1*07:13:52* make: *** [check-local] Error 1 Come on... I just want my patch in, it has nothing to do with this supposed breakage. Y.

2 2

Help debugging HC test failures
by Sahina Bose 09 Nov '16

09 Nov '16

Hi, I need some help/pointers to solve the issues I'm running into while running the gluster HC tests - https://gerrit.ovirt.org/57283 1. Once I run the suite, initialization completes successfully, but further tests fail. Engine is running as per "hosted-engine --vm-status" on the first host (lago_basic_suite_hc_host0) and I can ping the engine from the host running the test File "/usr/lib/python2.7/site-packages/ovirtlago/virt.py", line 189, in get_api return self.get_api_v3() File "/usr/lib/python2.7/site-packages/ovirtlago/virt.py", line 195, in get_api_v3 self._api_v3 = self._get_api(api_ver=3) File "/usr/lib/python2.7/site-packages/ovirtlago/virt.py", line 180, in _get_api raise RuntimeError('Failed to connect to the engine') RuntimeError: Failed to connect to the engine Which logs should I look at to debug this issue? 2. Cannot access the web url of engine: I've setup tunnelling: ssh -L hc-engine.lago.local:8443:hc-engine.lago.local:443 root(a)rhsdev-grafton1.lab.eng.blr.redhat.com But continue getting the error: The client is not authorized to request an authorization. It's required to access the system using FQDN. 3. Once the vms are left running for a while, connectivity is lost between the vms and cannot connect to some of the VMs via lago shell . [root@lago_basic_suite_hc_host0 ~]# ping lago_basic_suite_hc_host1 PING lago_basic_suite_hc_host1 (192.168.200.2) 56(84) bytes of data. >From lago-basic-suite-hc-host0.lago.local (192.168.200.3) icmp_seq=1 Destination Host Unreachable Looks like issue with network in VM from console of VM deployment-basic_suite_hc]# virsh console a2051d60-lago_basic_suite_hc_host1 Connected to domain a2051d60-lago_basic_suite_hc_host1 [root@lago_basic_suite_hc_host1 ~]# ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 54:52:c0:a8:c8:02 brd ff:ff:ff:ff:ff:ff inet6 fe80::5652:c0ff:fea8:c802/64 scope link valid_lft forever preferred_lft forever Any pointers are much appreciated. thanks sahina

4 7

New Lago release - 0.27
by Nadav Goldin 02 Nov '16

02 Nov '16

Hey all, New Lago version is out - v0.27, included in this release: fixes for a few bugs, improvements to the 'ovirt' verb, packaging fixes and some new docs. Also, a new verb was added: 'generate-config'[1], this verb allows to print the current loaded configuration lago is using. It also introduced a few changes to lago.conf file, so if you are using /etc/lago.d/lago.conf, please make sure you read[1] before upgrading. Specifically these parameters were changed in lago.conf: 1. 'default_ssh_user', changed to: 'ssh_user', no change to the default value. 2. 'default_ssh_password, changed to: 'ssh_password', no change to the default value. 3. 'template_default_repo', changed to: 'template_repo_name'(same as the existing CLI), no change to value. 4. 'template_*' parameters were moved under the [init] section in lago.conf. 5. lago.conf default location changed to /etc/lago/lago.conf(when upgrading via yum or dnf, it will be automatically be installed there) To upgrade using yum/dnf simply run: yum update lago If you find any bugs, or have request for new features please feel free to open an issue in the GitHub page[2]. Also we started working with GitHub's integrated Kanban board[3]. The updated docs can be found here[4], and the full change log here[5]. Thanks everyone who contributed to this release! Enjoy, Nadav. [1] http://lago.readthedocs.io/en/0.27/Configuration.html [2] https://github.com/lago-project/lago/issues [3] https://github.com/lago-project/lago/projects/1 [4] https://lago.readthedocs.org [5] https://github.com/lago-project/lago/milestone/2?closed=1

1 0

Re: [lago-devel] Lago - Installation help needed
by Yaniv Kaul 15 Oct '16

15 Oct '16

Adding the Lago devel mailing list. The download is the reposync phase - which seems to be OK, but then the connection means that for some reason Lago is not serving those RPMs (8585 is the port it should be listening to). Can you share some logs? TIA, Y. On Wed, Sep 21, 2016 at 4:25 PM, Nicolas Ecarnot <nicolas(a)ecarnot.net> wrote: > Hello Yaniv, > > Following your recommendation, I install a new bare metal host, installed > F24, then followed the lago.readthedoc web site. > > When running ./run_suite.sh basic_suite_3.6 , things seems to go right > (downloading...) for a while, then begin some errors about accessing > 192.168.200.1:8585 > > May you tell me where would be the best place to ask some help about Lago > ? (IRC, mailing list, e-mail... ?) > > Best regards, > > -- > Nicolas ECARNOT >

4 24

New Lago release - 0.26
by Gal Ben Haim 10 Oct '16

10 Oct '16

Hey All, Lago 0.26 is out, the key changes in this version are: - Improved the documentation. - Added support for oVirt v4 api. - Changes that are required for Python and Debian packaging for Lago. Docs: http://lago.readthedocs.io/en/0.26/# Here is the full change log: * Mon Oct 10 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.26.0 f070ef82: Merge pull request #338 from mykaul/prep_for_v4_ovirt_api c5dfc9c4: Prep for oVirt v4 API * Sun Oct 09 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.25.9 640247d8: Merge pull request #293 from irosenzw/change_wait_for_ssh 273df672: Changing the ssh connection waiting method. * Thu Oct 06 2016 Yaniv Kaul <ykaul(a)redhat.com> - 0.25.8 4fdd8462: Merge pull request #339 from mykaul/continue_on_failures 8ba99721: Merge branch 'master' into continue_on_failures bfea3cc4: Continue testing on test failures. * Sun Oct 02 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.25.7 6152127f: Merge pull request #337 from eedri/docs c66cd924: restore meaningfull README file 4573c7e9: add also link to main README.rst file 24c6afcb: added missing libvirt & user permissions info * Thu Sep 29 2016 Eyal Edri <eedri(a)redhat.com> - 0.25.6 aa093270: Merge pull request #336 from eedri/docs 24c6afcb: added missing libvirt & user permissions info 4d20490f: removed selinux section, seems to be working with enforcing also * Thu Sep 29 2016 Eyal Edri <eedri(a)redhat.com> - 0.25.5 95bdb652: Merge pull request #330 from eedri/docs eed1fa98: Adding debugging and troubleshooting section fc617149: Merge branch 'master' into docs 26692e59: Moving over get_prefixed_name() to ovirtlago/testlib 68137950: Merge branch 'master' into docs 1e63cd89: fixing typos 327f0b72: Refactoring Lago docs * Wed Sep 28 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.25.4 52b87825: Merge pull request #332 from mykaul/get_prefixed_name 2447e5ab: Merge branch 'master' into get_prefixed_name d255b2fc: Moving over get_prefixed_name() to ovirtlago/testlib * Wed Sep 28 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.25.3 ef90a75e: Merge pull request #296 from pilou-/search_for_kvm_executable_too 8e5d752c: Ask libvirt for path of kvm executable c5158fd9: Don't run flakes on .eggs directory * Tue Sep 27 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.25.2 9e48c95b: Merge pull request #329 from mykaul/switch_qemu_ga_with_agent 627fb675: Replace the order between qemu-ga and qemu-guest-agent. * Mon Sep 26 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.25.1 51158c7c: Merge pull request #327 from lago-project/adding_requirements.txt 2888b6ea: Added requirements.txt Gal Ben Haim gbenhaim(a)redhat.com RHEV DevOps

1 0

Re: [lago-devel] Lago - Installation help needed
by Nicolas Ecarnot 29 Sep '16

29 Sep '16

Le 26/09/2016 à 12:04, Yedidyah Bar David a écrit : > On Mon, Sep 26, 2016 at 1:02 PM, Nicolas Ecarnot <nicolas(a)ecarnot.net> wrote: >> Le 26/09/2016 à 12:00, Yedidyah Bar David a écrit : >>> >>> On Mon, Sep 26, 2016 at 12:36 PM, Nicolas Ecarnot <nicolas(a)ecarnot.net> >>> wrote: >>>> >>>> Le 26/09/2016 à 10:55, Yedidyah Bar David a écrit : >>>>> >>>>> >>>>> So we need engine logs to know more. >>>>> >>>>> If none were generated, it might have failed too early. >>>>> >>>>> Please check system logs - /var/log/messages, journalctl, etc. Thanks. >>>> >>>> >>>> >>>> Just to be sure : are you speaking about the log files on the bare-metal >>>> server, or the virtual hosts (engine)? >>> >>> >>> I referred to the engine vm. In principle both might be >>> interesting/relevant. >>> >>>> >>>> >>>> If this is the engine, I already provided the only file I got (and I also >>>> double-checked its /var/log/message, with no interesting info). >>> >>> >>> Perhaps journalctl output? >> >> >> Engine is centos 6, so no systemd at this time... > > OK. Can you try starting the service manually and see if you get anything > in any log? You can try getting more debug info using e.g.: > > https://bugzilla.redhat.com/show_bug.cgi?id=1230165#c8 OK. I read this BZ, and I also tried to launch a run using basic_suite_4.0 The results were quite different, as I see no more memory issues. Actually, it looks like all the 3 VMs are deployed OK (engine, host0 and host1). Then the tests about the engine are OK. Then I only have an error in post-001_initialize_engine.py But I can not find any detail : @ Collect artifacts: # [Thread-1] lago_basic_suite_4_0_host0: # [Thread-2] lago_basic_suite_4_0_host1: # [Thread-3] lago_basic_suite_4_0_engine: No handlers could be found for logger "paramiko.transport" # [Thread-3] lago_basic_suite_4_0_engine: Success (in 0:01:07) # [Thread-1] lago_basic_suite_4_0_host0: ERROR (in 0:02:18) # [Thread-2] lago_basic_suite_4_0_host1: ERROR (in 0:02:18) (nothing more). The script is not stopping there, and keeps going until 002_bootstrap.py : # add_dc: # add_dc: Success (in 0:00:03) # add_dc_quota: # add_dc_quota: Success (in 0:00:02) # add_cluster: # add_cluster: Success (in 0:00:01) # add_hosts: * Collect artifacts: * Collect artifacts: ERROR (in 0:01:55) # add_hosts: ERROR (in 0:17:08) # Results located at /data/lago/ovirt-system-tests/deployment-basic_suite_4.0/default/nosetests-002_bootstrap.py.xml @ Run test: 002_bootstrap.py: ERROR (in 0:17:16) Error occured, aborting Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 258, in do_run self.cli_plugins[args.ovirtverb].do_run(args) File "/usr/lib/python2.7/site-packages/lago/plugins/cli.py", line 180, in do_run self._do_run(**vars(args)) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 488, in wrapper return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/lago/utils.py", line 499, in wrapper return func(*args, prefix=prefix, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/cmd.py", line 102, in do_ovirt_runtest raise RuntimeError('Some tests failed') RuntimeError: Some tests failed I'm still having a look at the log files to see what is the issue. Apart that, by connecting into the engine VM, I saw that the engine process was running, so I tried to access the web GUI, by running an SSH connection to the bare-metal host : ssh -L 8443:192.168.200.4:443 root(a)serv-hv-dev01.sdis.isere.fr (BTW, the readthedoc is showing 200.2 but this is irrelevant for basic_test_4.0, where the engine ip is 200.4) Accessing https://localhost:8443/ is working, but when trying to access the login screen, I'm left with : "The client is not authorized to request an authorization. It's required to access the system using FQDN." ... Dear Redhat employees and al., I sincerely respect your great patience because I'm witnessing the huge complexity of this project, as I'm trying to find my way out this mess^W wonderful project ;) Anyway, I'm feeling I made one step further, so this is encouraging (I have modest expectations and a few is making my day). So about this last issue, please don't answer me that every Lago user is using its own laptop with a graphical layer and running a direct browser access to the web GUI? -- Nicolas ECARNOT

3 11

lago destroy doesn't stop qemu processes
by Nadav Goldin 27 Sep '16

27 Sep '16

Hi, I've noticed a strange issue today. After running successfully lago init && start, then running lago stop && destroy, the qemu-kvm VM's processes are still running even though the destroy command completed successfully. Anyone else encountered this? Nadav.

1 0

moving ovirt-system-tests docs out of lago main doc page
by Eyal Edri 27 Sep '16

27 Sep '16

FYI, I've created a new RTD page for oVirt-system-tests [1] as its an independent project and shouldn't be part of the official Lago documentation, especially not as 1st how-to example. Please feel free to contribute to it and update it with new info, especially on adding new tests or devel use. I've also sent a new PR [2] to remove most of the OST and link to the new OST documentation page, and replacing the main example with the Lago jenkins demo. Going forward, we'll probably create a new lago-examples.git and reference to it for all examples documentation. You'll also notice I've removed some of the documentation around advanced debugging and explanations on internal Lago structure which shouldn't be on how how to page, but in the Lago Tutorial which is also in progress at [3]. I believe this will help new users get Lago up and running much faster and not handle complex settings like nested virt if they are not interested in installing oVirt at first. [1] http://ovirt-system-tests.readthedocs.io [2] https://github.com/lago-project/lago/pull/330 [3] https://github.com/lago-project/lago/pull/228 -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

Please create a repo for ansible under lago org
by Roy Golan 27 Sep '16

27 Sep '16

Hi lake swimmers, In this pr[1] I am adding an ansible playbook (which will grow to a role) to install lago and system-tests. Brought up by maintainers and duck-rh, its more appropriate to create an ansible focused repo which will also play nicely with galaxy and will contain potentially multi roles for all sorts of automation and orchestration we can come up with for lago and lago related. Please create `ansible-role-lago` and I'll move the below pr to it. Thanks, Roy [1] https://github.com/lago-project/lago/pull/326

2 1

lago-ovirt-system-tests ansible PR
by Nadav Goldin 26 Sep '16

26 Sep '16

Hi, As discussed in the PR[1], we might need to think of restructuring our demos/examples repositories. I suggest the following structure: - lago-project/lago-examples.git - Examples of how to use lago to deploy 'X' This repository will hold all examples of deploying Lago, each example will have its own directory. Currently we have: lago-project/lago-examples/jenkins - the current lago-demo repository[1](scripts to deploy Jenkins using Lago) lago-project/lago-examples/ovirt-system-tests - installing lago + ovirt-system-tests[3] - lago-project/lago-ansible-examples.git The same as 'lago-examples.git', only it will hold ansible playbooks that use lago and ansible for deployment(such as the PR) - lago-project/lago-ansible.git Holding a generic ansible playbook to install lago(once we have one :) Though I'll note that I have no concrete idea of what are the ansible conventions. Thoughts? Thanks, Nadav. [1] https://github.com/lago-project/lago/pull/326 [2] https://github.com/lago-project/lago-demo [2] https://github.com/lago-project/lago-demo/tree/master/install_scripts

2 1