September 2016 - lago-devel - oVirt List Archives

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

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

Lago check patch is failing when running on my laptop
by Gal Ben Haim 15 Sep '16

15 Sep '16

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

3 5

New Lago release - 0.24
by Nadav Goldin 07 Sep '16

07 Sep '16

Hey, Lago 0.24 is out, introducing 2 new features: initial DNS + IPv6 support, and a new flat output formatter for the CLI. Here is the full change log: * Sun Sep 04 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.24.0 531bd754: Merge pull request #303 from lago-project/refactor_engine_api_request 41a15764: Removed redundant checks when getting ovirt api * Sun Sep 04 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.23.4 b17a5c29: Merge pull request #304 from mykaul/DNS 783aae26: Add DNS and IPv6 support * Thu Sep 01 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.23.3 ee7b814f: Merge pull request #301 from lago-project/flat_output_plugin 1f6fc70f: Added flat output formatter * Mon Aug 22 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.23.2 ed6371fa: Merge pull request #294 from sandrobonazzola/master ca3c023b: reposetup: be more verbose on reposync failure 13e921eb: Merge branch 'master' into master * Tue Aug 16 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.23.1 030f6e76: Merge pull request #279 from mpolednik/libvirt-auth ed219883: libvirt: add auth Repo - http://resources.ovirt.org/repos/lago/stable/0.0/rpm/ Docs - http://lago.readthedocs.io/en/0.24/Env_Setup.html Enjoy!

1 0

lago_master_check-patch-fc23-x86_64 #224 Console [Jenkins]
by Yaniv Kaul 06 Sep '16

06 Sep '16

New breakage (that I hope) has nothing to do with my patch: Error: nothing provides repoman >= 2.0.12 needed by python-lago-ovirt-0.24.1-1.fc23.noarch Anyone? http://jenkins.ovirt.org/job/lago_master_check-patch-fc23-x86_64/224/console

4 4