- lago-devel - oVirt List Archives

Lago v0.31 released
by Nadav Goldin 09 Jan '17

09 Jan '17

Hi all, New Lago version is out - v0.31, this is a small release with few bug fixes. To upgrade using yum or dnf simply run: yum/dnf update lago Note to ovirt-system-tests users: you might need to re-enable the 'ovirtlago' service after upgrading. This can be done by running: sudo firewall-cmd --add-service=ovirtlago --permanent sudo firewall-cmd --reload If you find any problems, please open an issue in the GitHub page[1]. Docs: http://lago.readthedocs.io/en/0.31/ RPM Repository: http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ GitHub: https://github.com/lago-project/lago/ For OST docs: http://ovirt-system-tests.readthedocs.io/en/latest/ The full change-log: * Mon Jan 09 2017 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.31.0 c8ee2190: Merge pull request #408 from nvgoldin/reposync_no_file 2cef75b4: ovirtlago: allow running reposync with custom_sources only * Mon Jan 09 2017 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.30.4 5fee77b2: Merge pull request #415 from nvgoldin/collect_libvirt 3a603784: ovirtlago: drop ovirt.collect tests a345d4d8: ovirtlago: collect entire /var/log directory * Sun Jan 08 2017 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.30.3 b12bad3a: Merge pull request #421 from nvgoldin/slow_start 3dea5d04: workaround for cirros images not getting ip on boot * Wed Jan 04 2017 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.30.2 7a990a30: Merge pull request #397 from mz-pdm/fix-rpmbuild ee5327a4: Add build dependency on python2-rpm-macros * Wed Jan 04 2017 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.30.1 bb846b43: Merge pull request #398 from mz-pdm/fix-cpu-model 05ccf724: More robust CPU selection Thanks everyone for their contributions! Nadav. [1] http://github.com/lago-project/lago/issues

1 0

Lago v0.30 released
by Nadav Goldin 26 Dec '16

26 Dec '16

Hi, New Lago version is out - v0.30, this release adds few major improvements: 1. Fedora 25 RPMs are now available, also dropping support for Fedora 23 after it was EOL'ed last week(last fc23 version is 0.29). 2. 'lago collect' command now uses SCP to extract files, if SSH in the VM is unavailable it will attempt to use libguestfs. 3. List multiple IPs in each VM. 4. ovirtlago: add new test_equals* assertion functions to the testlib. Other than that this release includes quite a few bug fixes, details are in the change-log below. Thanks for everyone who contributed and reported issues. To upgrade using yum or dnf simply run: yum/dnf update lago Note to ovirt-system-tests users: you might need to re-enable the 'ovirtlago' service after upgrading, this can be done by running: sudo firewall-cmd --add-service=ovirtlago --permanent sudo firewall-cmd --reload If you find any problems, please open an issue in the GitHub page[1]. Docs: http://lago.readthedocs.io/en/0.30/ RPM Repository: http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ GitHub: https://github.com/lago-project/lago/ For OST docs: http://ovirt-system-tests.readthedocs.io/en/latest/ The full change-log: * Mon Dec 26 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.30.0 bfd635d8: Merge pull request #400 from mykaul/multiple_ips 1dc030f5: Add a function to get all the IPs of a VM * Mon Dec 26 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.29.10 d62571fa: Merge pull request #385 from leongold/master 39babc10: added test_equals* tests in order for testlib to include tests * Mon Dec 26 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.29.9 b79fc534: Merge pull request #404 from mykaul/master 8855d669: Fix IPv6 subnet allocation. * Mon Dec 26 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.29.8 ca83aab0: Merge pull request #406 from nvgoldin/sshinject ac4f2df0: Revert usage of 'ssh-inject' in sysprep * Mon Dec 26 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.29.7 d94b452f: Merge pull request #383 from nvgoldin/guestfs_backend 4f6eb28d: use LIBGUESTFS_BACKEND variable if set * Mon Dec 26 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.29.6 71b93315: Merge pull request #382 from nvgoldin/continue_on_failure 0f8cee80: ovirtlago: drop exception handling in test_sequence_gen * Sun Dec 25 2016 Yaniv Kaul <ykaul(a)redhat.com> - 0.29.5 c58abf06: Merge pull request #395 from mykaul/inject-keys 9f9e7185: Small sysprep fixes * Sun Dec 25 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.29.4 60bde7d9: Merge pull request #388 from nvgoldin/extract_scp f7c5762a: Refactor collect command to use SCP * Sun Dec 25 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.29.3 62c92b12: Merge pull request #405 from nvgoldin/wait_net 511e3dc5: Check network is active after creation * Mon Dec 19 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.29.2 f4b86af2: Merge pull request #396 from mykaul/fix_apiv4 ed77c957: Fix oVirt APIv4 creation * Mon Dec 19 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.29.1 12b7fbbf: Merge pull request #391 from nvgoldin/guestfs_params afec1ac3: automation: configure KVM and libguestfs parameters Enjoy! Nadav. [1] http://github.com/lago-project/lago/issues

1 0

Re: [lago-devel] [Infra-private] Jenkins failure - parallel build?
by Barak Korren 25 Dec '16

25 Dec '16

On 20 December 2016 at 14:31, Yaniv Kaul <ykaul(a)redhat.com> wrote: > > > On Tue, Dec 20, 2016 at 12:32 PM, Barak Korren <bkorren(a)redhat.com> wrote: >> >> Its just its "nice" way of telling you that check_merged failed on fc23: >> http://jenkins.ovirt.org/job/lago_master_check-merged-fc23-x86_64/276/ > > > Thanks. That seem to fail on an unrelated issue to my patch... > > 08:21:16 not ok 16 basic.full_run: shell to a vm > 08:21:16 # (from function `helpers.contains' in file > tests/functional/helpers.bash, line 96, > 08:21:16 # in test file tests/functional/basic.bats, line 201) > 08:21:16 # `helpers.contains "$output" "$expected_hostname"' failed > > 08:21:16 # RUNNING:lago shell lago_functional_tests_vm01 hostname > > > ARGH... I'll look into it. > Y. > Worked fine on fc24 and el7, so maybe just drop fc23? Adding Nadav and Gal, moving to lago-devel. -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

3 3

[Attention] Lago release on Tuesday - 20.12.2016
by Nadav Goldin 25 Dec '16

25 Dec '16

Hey all, We plan to release Lago 0.30 on Tuesday, so please make sure all PRs are merged until 11:00 - 20.12.2016 TLV time. Thanks, Nadav.

1 2

New Lago release - v0.29
by Nadav Goldin 13 Dec '16

13 Dec '16

Hey all, New Lago version is out - 0.29, this is a small release with few bug fixes and enhancements, namely: 1. Improvement to VM boot time - interactive boot-menu will now be disabled for fc24/el7 images. 2. The SCSI controller will be generated only if virtio-SCSI is used. 3. 'lago ovirt reposetup' command will run per repository and will handle better conflicting RPMs stored in the local cache. 4. Two bug fixes in the ovirtlago testing library. To upgrade using yum or dnf simply run: yum/dnf update lago If you find any problems, please open an issue in the GitHub page[1]. Known issue with ovirt-system-tests ----------------------------------------------------- After upgrading, the 'ovirtlago' service might be disabled which will fail the 'reposetup' stage. As a work-around please run: sudo firewall-cmd --add-service=ovirtlago --permanent sudo firewall-cmd --reload If not using firewalld, see [2] for iptables instructions. This is caused due to a bug in the spec file, apologizes for the inconvenience. Docs: http://lago.readthedocs.io/en/0.29/ RPM Repository: http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ GitHub: https://github.com/lago-project/lago/i For OST docs: http://ovirt-system-tests.readthedocs.io/en/latest/ The full change-log: * Sun Dec 11 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.29.0 3cf8d87c: Merge pull request #377 from nvgoldin/log_skiptest 916cd379: ovirtlago: log skipped tests to stdout * Sun Dec 11 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.28.5 45a445b7: Merge pull request #376 from mykaul/sysprep_edit b2511c45: Reduce boot time * Sun Dec 11 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.28.4 955974de: Merge pull request #372 from nvgoldin/caps_bug 53262943: ovirtlago: fix bug in capabilities * Wed Dec 07 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.28.3 fbb96183: Merge pull request #374 from mykaul/fix_reposetup 1e935e94: Fix reposync - use 'continue', not 'return' * Tue Dec 06 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.28.2 48bffab0: Merge pull request #369 from nvgoldin/bz1399235 e8a6edb7: make reposync more verbose and fix bz 1399235 * Mon Dec 05 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.28.1 e8d11e3d: Merge pull request #370 from mykaul/scsi_on_demand ef337fff: Create the SCSI controller only if needed. Enjoy! Nadav. [1] http://github.com/lago-project/lago/issues [2] https://github.com/lago-project/lago/pull/379/commits/454930fab2bb7477cedc4…

1 0

New error in mock on lago check_patch
by Nadav Goldin 12 Dec '16

12 Dec '16

Hi Barak, I saw a new error[1] in mock today, IIRC this is not the same error as the usual 'mirror unavailable': DEBUG util.py:502: Executing command: ['/usr/bin/yum-deprecated', '--installroot', '/var/lib/mock/fedora-24-x86_64-b43344fe05507be58adc19b93da78705-5023/root/', '--releasever', '24', 'install', '@buildsys-build', 'bats', 'git', 'python-dulwich', 'python2-devel', 'python-virtualenv', 'python-libguestfs', 'libxslt-devel', 'libvirt-devel', 'libffi-devel', 'openssl-devel', 'dnf-command(builddep)', 'grubby', 'python-pip', '--setopt=tsflags=nocontexts'] with env {'PS1': '<mock-chroot> \\s-\\v\\$ ', 'SHELL': '/bin/bash', 'TERM': 'vt100', 'LC_MESSAGES': 'C', 'HOME': '/builddir', 'LD_PRELOAD': '/tmp/tmpzv6o4sbn/$LIB/nosync.so', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'LANG': 'en_US.UTF-8'} and shell False DEBUG util.py:421: Yum command has been deprecated, use dnf instead. DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information. DEBUG util.py:421: http://mirror.math.princeton.edu/pub/fedora/linux/updates/24/x86_64/repodat…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: http://repo.atlantic.net/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: https://mirrors.kernel.org/fedora/updates/24/x86_64/repodata/repomd.xml: .... You think it might be related to the cache change? Thanks, Nadav. [1] http://jenkins.ovirt.org/job/lago_master_check-patch-fc24-x86_64/260/artifa…

3 7

Fwd: Lago/o-s-t VLAN/dnsmasq issue.
by Leon Goldberg 07 Dec '16

07 Dec '16

Hey, I suspect there's an issue where the current configuration of o-s-t (I've only tried basic-suite-4.0, but I guess it is not suite related), and more specifically dnsmasq's dhcp configuration under Lago/o-s-t (or otherwise) fails to serve VLAN interfaces. After successfully running basic-suite-4.0, I'm trying to call dhclient to serve eth0.600 on host0 (created in 005_network_by_label), which fails. DHCPDISCOVER(s) are reaching the bridge dnsmasq listen on, however no offers are being sent. A couple of things I've tried and the relevant conclusions: 1) After hotplugging a nic (eth1) on host0 via virsh (using the same source network/bridge), I've set a VLAN interface on top of it (eth1.600). Calling dhclient for eth1 worked; eth1.600 failed. I've tried this to rule out the cause being some configuration used in 005_network_by_label. 2) I've added a veth pair, with veth0 being added to Lago's bridge, and with having a VLAN interface (using the same ID) on top of veth1 (veth1.600) dnsmasq was set to listen on/serve veth1.600 without any success, although the VLAN tag is effectively removed. Similarly, DHCPDISCOVER(s) are being received, without any offers being sent. After setting an address manually on eth0.600, I was able to ping veth1.600 <-> eth0.600. Thanks, Leon

2 1

Where is ovirt-engine-sdk-python ?
by Yaniv Kaul 07 Dec '16

07 Dec '16

For some reason, both Hosted Engine and 4.0 ovirt-system-tests suites fail to find the v3 ovirt-engine-sdk-python RPM. I'm pretty sure it was OK yesterday. I do see it in the repos, the failure is: Error: Package: ovirt-engine-cli-3.6.9.2-1.el7.centos.noarch (alocalsync) Requires: ovirt-engine-sdk-python >= 3.6.0.0 However, I do have it: [ykaul@ykaul reposync]$ find . -name "ovirt-engine-cli-3.6.9.2-1.el7.centos.noarch*" ./ovirt-4.0-snapshot-el7/noarch/ovirt-engine-cli-3.6.9.2-1.el7.centos.noarch.rpm ./ovirt-master-snapshot-el7/noarch/ovirt-engine-cli-3.6.9.2-1.el7.centos.noarch.rpm [ykaul@ykaul noarch]$ find . -name "ovirt-engine-sdk-python-*" ./ovirt-engine-sdk-python-3.6.9.2-0.1.20161204.gite99bbd1.el7.centos.noarch.rpm And it's not copied to the deployment - could be a regression in the reposync? Y.

2 1

Deprecating Defaults for to_all_distros Setting in repoman
by Anton Marchukov 01 Dec '16

01 Dec '16

Hello All. If you use repoman please be aware that it currently has hardcoded list of packages that defaults to being distroless. This is controlled by "to_all_distros" configuration setting, but if you do not set it than the defaults are used. For ovirt experimental we decided that we better have all packages to have distro specified in spec. This also inline with most distro packaging guidelines. But then with current defaults repoman will consider those package to be distroless even when they are not and specifying an empty list in configuration is a silly way to override this. This change provides an incompatibility, but you can still use this feature by specifying to_all_distros package list explicitly in the config. So it is just the change of default values at this point: https://gerrit.ovirt.org/#/c/67662/ If somebody is not ok with defaults change and need time to update configuration please let me know. Also if you are not sure we can go another way and have intermediate repoman version that does not do the change, but issue deprecation warning if defaults are being used, so everybody can test their setups. However I think that it is might not be actually needed in this case as it is a configuration thing. Please feel free to comment on change request. Anton. -- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat

2 2

New Lago release - 0.28.0
by Gal Ben Haim 24 Nov '16

24 Nov '16

Hi Everyone! There's a new Lago release with version 0.28.0 ready for you to upgrade! Key Changes: 1. We are now formatting our code with 'yapf' 0.14.0. For all our contributors, please update 'yapf' if needed. 2. When running 'lago shell' it's possible to specify only the suffix of the vm's name and lago will resolve the full name. 3. We removed some unused code from lago-ovirt plugin. Docs - http://lago.readthedocs.io/en/0.28/ Repo - http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ Here are the changes: * Thu Nov 24 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.28.0 ee15dfbb: Merge pull request #356 from lago-project/pkg_resources_exception 81152cd7: Fixed exception handling when checking for deps * Thu Nov 24 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.27.5 ab5aa8a6: Merge pull request #366 from mykaul/skip_freeze 397321e5: Switch to optionall freeze the FS before logs extraction. 5fe33adb: Merge branch 'master' into skip_freeze * Wed Nov 23 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.27.4 c577b8d7: Merge pull request #365 from mykaul/guess_host_name_in_shell d90f2b50: For ease of use, connect to a host even if only the suffix is given. * Tue Nov 22 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.27.3 cb48ad59: Merge pull request #367 from nvgoldin/update_yapf d891034b: Bump yapf version 0.7.1 -> 0.14.0 * Sat Nov 12 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.27.2 fa588e4f: Merge pull request #360 from nvgoldin/ovirtlago_cleanup_i a1bf8dc6: [ost-plugin] cleanup unused commands * Wed Nov 09 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.27.1 290c49a3: Merge pull request #361 from nvgoldin/tests_generate_config 587eba28: Add 'generate-config' verb to functional tests list Gal Ben Haim gbenhaim(a)redhat.com RHEV DevOps

1 0

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

backward-incompatible changes to lago.conf
by Nadav Goldin 25 Sep '16

25 Sep '16

Hi all, As a side-effect of my proposed PR[1], 3 backward-incompatible changes will be added: variables names in lago.conf ------------------------------------ 1. 'default_ssh_user', changed to: 'ssh_user', value: no change. 2. 'default_ssh_password, changed to: 'ssh_password', value: no change. 3. 'template_default_repo', changed to: 'template_repo_name'(same as the existing CLI), value: was never set. The above 3 were hard-coded in config.py's defaults dictionary and never exposed externally. They had no documents, but, if a user knew about them he could have added them manually to lago.conf The reason for changing is that the PR unifies the configuration files and CLI parameters. So keeping the 'default' prefix is misleading and will lead to awkward results, such as: lago --default-ssh-user root --default-ssh-password .... instead of: lago --ssh-user root --ssh-password ... 'template_*' section ------------------------- 'template_*' parameters which are used by lago init command, will be move to [init] section in lago.conf. lago.conf location ----------------------- 1. Drop /etc/lago.d/lago.conf in favour of /etc/lago/lago.conf 2. The installed file from the RPM will be all commented out(i.e. installed just to use as a reference). 3. /etc/lago/lago.conf will be the least important in the hierarchy(you can read more details about the hierarchy in the PR) I'll note that Lago will be fully functional without any configuration file at all. These changes will possibly affect only already-customized lago.conf files. But, changing to the new configuration format will be easy, using the 'generate-config' command: mkdir -p ~/.config/lago && lago generate-config > ~/.config/lago/lago.conf The changes are needed as the the PR mainly deals with standardizing the configuration loading module, so it is a good time for clean-up, and dropping misleading variable names(which were probably good at the time written). Second, I'm not sure how widely these parameters were used, as some of them didn't have any docs. For instance I couldn't find any evidence of usage for 'template_default_repo'(the CLI parameter is the same as it was, 'template_repo_name'). Some possible alternatives: 1. Issue a warning about variables name change, and use both, then in 2-3 versions from now, completely remove them. 2. lago.conf location: Not a major issue, as far as I know, '.d' suffix was used historically for distinguishing a 'directory' from a single configuration file, so having '/etc/lago/' is better(and keeping lago.d if someday we will need to load other user-defined configurations). But this can be easily changed. If there is no request for the alternatives or objection, I'll try to get it merged for the next version and add a short summary of this message to the release email. Thanks, Nadav. [1] https://github.com/lago-project/lago/pull/324

3 2

New Lago release - 0.25
by Nadav Goldin 22 Sep '16

22 Sep '16

Hey, Lago 0.25 is out, introducing few bug fixes, and 2 new features: - /var/lib/lago/subnets is now configurable, this is useful if you want to install Lago in virtualenv(thanks @pilou-) - virtio-scsi support for none-root disks. More details in the PR[1] Here is the full change log: * Wed Sep 21 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.25.0 fdd63ae4: Merge pull request #298 from pilou-/make_lease_dir_configurable 5fb60899: Make lease_dir configurable * Tue Sep 20 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.24.5 8845853f: Merge pull request #323 from mykaul/get_cpu_caps 350db807: Merge branch 'master' into get_cpu_caps 83a7f68a: Add host CPU model detection * Tue Sep 20 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.24.4 1d7722a6: Merge pull request #322 from rafaelmartins/master 9f423604: utils: fixed typo * Tue Sep 20 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.24.3 3dd77113: Merge pull request #318 from lago-project/add_boot_menu 26e9dd71: Adding boot menu * Sun Sep 11 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.24.2 061207c6: Merge pull request #314 from mykaul/add_serial_to_disks c0baab76: Add serial number to disks. * Wed Sep 07 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.24.1 27856ea9: Merge pull request #306 from mykaul/virtio-scsi af1c52d6: virtio-scsi support in Lago 6334cc2b: Merge branch 'master' into virtio-scsi Repo - http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ Docs - http://lago.readthedocs.io/en/0.25/Env_Setup.html Enjoy! [1] https://github.com/lago-project/lago/pull/306

1 0

Lago hostnames
by Sahina Bose 22 Sep '16

22 Sep '16

Hi all, Is it possible to change the generated hostnames in Lago - currently it is of the form lago_basic_suite_hc_host1 and using this hostname fails while peer probing gluster. According to gluster dev: "The valid_host_name () function what we have at gluster CLI is as per RFC 1912 and an underscore in the hostname is *not* accepted." If not, other suggestions? thanks sahina

3 3

reposync
by Sahina Bose 21 Sep '16

21 Sep '16

Hi! Not sure if this is the right forum for this newbie question - if not, please point me to the right one. My issue is the repos available in the guest VMs started by lago. I have executed from the working dir #lagocli ovirt reposetup --reposync-yum-config="/home/ovirt-system-tests/basic_suite_hc/reposync-config.repo" When I launch into shell of guest VM : [root@lago_basic_suite_hc_host0 ~]# yum repolist Loaded plugins: fastestmirror http://192.168.201.1:8585/el7/repodata/repomd.xml: [Errno 14] curl#7 - "Failed connect to 192.168.201.1:8585; Connection refused" Trying other mirror. I must be missing some step, could you help me figure out what? thanks! sahina

2 2

Re: [lago-devel] Lago check patch is failing when running on my laptop
by Gal Ben Haim 15 Sep '16

15 Sep '16

Not sure why, but adding back "bootmenu enable='yes'" solved the problem. Gal Ben Haim gbenhaim(a)redhat.com RHEV DevOps ----- Original Message ----- From: "Yaniv Kaul" <ykaul(a)redhat.com> To: "Gal Ben Haim" <gbenhaim(a)redhat.com> Sent: Thursday, September 15, 2016 9:58:51 AM Subject: Re: [lago-devel] Lago check patch is failing when running on my laptop I'm not very much interested in mock (I think it's not a good idea), but I can check. Where do I get gerrit.ovirt.org/jenkins/mock_configs/mock_runner.sh from? simple wget fails obviously. Y. On Wed, Sep 14, 2016 at 6:13 PM, Gal Ben Haim <gbenhaim(a)redhat.com> wrote: > for running the mock - ~/gerrit.ovirt.org/jenkins/moc > k_configs/mock_runner.sh --mock-confs-dir ~/gerrit.ovirt.org/jenkins/moc > k_configs/ -e automation/check-patch.sh -s fc24 > for running the test inside the mock - ./automation/check-patch.sh > > Gal Ben Haim > gbenhaim(a)redhat.com > RHEV DevOps > > ----- Original Message ----- > From: "Yaniv Kaul" <ykaul(a)redhat.com> > To: "Nadav Goldin" <ngoldin(a)redhat.com> > Cc: "Gal Ben Haim" <gbenhaim(a)redhat.com>, lago-devel(a)ovirt.org > Sent: Wednesday, September 14, 2016 12:41:26 PM > Subject: Re: [lago-devel] Lago check patch is failing when running on my > laptop > > What command are you using to trigger it? > My code adds virtio-scsi - but no one is using it (yet, I am in my tests > and it works well). > It also adds UNMAP support to all disk - which should be silently ignored > (as no one is using yet virtio-scsi). > Apart from that, not sure what could cause it. > > On Wed, Sep 14, 2016 at 12:09 PM, Nadav Goldin <ngoldin(a)redhat.com> wrote: > > > Hitting the same error on 'master' - this time on fc24 host & fc24 > > chroot. Reverting back to '531bd75'(before iSCSI PR) seems to resolve > > the issue. > > Strangely enough, re-triggering the CI on current master branch works.[1] > > As a side note, I was mistaken - check_patch do run on VMs(it is OST > > that run on BMs) > > > > [1] http://jenkins.ovirt.org/job/lago_master_check-patch-fc24-x8 > 6_64/102/ > > > > On Mon, Sep 12, 2016 at 8:46 PM, Nadav Goldin <ngoldin(a)redhat.com> > wrote: > > > iirc, we are runing all lago jobs on fc24 bare metal slaves, since > > > there was an issue with running fc24 chroots on el7 hosts, not sure if > > > it was resolved. It might explain why Jenkins jobs are running ok. > > > > > > > > > > > > > > > On Sun, Sep 11, 2016 at 8:56 PM, Gal Ben Haim <gbenhaim(a)redhat.com> > > wrote: > > >> Hi All, > > >> > > >> When running check-patch on my laptop and mini-dell (rhel 7.1 and mock > > fc-24 on both), > > >> the tests fails on ssh timeout. > > >> > > >> I'm running the tests on the latest commit on master (hash 27856ea). > > >> I tried to run the tests on hash: 531bd75 (0.24 stable release) and it > > >> went well. > > >> > > >> It's strange because I don't see those failures on jenkins. > > >> > > >> test log: http://pastebin.test.redhat.com/410685 > > >> > > >> Does anyone else experiencing this problem ? > > >> > > >> > > >> Gal Ben Haim > > >> gbenhaim(a)redhat.com > > >> RHEV DevOps > > >> _______________________________________________ > > >> lago-devel mailing list > > >> lago-devel(a)ovirt.org > > >> http://lists.ovirt.org/mailman/listinfo/lago-devel > > _______________________________________________ > > lago-devel mailing list > > lago-devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/lago-devel > > >

1 0