April 2019 - Devel - oVirt List Archives

[VDSM] Started getting virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired
by Edward Haas 11 Jan '24

11 Jan '24

Hi, I have a VM which acts as an oVirt host with VDSM installed. I use it for testing without connecting it to Engine. Recently VDSM fails to come up and I see this error: Sep 26 17:58:18 localhost libvirtd: 2018-09-26 14:58:18.978+0000: 12176: error : virNetTLSContextCheckCertTimes:154 : The server certificate /etc/pki/vdsm/certs/vdsmcert.pem has expired Any hint on how to generate or fetch a new certificate without the help of Engine? Thanks, Edy.

3 5

Error Java SDK Issue??
by Geschwentner, Patrick 02 Apr '21

02 Apr '21

Dear Ladies and Gentlemen! I am currently working with the java-sdk and I encountered a problem. If I would like to retrieve the disk details, I get the following error: Disk currDisk = ovirtConnection.followLink(diskAttachment.disk()); The Error is occurring in this line: [cid:image001.png@01D44537.AF127FD0] The getResponst looks quiet ok. (I inspected: [cid:image002.png@01D44537.AF127FD0] and it looks ok). Error: wrong number of arguments The code is quiet similar to what you published on github (https://github.com/oVirt/ovirt-engine-sdk-java/blob/master/sdk/src/test/jav… ). Can you confirm the defect? Best regards Patrick

6 11

OST's basic suite UI sanity tests optimization
by Marcin Sobczyk 07 Aug '19

07 Aug '19

Hi, _TL; DR_ Let's cut the running time of '008_basic_ui_sanity.py' by more than 3 minutes by sacrificing Firefox and Chrome screenshots in favor of Chromium. During the OST hackathon in Brno this year, I saw an opportunity to optimize basic UI sanity tests from basic suite. The way we currently run them, is by setting up a Selenium grid using 3 docker containers, with a dedicated network... that's insanity! (pun intended). Let's a look at the running time of '008_basic_ui_sanity.py' scenario (https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test…) 01:31:50 @ Run test: 008_basic_ui_sanity.py: 01:31:50 nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] 01:31:50 # init: 01:31:50 # init: Success (in 0:00:00) 01:31:50 # start_grid: 01:34:05 # start_grid: Success (in 0:02:15) 01:34:05 # initialize_chrome: 01:34:18 # initialize_chrome: Success (in 0:00:13) 01:34:18 # login: 01:34:27 # login: Success (in 0:00:08) 01:34:27 # left_nav: 01:34:45 # left_nav: Success (in 0:00:18) 01:34:45 # close_driver: 01:34:46 # close_driver: Success (in 0:00:00) 01:34:46 # initialize_firefox: 01:35:02 # initialize_firefox: Success (in 0:00:16) 01:35:02 # login: 01:35:11 # login: Success (in 0:00:08) 01:35:11 # left_nav: 01:35:29 # left_nav: Success (in 0:00:18) 01:35:29 # cleanup: 01:35:36 # cleanup: Success (in 0:00:06) 01:35:36 # Results located at /dev/shm/ost/deployment-basic-suite-master/008_basic_ui_sanity.py.junit.xml 01:35:36 @ Run test: 008_basic_ui_sanity.py: Success (in 0:03:45) Starting the Selenium grid takes 2:15 out of 3:35 of total running time! I've investigated a lot of approaches and came up with something like this: * install 'chromium-headless' package on engine VM * download 'chromedriver' and 'selenium hub' jar and deploy them in '/var/opt/' on engine's VM * run 'selenium.jar' on engine VM from '008_basic_ui_sanity.py' by using Lago's ssh * connect to the Selenium instance running on the engine in '008_basic_ui_sanity.py' * make screenshots This series of patches represent the changes: https://gerrit.ovirt.org/#/q/topic:selenium-on-engine+(status:open+OR+statu…. This is the new running time (https://jenkins.ovirt.org/view/oVirt system tests/job/ovirt-system-tests_manual/4195/): 20:13:26 @ Run test: 008_basic_ui_sanity.py: 20:13:26 nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$'] 20:13:26 # init: 20:13:26 # init: Success (in 0:00:00) 20:13:26 # make_screenshots: 20:13:27 * Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fdb6004f8d0>: Failed to establish a new connection: [Errno 111] Connection refused',)': /wd/hub 20:13:27 * Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fdb6004fa10>: Failed to establish a new connection: [Errno 111] Connection refused',)': /wd/hub 20:13:27 * Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fdb6004fb50>: Failed to establish a new connection: [Errno 111] Connection refused',)': /wd/hub 20:13:28 * Redirecting http://192.168.201.4:4444/wd/hub -> http://192.168.201.4:4444/wd/hub/static/resource/hub.html 20:14:02 # make_screenshots: Success (in 0:00:35) 20:14:02 # Results located at /dev/shm/ost/deployment-basic-suite-master/008_basic_ui_sanity.py.junit.xml 20:14:02 @ Run test: 008_basic_ui_sanity.py: Success (in 0:00:35) (The 'NewConnectionErrors' is waiting for Selenium hub to be up and running, I can silence these later). And the screenshots are here: https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… _The pros:_ * we cut the running time by more than 3 minutes _The cons:_ * we don't get Firefox or Chrome screenshots - we get Chromium screenshots (although AFAIK, QE has much more Selenium tests which cover both Firefox and Chrome) * we polute the engine VM with 'chromium-headless' package and deps (in total: 'chromium-headless', 'chromium-common', 'flac-libs' and 'minizip'), although we can remove these after the tests _Some design choices explained:_ Q: Why engine VM? A: Because the engine VM already has 'X11' libs. We could install 'chromium-headless' (and even other browsers) on our Jenkins executors, but that would mess them up a lot. Q: Why Chromium? A: Because it has a separate 'headless' package. Q: Why not use 'chromedriver' RPM in favor of https://chromedriver.storage.googleapis.com Chromedriver builds? A: Because the RPM version pulls a lot of extra dependencies even on the engine VM ('gtk3', 'cairo' etc.). Builds from the URL are the offical Google Chromedriver builds, they contain a single binary, and they work for us. _What still needs to be polished with the patches:_ * Currently 'setup_engine_selenium.sh' script downloads each time 'selenium.jar' and 'chromedriver.zip' (even with these downloads we get much faster set-up times) - we should bake these into the engine VM image template. * 'selenium_hub_running' function in 'selenium_on_engine.py' is hackish - an ability to run an ssh command with a context manager (and auto-terminate on it exits) should be part of Lago. Can be refactored. Questions, comments, reviews are welcome. Regards, Marcin

7 10

ovirt-system-tests_compat-4.2-suite-master failing for 3 weeks?
by Doron Fediuck 17 May '19

17 May '19

https://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/55… The current failure is on adding a storage domain. Did anyone review it?

7 10

Testing oVirt with Gluster 6
by Simone Tiraboschi 13 May '19

13 May '19

Hi, according to https://bugzilla.redhat.com/show_bug.cgi?id=1673058 the network throughput usage increases by a x5 upgrading from Gluster 3.12 to Gluster 5.y. This seems definitively problematic on our hyper-converged environments: I read more than one report where, over 1 Gbps network, sanlock could not be refreshed quickly enough and so killed the engine VM if not rebooted the host due to the watchdog. This is probably due to the fact that, according to that bug, the network got completely saturated. Faster networks seems still fine. https://bugzilla.redhat.com/show_bug.cgi?id=1673058 is probably going to be solved for Gluster 5.6. On the other side we have https://bugzilla.redhat.com/1693998 <https://bugzilla.redhat.com/show_bug.cgi?id=1693998> about rebasing over Gluster 6 which seems not affected by that issue. Do you have concrete plans about testing oVirt with Gluster 6? thanks, Simone

5 7

Fedora 29 support?
by Nir Soffer 08 May '19

08 May '19

Fedora 28 will be EOL in few month, and at this point people are migration to Fedora 29. I tried yesterday to build engine development setup on Fedora 29 VM, and found that it does not work: - some packages are missing on engine side - after hacking the ovirt.repo files, pointing to "28" instead of "$releasever", I got the packages... - but then adding a host fail with "Python is missing" on the host, which is working Fedora 28 host used with engine before. What are our plans for supporting Fedora 29 on engine and host? I hope that the work we did for Fedora 28 will make it easier to port to Fedora 29. Nir

3 5

Fwd: Fedora 30 officially released!
by Sandro Bonazzola 30 Apr '19

30 Apr '19

FYI ---------- Forwarded message --------- Da: Matthew Miller <mattdm(a)fedoraproject.org> Date: mar 30 apr 2019 alle ore 16:02 Subject: Fedora 30 officially released! To: <announce(a)lists.fedoraproject.org> Cc: <devel-announce(a)lists.fedoraproject.org> It's been six months, and like clockwork, we release Fedora 30 today! Thank you to the thousands of people who worked to bring this release together. Fedora doesn't happen by magic: it happens because of you! Read the official announcement at: * https://fedoramagazine.org/announcing-fedora-30/ or just go ahead and grab it from: * https://getfedora.org/ -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr… -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

Some feedback of an upgrade from 4.2 to 4.3 (EPYC Cluster)
by Tobias Scheinert 30 Apr '19

30 Apr '19

Hi, 1) Thank you all for the official support of the AMD EPYC processors in version 4.3! :-) 2) During the upgrade process I removed the old guest ISO file and replaced it with the new one (different filename of course). As I moved a virtual machine with the old ISO file mounted, the vm crashed. "Migration failed: Lost connection with qemu process (VM: <vmname>, Source: <ovirt-node-host>)." Yes I know this is not real bug (dumb user), but maybe it is good preventing the users for doing something stupid ;-) 3) The log contains following messages after upgrading the node: "VDSM <ovirt-node-host> command Get Host Statistics failed: Internal JSON-RPC error: {'reason': '[Errno 19] genev_sys_6081 is not present in the system'}" This stops after some time ~20-30 minutes, but comes back after a restart of a node. And disappears again after some time. At the moment we have no problems and not taking this as a real issue. 4) If we are running Windows 10 guests newer than build version 1709, the vm crashes on our EPYC cluster, on the SandyBridge cluster the issue doesn't exists. The reason is the wrong CPU model of QEMU, see: <https://bugzilla.redhat.com/show_bug.cgi?id=1593190> We fixed this problem with a line in "/etc/modprobe.d/kvm.conf" "options kvm ignore_msrs=1". Thank you all for this great piece of software :-) Regard Tobias

3 2

HA VM not work when VM OS cannot run normally
by du_hongyu＠yeah.net 30 Apr '19

30 Apr '19

HI， I create a HA VM in ovirt follaw this article https://ovirt.org/develop/ha-vms.html#highly-available-vms-and-io-errors when my vm‘s OS can not run, but ovirt consider this vm is up, so is this a bug for HA VM? can you give me some advise? Regards Hongyu Du

2 4

repo, el7: Provide nmstate through copr for VDSM
by Sandro Bonazzola 30 Apr '19

30 Apr '19

Hi, Is https://gerrit.ovirt.org/#/c/96856/ still relevant? I see nmstate-0.0.5 is in EPEL testing and shipped within Fedora while the copr repo has 0.0.4. Can I abandon the patch? -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 2

Nominating Miguel Barosso as ovirt-provider-ovn maintainer
by Marcin Mirecki 29 Apr '19

29 Apr '19

I would like to propose Miguel Barosso as a maintainer for ovirt-provider-ovn. Miguel is now working on the project for almost a year, and for the last few month is practically the only active contributor to the project. He has successfully implemented new features right up from the design stage, added a new integration test framework, fixed an endless amount of bugs and contributed over 200 patches to the project. Currently the only maintainer (me) is no longer actively working on the project, which is a cause of a review bottleneck. Thanks, Marcin

5 4

[ OST Failure Report ] [ oVirt 4.3 (vdsm) ] [ 22-03-2019 ] [ 002_bootstrap.add_master_storage_domain ]
by Dafna Ron 29 Apr '19

29 Apr '19

Hi, We are failing branch 4.3 for test: 002_bootstrap.add_master_storage_domain It seems that in one of the hosts, the vdsm is not starting there is nothing in vdsm.log or in supervdsm.log CQ identified this patch as the suspected root cause: https://gerrit.ovirt.org/#/c/98748/ - vdsm: client: Add support for flow id Milan, Marcin, can you please have a look? full logs: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/326/artifact/bas… the only error I can see is about host not being up (makes sense as vdsm is not running) Stacktrace File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/basic-suite-4.3/test-scenarios/002_bootstrap.py", line 417, in add_master_storage_domain add_iscsi_storage_domain(prefix) File "/home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/basic-suite-4.3/test-scenarios/002_bootstrap.py", line 561, in add_iscsi_storage_domain host=_random_host_from_dc(api, DC_NAME), File "/home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/basic-suite-4.3/test-scenarios/002_bootstrap.py", line 122, in _random_host_from_dc return _hosts_in_dc(api, dc_name, True) File "/home/jenkins/workspace/ovirt-4.3_change-queue-tester/ovirt-system-tests/basic-suite-4.3/test-scenarios/002_bootstrap.py", line 119, in _hosts_in_dc raise RuntimeError('Could not find hosts that are up in DC %s' % dc_name) 'Could not find hosts that are up in DC test-dc\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:937bdea7-a2a3-47ad-9383-36647ea37ddf:Get ssh client for lago-basic-suite-4-3-engine:\nlago.ssh: DEBUG: end task:937bdea7-a2a3-47ad-9383-36647ea37ddf:Get ssh client for lago-basic-suite-4-3-engine:\nlago.ssh: DEBUG: Running c07b5ee2 on lago-basic-suite-4-3-engine: cat /root/multipath.txt\nlago.ssh: DEBUG: Command c07b5ee2 on lago-basic-suite-4-3-engine returned with 0\nlago.ssh: DEBUG: Command c07b5ee2 on lago-basic-suite-4-3-engine output:\n 3600140516f88cafa71243648ea218995\n360014053e28f60001764fed9978ec4b3\n360014059edc777770114a6484891dcf1\n36001405d93d8585a50d43a4ad0bd8d19\n36001405e31361631de14bcf87d43e55a\n\n-----------

8 31

oVirt Node build failure on 4.2 snapshot
by Sandro Bonazzola 28 Apr '19

28 Apr '19

https://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/… Not sure what happened but yesterday ovirt Node 4.2 jenkins job started failing with: 06:28:14,517 INFO program:Error: Package: vdsm-client-4.20.47-2.git31d3591.el7.noarch (ovirt-4.2-snapshot) 06:28:14,518 INFO program:Requires: vdsm-api = 4.20.47-2.git31d3591.el7 06:28:14,518 INFO program:Available: vdsm-api-4.20.23-1.el7.noarch (ovirt-4.2-centos-ovirt42) 06:28:14,519 INFO program:vdsm-api = 4.20.23-1.el7 06:28:14,520 INFO program:Available: vdsm-api-4.20.39.1-1.el7.noarch (ovirt-4.2-centos-ovirt42) 06:28:14,521 INFO program:vdsm-api = 4.20.39.1-1.el7 06:28:14,522 INFO program:Error: Package: vdsm-jsonrpc-4.20.47-2.git31d3591.el7.noarch (ovirt-4.2-snapshot) 06:28:14,522 INFO program:Requires: vdsm-api = 4.20.47-2.git31d3591.el7 06:28:14,523 INFO program:Available: vdsm-api-4.20.23-1.el7.noarch (ovirt-4.2-centos-ovirt42) 06:28:14,524 INFO program:vdsm-api = 4.20.23-1.el7 06:28:14,525 INFO program:Available: vdsm-api-4.20.39.1-1.el7.noarch (ovirt-4.2-centos-ovirt42) 06:28:14,526 INFO program:vdsm-api = 4.20.39.1-1.el7 06:28:14,527 INFO program:Error: Package: vdsm-python-4.20.47-2.git31d3591.el7.noarch (ovirt-4.2-snapshot) 06:28:14,528 INFO program:Requires: vdsm-api = 4.20.47-2.git31d3591.el7 06:28:14,528 INFO program:Available: vdsm-api-4.20.23-1.el7.noarch (ovirt-4.2-centos-ovirt42) 06:28:14,529 INFO program:vdsm-api = 4.20.23-1.el7 06:28:14,530 INFO program:Available: vdsm-api-4.20.39.1-1.el7.noarch (ovirt-4.2-centos-ovirt42) 06:28:14,531 INFO program:vdsm-api = 4.20.39.1-1.el7 Looking at vdsm.spec I see: grep "\-api" vdsm.spec.in: Requires: %{name}-api = %{version}-%{release} Requires: %{name}-api = %{version}-%{release} Obsoletes: %{name}-api < 4.16 Requires: %{name}-api = %{version}-%{release} Requires: glusterfs-api >= %{gluster_version} Looking at the Obsoletes: %package jsonrpc Summary: VDSM API Server BuildArch: noarch Requires: %{name}-python = %{version}-%{release} Requires: %{name}-api = %{version}-%{release} Requires: %{name}-yajsonrpc = %{version}-%{release} Obsoletes: %{name}-api < 4.16 There's an Obsoletes without a Provides while there are still around lines with: Requires: %{name}-api = %{version}-%{release} so I don't know how it could have worked till now. -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

3 2

ovirt-engine has been tagged (ovirt-engine-4.3.3.6)
by Tal Nisan 24 Apr '19

24 Apr '19

1 0

ovirt-vmconsole CI check-patch
by Sandro Bonazzola 19 Apr '19

19 Apr '19

Hi, looks like ovirt-vmconsole is missing CI check-patch stage. Is there any reason for not running at least an rpm build in check-patch? I see the project has unit testing, why not run them on check-patch? Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 2

Re: Is only master branch of ovirt-engine analyzed on coverity scan?
by Nasif Imtiaz 18 Apr '19

18 Apr '19

Hi Martin, Thanks for answering my questions. I am a PhD student at North Carolina State University. As a part of our research project, we are looking at how developers respond to alerts from static analysis tools (e.g. Coverity). If you can participate in a short survey <https://ncsu.qualtrics.com/jfe/form/SV_dakHeRNGBoWq9r7> answering how your project team monitors Coverity reports, that will help us greatly in our research. Thanks, Nasif

1 0

sanlock 3.7.1-2 for Fedora available in updates-testing
by Nir Soffer 16 Apr '19

16 Apr '19

This version refines the new 4k constants. If you use Fedora host, please test and submit feedback. To update sanlock: sudo dnf update --enablerepo=updates-testing sanlock python2-sanlock Submit feedback here: f28: https://bodhi.fedoraproject.org/updates/FEDORA-2019-3294cacaa5 f29: https://bodhi.fedoraproject.org/updates/FEDORA-2019-3f694721ce f30: https://bodhi.fedoraproject.org/updates/FEDORA-2019-fff6370c64 Thanks, Nir

1 0

ovirt-engine has been tagged (ovirt-engine-4.3.3.5)
by Tal Nisan 16 Apr '19

16 Apr '19

1 0

Re: Problem on host deployment from engine
by Nir Soffer 16 Apr '19

16 Apr '19

On Mon, Apr 15, 2019, 14:59 Amit Bawer <abawer(a)redhat.com> wrote: > Hello Didi & Sandro, > > I have encountered following issue when attempting to deploy a host from > the engine management. > > Engine: Fedora 28 > Host: CentOS 7.6.1810 > > engine.log error: > > 2019-04-14 14:08:35,578+03 INFO > [org.ovirt.engine.core.uutils.ssh.SSHDialog] > (EE-ManagedThreadFactory-engine-Thread-2) [628278a7] SSH execute ' > root(a)10.35.0.229' 'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp > -d -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null > 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp > -C "${MYTMP}" -x && "${MYTMP}"/ovirt-host-deploy > DIALOG/dialect=str:machine DIALOG/customization=bool:True' > 2019-04-14 14:08:35,670+03 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (VdsDeploy) [628278a7] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), An > error has occurred during installation of Host host1: Python is required > but missing. > 2019-04-14 14:08:35,688+03 ERROR > [org.ovirt.engine.core.uutils.ssh.SSHDialog] > (EE-ManagedThreadFactory-engine-Thread-2) [628278a7] SSH error running > command root(a)10.35.0.229:'umask 0077; MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" > mktemp -d -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; tar > --warning=no-timestamp -C "${MYTMP}" -x && "${MYTMP}"/ovirt-host-deploy > DIALOG/dialect=str:machine DIALOG/customization=bool:True': IOException: > Command returned failure code 1 during SSH session 'root(a)10.35.0.229' > > > I managed to resolve it manually by installing following rpms over the > host machine before reattempting to deploy again the host from the engine > management: > > python2-otopi > python2-ovirt-host-deploy > > I should mention that both engine and host were built from git master > branch and not installed using the release rpms themselves, however Nir can > also testify there is an issue when trying to deploy a host from Fedora > engines (29 in Nir's case and 28 in my case). > > Thanks, > Amit > Adding devel > >

3 2

ovirt-engine has been tagged (ovirt-engine-4.2.8.7)
by Tal Nisan 15 Apr '19

15 Apr '19

1 0

4.2 HC suite - missing sanlock-lib 3.7.1 dependency
by Sahina Bose 15 Apr '19

15 Apr '19

The 4.2 HC suite is failing on missing dependencies Error: Package: python2-sanlock-3.7.1-1.el7.x86_64 (alocalsync) Requires: sanlock-lib = 3.7.1-1.el7 Installing: sanlock-lib-3.6.0-1.el7.x86_64 (alocalsync) sanlock-lib = 3.6.0-1.el7 Any recent changes here? On Sat, Apr 13, 2019 at 7:10 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ > Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/852/ > Build Number: 852 > Build Status: Still Failing > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #850 > [Dominik Holler] network-suite-4.2: Skip test to for vnic profile live update > > > Changes for Build #851 > [Martin Perina] common: Really enable debug logging for engine > > [Simone Tiraboschi] Skip he-basic-role-remote-suite-4.2 > > [Daniel Belenky] mock_configs: update rawhide releasever > > [Daniel Belenky] stdci_slaves: add timeouts to loader node > > > Changes for Build #852 > [Ondra Machacek] ansible_suite: Update datacenter version > > > > > ----------------- > Failed Tests: > ----------------- > No tests ran.

3 5

Fails to enter Import screen using the current master branch
by Steven Rosenberg 14 Apr '19

14 Apr '19

We found an issue where entering the Import functionality within the VM screen fails on ovirt-engine with an error message of 500. The link for the screen shot is as follows: https://imgur.com/a/AadtU1u Please advise if others have seen this issue as well and if there is a fix. With Best Regards. Steven Rosenberg.

5 11

[ OST Failure Report ] [ oVirt 4.2 (vdsm-jsonrpc-java) ] [ 12-04-2019 ] [ 002_bootstrap.add_dc ]
by Dafna Ron 14 Apr '19

14 Apr '19

Hi, We had a failure on both basic and upgrade suites. The issue seems to be in initialize engine with the below error Root cause change: https://gerrit.ovirt.org/#/c/99278/ - Purge old events and EventPublisher should handle exceptions Logs can be found here: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4217/artifact/ba… error: 2019-04-12 03:36:25,571-04 ERROR [org.ovirt.engine.core.bll.Backend] (ServerService Thread Pool -- 44) [] Error during initialization: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.ovirt.engine.core.vdsbroker.monitoring.VmMigrationProgressMonitoring.subscribe() on org.ovirt.engine.core.vdsbroker.monitoring.VmMigrationProgressMonitoring@c22d2ea at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:85) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:66) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:122) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:162) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.contexts.AbstractContext.get(AbstractContext.java:96) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:140) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:700) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:252) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:114) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.bll.ServiceLoader.load(ServiceLoader.java:34) [bll.jar:] at org.ovirt.engine.core.bll.Backend.initialize(Backend.java:312) [bll.jar:] at org.ovirt.engine.core.bll.Backend.create(Backend.java:195) [bll.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_201] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_201] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_201] at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:78) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:125) at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:111) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) [weld-ejb-3.0.5.Final.jar:3.0.5.Final] at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:53) [wildfly-weld-14.0.1.Final.jar:14.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) [wildfly-weld-14.0.1.Final.jar:14.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.ComponentInstantiatorInterceptor.processInvocation(ComponentInstantiatorInterceptor.java:74) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.interceptors.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:105) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:216) [wildfly-ejb3-14.0.1.Final.jar:14.0.1.Final] at org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:418) [wildfly-ejb3-14.0.1.Final.jar:14.0.1.Final] at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:70) [wildfly-ejb3-14.0.1.Final.jar:14.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) [wildfly-weld-14.0.1.Final.jar:14.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-14.0.1.Final.jar:14.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) [wildfly-ee-14.0.1.Final.jar:14.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25) [wildfly-ejb3-14.0.1.Final.jar:14.0.1.Final] at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161) at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134) at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:127) [wildfly-ejb3-14.0.1.Final.jar:14.0.1.Final] at org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) [wildfly-ejb3-14.0.1.Final.jar:14.0.1.Final] at org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_201] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_201] at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_201] at org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_201] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_201] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_201] at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:83) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] ... 69 more Caused by: java.lang.NoSuchMethodError: org.ovirt.vdsm.jsonrpc.client.reactors.ReactorFactory.getWorker(I)Lorg/ovirt/vdsm/jsonrpc/client/internal/ResponseWorker; at org.ovirt.engine.core.vdsbroker.ResourceManager.subscribe(ResourceManager.java:458) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.subscribe$$super(Unknown Source) [vdsbroker.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_201] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_201] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_201] at org.jboss.weld.interceptor.proxy.TerminalAroundInvokeInvocationContext.proceedInternal(TerminalAroundInvokeInvocationContext.java:51) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:78) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.common.di.interceptor.LoggingInterceptor.apply(LoggingInterceptor.java:12) [common.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_201] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_201] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_201] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_201] at org.jboss.weld.interceptor.reader.SimpleInterceptorInvocation$SimpleMethodInvocation.invoke(SimpleInterceptorInvocation.java:73) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeAroundInvoke(InterceptorMethodHandler.java:84) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:72) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:56) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:79) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:68) [weld-core-impl-3.0.5.Final.jar:3.0.5.Final] at org.ovirt.engine.core.vdsbroker.ResourceManager$Proxy$_$$_WeldSubclass.subscribe(Unknown Source) [vdsbroker.jar:] at org.ovirt.engine.core.vdsbroker.monitoring.VmMigrationProgressMonitoring.subscribe(VmMigrationProgressMonitoring.java:35) [vdsbroker.jar:] ... 74 more 2019-04-12 03:36:46,992-04 DEBUG [org.ovirt.engine.core.utils.servlet.LocaleFilter] (default task-1) [] Incoming locale 'en-US'. Filter determined locale to be 'en-US' 2019-04-12 03:36:47,025-04 DEBUG [org.ovirt.engine.core.utils.servlet.LocaleFilter] (default task-1) [] Incoming locale 'en-US'. Filter determined locale to be 'en-US' 2019-04-12 03:36:47,027-04 DEBUG [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-1) [] Exponent is 65537 (010001). 2019-04-12 03:36:47,027-04 DEBUG [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-1) [] Modulus is 23045455587502151351307881395746676489582617487444460434296505697360842634378900404903793405238811523302482543003054056200741987458008963931649820493880963560986441075262188689772713221069929429876133085702357731148902133770193496183003052020349333463043013537857088409307780071693644400706574082881179894409681722899845950989200033040393214136788457749540203592306287581368470141041245429472069137351244033201424938951360962572394606552585936959608039675862808386819256128109473508142431203907117802195732456069118309327167040542073925080491412451765973629566066094113148306929852301896069383522789589872834454425973 (010001).

1 1

vdsm has been tagged (v4.20.48)
by Milan Zamazal 11 Apr '19

11 Apr '19

1 0

GetVdsHooksByIdQuery comes back with NullPointerException
by Dafna Ron 11 Apr '19

11 Apr '19

Hi, This is a code issue 100%, I am not sure which team sends the query but this needs to be addressed. I think it would also help debug/fix the issue with the random failure of get_host_hooks which was already reported and communicated on in the list. Can someone from infra/network please look at the query and see what is the cause of the NPE? Thanks, Dafna

2 2