- Devel - oVirt List Archives

api.vms.get(VM0_NAME).snapshots.list() returned 404
by Yedidyah Bar David 24 Aug '17

24 Aug '17

Hi all, A jenkins job that ran as a check-patch for ovirt-system-tests failed [1] for me due to what seems to me like unrelated reason. It seems to have failed in [2]. This code does various actions with vm snapshots. At some point it failed with 'status: 404' [3]. httpd's log also shows 404 [4] in the end, after a long list of successful actions with snapshots. engine.log [5] shows no relevant error AFAIU. Is this reasonable? Expected? Not sure where the bug is, if at all. Best, [1] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… [2] https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=blob;f=image-ng-… [3] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… [4] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… [5] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_… -- Didi

2 1

Lago and vm templates
by Marc Young 24 Aug '17

24 Aug '17

Im currently neck deep in ovirt-system-tests and lago I see alot of usages about importing VMs from templates, but are there any examples of exporting a VM to template? Side note I cant find a good source of methods available for use in python-lago-ovirt (or even python-lago). The docs[1] are pretty lacking [1] http://lago.readthedocs.io/en/latest/lago.html

1 0

Host firewalld support patches merged
by Martin Perina 23 Aug '17

23 Aug '17

Hi, we have just merged patches [1], which adds the ability to use firewalld instead of iptables on oVirt hosts. The type of firewall can be defined per cluster, there is new combo box 'Firewall Type' in 'Cluster Detail' dialog. By default all new clusters will be created with firewalld enabled, existing clusters needs to be switched from iptables to firewalld manually and then invoke Reinstall on all hosts in a cluster. Be aware that firewalld can be enabled only for hosts with 4.2 capabilities (VDSM >= 4.20.0). Firewalld deployment is using Ansible role introduced in new ovirt-ansible-roles package [2], which executes ovirt-host-deploy role [3]. ovirt-ansible-roles package is installed automatically if engine is installed from RPM, but for development environment installation please take a look at [4], because ovirt-ansible-roles needs to be installed manually into development environment prefix. Please let me or Ondra know if you find any issues. Thanks Martin [1] https://gerrit.ovirt.org/78504 [2] https://github.com/ovirt/ovirt-ansible [3] https://github.com/oVirt/ovirt-ansible/blob/master/roles/ovirt-host-deploy/… [4] https://github.com/oVirt/ovirt-engine/blob/master/README.adoc#host-deploy-v…

2 1

[ ovirt-devel ] [OST Failure Report ] [ oVirt Master ] [ 002_bootstrap ] [ 20/08/17 ]
by Daniel Belenky 23 Aug '17

23 Aug '17

Failed test: basic_suite_master/002_bootstrap Version: oVirt Master Link to failed job: ovirt-master_change-queue-tester/1860/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1860/> Link to logs (Jenkins): test logs <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1860/artifact…> Suspected patch: https://gerrit.ovirt.org/#/c/80749/3 >From what I was able to find, It seems that for some reason VDSM failed to start on host 1. The VDSM log is empty, and the only error I could find in supervdsm.log is that start of LLDP failed (Not sure if it's related) >From host-deploy log: <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1860/artifact…> 2017-08-19 16:38:41,476-0400 DEBUG otopi.plugins.otopi.services.systemd systemd.state:130 starting service vdsmd 2017-08-19 16:38:41,476-0400 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:813 execute: ('/bin/systemctl', 'start', 'vdsmd.service'), executable='None', cwd='None', env=None 2017-08-19 16:38:44,628-0400 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:863 execute-result: ('/bin/systemctl', 'start', 'vdsmd.service'), rc=1 2017-08-19 16:38:44,630-0400 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:921 execute-output: ('/bin/systemctl', 'start', 'vdsmd.service') stdout: 2017-08-19 16:38:44,630-0400 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/bin/systemctl', 'start', 'vdsmd.service') stderr: Job for vdsmd.service failed because the control process exited with error code. See "systemctl status vdsmd.service" and "journalctl -xe" for details. 2017-08-19 16:38:44,631-0400 DEBUG otopi.context context._executeMethod:142 method exception Traceback (most recent call last): File "/tmp/ovirt-dunwHj8Njn/pythonlib/otopi/context.py", line 132, in _executeMethod method['method']() File "/tmp/ovirt-dunwHj8Njn/otopi-plugins/ovirt-host-deploy/vdsm/packages.py", line 224, in _start self.services.state('vdsmd', True) File "/tmp/ovirt-dunwHj8Njn/otopi-plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'vdsmd' >From /var/log/messages: <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1860/artifact…> Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: Error: Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: One of the modules is not configured to work with VDSM. Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: To configure the module use the following: Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: 'vdsm-tool configure [--module module-name]'. Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: If all modules are not configured try to use: Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: 'vdsm-tool configure --force' Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: (The force flag will stop the module's service and start it Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: afterwards automatically to load the new configuration.) Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: abrt is already configured for vdsm Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: lvm is configured for vdsm Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: libvirt is already configured for vdsm Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: multipath requires configuration Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: Modules sanlock, multipath are not configured Aug 19 16:38:44 lago-basic-suite-master-host0 vdsmd_init_common.sh: vdsm: stopped during execute check_is_configured task (task returned with error code 1). Thanks, -- DANIEL BELENKY RHV DEVOPS EMEA VIRTUALIZATION R&D <https://red.ht/sig>

7 11

Jenkins job Build History
by Yedidyah Bar David 23 Aug '17

23 Aug '17

Hi all, Is it possible to make the "Build History" box in jenkins show some more information? E.g. Who/What triggered each build? This is especially useful for *manual* jobs, that are supposed to be triggered manually by users. Later, it's a bit hard to find your builds. Thanks, -- Didi

3 2

[ACTION REQUIRED] engine master branch was broken today
by Yedidyah Bar David 22 Aug '17

22 Aug '17

Hi all, It was broken by 7914051a (merged yesterday) and fixed by 7e27a47 (merged today). If you run 'engine-setup' with a broken version, it will exit silently with rc=1. If this happens, please pull from master. Sorry for the mess. Best, -- Didi

1 0

Authentication error are not helpful - " The redirection URI for client is not registered "
by Roy Golan 22 Aug '17

22 Aug '17

When using OST you get an engine on isolated network, that in order to make available you must tunnel. When tunnelling you end up with a URI with a uncommon port or hostname that will result an error while authenticating: URL: https://localhost:9000/ovirt-engine This displays this error: *" The redirection URI for client is not registered " <http://imgur.com/a/D0edf>*See screenshot <http://imgur.com/a/D0edf> Can we expose the expected valid redirect urls? Is it used for something else than obscurity? If we can expose it then at least a message of the form would be better: * " Please make sure to connect to https://EXPECTED/URL " <https://the>* \R

3 2

[ OST Failure Report ] [ upgrade-from-release-suite-master ] [ 21/08/2017 ][000_deploy]
by Valentina Makarova 22 Aug '17

22 Aug '17

Hello! OST failed in ./run_suilte.sh upgrade-from-release-suite-master (it is likely to appear after updating in some remote repo) with error: @ Deploy oVirt environment: # Deploy environment: * [Thread-2] Deploy VM lago-upgrade-from-release-suite-master-engine: STDERR + EL7='release 7\.[0-9]' + cat + cat ++ /sbin/ip -4 -o addr show dev eth0 ++ awk '{split($4,a,"."); print a[1] "." a[2] "." a[3] "." a[4]}' ++ awk -F/ '{print $1}' + ADDR=192.168.203.2 + echo '192.168.203.2 engine' + install_firewalld + grep 'release 7\.[0-9]' /etc/redhat-release + rpm -q firewalld + systemctl enable firewalld + systemctl start firewalld + yum install --nogpgcheck -y --downloaddir=/dev/shm ntp net-snmp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*' http://mirror.vilkam.ru/centos/7.3.1611/os/x86_64/repodata/bd50ff3d861cc21d…: [Errno 14] curl#7 - "Failed connect to mirror.vilkam.ru:80; Connection refused" Trying other mirror. *Error: Package: ovirt-engine-extension-aaa-ldap-setup-1.3.3-1.el7.centos.noarch (alocalsync)* * Requires: ovirt-engine-extension-aaa-ldap = 1.3.3-1.el7.centos* * Installing: ovirt-engine-extension-aaa-ldap-1.3.2-1.el7.centos.noarch (alocalsync)* * ovirt-engine-extension-aaa-ldap = 1.3.2-1.el7.centos* * [Thread-2] Deploy VM lago-upgrade-from-release-suite-master-engine: ERROR (in 0:01:18) Error while running thread Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue queue.put({'return': func()}) File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1610, in _deploy_host (script, ret, host.name(), ), RuntimeError: /home/vmakarova/template_update/ovirt-system-tests/deployment-upgrade-from-release-suite-master/default/scripts/_home_vmakarova_template_update_ovirt-system-tests_upgrade-from-release-suite-master_.._common_deploy-scripts_setup_engine.sh failed with status 1 on lago-upgrade-from-release-suite-master-engine Updating of my yum packages and pip packages is not effective. Please, update remote repo or say me, how can I run this. Sincerely, Valentina Makarova

4 4

Re: [ovirt-devel] [CQ]: 80866, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by Michal Skrivanek 22 Aug '17

22 Aug '17

This seems unrelated to both changes mentioned below Please take a look at why does it identify those patches At least one issue seems to be http://lists.ovirt.org/pipermail/devel/2017-August/031057.html Thanks, michal > On 22 Aug 2017, at 08:40, oVirt Jenkins <jenkins(a)ovirt.org> wrote: > > A system test invoked by the "ovirt-master" change queue including change > 80866,2 (ovirt-engine) failed. However, this change seems not to be the root > cause for this failure. Change 80721,3 (ovirt-engine) that this change depends > on or is based on, was detected as the cause of the testing failures. > > This change had been removed from the testing queue. Artifacts built from this > change will not be released until either change 80721,3 (ovirt-engine) is fixed > and this change is updated to refer to or rebased on the fixed version, or this > change is modified to no longer depend on it. > > For further details about the change see: > https://gerrit.ovirt.org/#/c/80866/2 > > For further details about the change that seems to be the root cause behind the > testing failures see: > https://gerrit.ovirt.org/#/c/80721/3 > > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1899/ > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra

2 1

FYI - Connectivity issues on GitHub.com
by Eyal Edri 21 Aug '17

21 Aug '17

Published on https://status.github.com/: "16:44 IDT We are investigating reports of connectivity issues to GitHub.com and related services. " This might affect projects oVirt running on GitHub -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0