- Infra - oVirt List Archives

[CQ]: 88504,1 (ovirt-engine-metrics) failed "ovirt-4.2" system tests
by oVirt Jenkins 05 Mar '18

05 Mar '18

Change 88504,1 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/88504/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1036/

1 0

[CQ]: 88038, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88038,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (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 88402,4 (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/88038/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88402/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6054/

1 0

[CQ]: 88470, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88470,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (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 88402,4 (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/88470/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88402/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6050/

1 0

hosted-engine ovirt-system-tests
by Yedidyah Bar David 05 Mar '18

05 Mar '18

Hi all, Recently I have been pushing various patches to OST in order to verify specific bugs/fixes I was working on, using them with the "manual" jenkins job but with no immediate intention to get them merged. Main reason is that it's not clear what's the best approach to get such tests merged. Do we want a new suite? How often does it run? How long does it take? Do we have enough resources? etc. Do we have plans re this? Bugs/tickets/etc.? Do we want to do something? Specifically, do we want (eventually) many more suites? This seems unmanageable. A few suites, perhaps (also) using lago snapshots? Didn't try that myself, might be useful and relevant. Some examples: https://gerrit.ovirt.org/79203 https://gerrit.ovirt.org/79215 https://gerrit.ovirt.org/84813 https://gerrit.ovirt.org/88201 https://gerrit.ovirt.org/88234 And current one - this and the next ones in the stack: https://gerrit.ovirt.org/88331 Best regards, -- Didi

3 3

[JIRA] (OVIRT-1916) ovirt site doesn't render/publish the latest blog post
by eyal edri (oVirt JIRA) 05 Mar '18

05 Mar '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1916?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-1916: ---------------------------------- Can you please check? On Mon, Mar 5, 2018 at 4:25 PM, Roy Golan (oVirt JIRA) < -- Eyal edri 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) > ovirt site doesn't render/publish the latest blog post > ------------------------------------------------------ > > Key: OVIRT-1916 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1916 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: infra > > on March 4th this blog post was merged, but it is still not appearing under > Blogs. Please check what's wrongj > [1] https://github.com/oVirt/ovirt-site/pull/1529 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

1 0

[JIRA] (OVIRT-1916) ovirt site doesn't render/publish the latest blog post
by Roy Golan (oVirt JIRA) 05 Mar '18

05 Mar '18

Roy Golan created OVIRT-1916: -------------------------------- Summary: ovirt site doesn't render/publish the latest blog post Key: OVIRT-1916 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1916 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Roy Golan Assignee: infra on March 4th this blog post was merged, but it is still not appearing under Blogs. Please check what's wrongj [1] https://github.com/oVirt/ovirt-site/pull/1529 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100081)

2 1

[CQ]: 88438, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88438,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (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 88402,4 (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/88438/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88402/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6045/

1 0

[ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 05-03-2018 ] [ 006_migrations.migrate_vm ]
by Dafna Ron 05 Mar '18

05 Mar '18

Hi, We have a failure in OST on test 006_migrations.migrate_vm. >From what I can see, the migration succeeded but because there was a KeyError: 'cpuUsage' engine assume the v is down and tries to retry migration. the re-try fails with vm already exists. *Link and headline of suspected patches: *Failed change: *https://gerrit.ovirt.org/#/c/88432/2 <https://gerrit.ovirt.org/#/c/88432/2> - * *engine : Events coming too soon on refresh caps* *CQ reported this as root ca*use but I don't think its related as well: *https://gerrit.ovirt.org/#/c/88404/ <https://gerrit.ovirt.org/#/c/88404/> - * *core: Auto SD selection on template version update* *Link to Job:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1021/ <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1021/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1021/artifa… <http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1021/artifact/>(Relevant) error snippet from the log: <error>* *migration starts and finishs *but fails on vm state on eyError: 'cpuUsage' *2018-03-05 05:21:33,269-0500 INFO (jsonrpc/3) [api.virt] START migrate(params={u'incomingLimit': 2, u'tunneled': u'false', u'dstqemu': u'192.0.3.2', u'autoConverge': u'false', u'src': u'lago-basic-suite-4-2-host-0', u'enableGuestEvents': False, u'dst': u'lago-basic-suite-4-2-host-1:54321', u'vmId': u'a80596a2-f57b-4878-adc3-772363e42783', u'abortOnError': u'true', u'outgoingLimit': 2, u'compressed': u'false', u'method': u'online'}) from=::ffff:192.168.200.2,42452, flow_id=123f5fd3-81a4-4ba9-9034-525674696629, vmId=a80596a2-f57b-4878-adc3-772363e42783 (api:46)2018-03-05 05:21:33,271-0500 INFO (jsonrpc/3) [api.virt] FINISH migrate return={'status': {'message': 'Migration in progress', 'code': 0}, 'progress': 0} from=::ffff:192.168.200.2,42452, flow_id=123f5fd3-81a4-4ba9-9034-525674696629, vmId=a80596a2-f57b-4878-adc3-772363e42783 (api:52)2018-03-05 05:21:33,271-0500 INFO (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC call VM.migrate succeeded in 0.00 seconds (__init__:573)2018-03-05 05:21:33,473-0500 INFO (monitor/bd2f874) [IOProcessClient] Closing client ioprocess-0 (__init__:583)2018-03-05 05:21:34,936-0500 INFO (migsrc/a80596a2) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') Creation of destination VM took: 1 seconds (migration:473)2018-03-05 05:21:34,936-0500 INFO (migsrc/a80596a2) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') starting migration to qemu+tls://lago-basic-suite-4-2-host-1/system with miguri tcp://192.0.3.2 <http://192.0.3.2> (migration:502)2018-03-05 05:21:36,356-0500 INFO (jsonrpc/7) [api.host] START getAllVmStats() from=::ffff:192.168.200.2,42452 (api:46)2018-03-05 05:21:36,359-0500 INFO (jsonrpc/7) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:192.168.200.2,42452 (api:52)2018-03-05 05:21:36,361-0500 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:573)2018-03-05 05:21:38,861-0500 INFO (libvirt/events) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') CPU stopped: onSuspend (vm:6063)2018-03-05 05:21:40,109-0500 WARN (periodic/0) [virt.periodic.VmDispatcher] could not run <class 'vdsm.virt.periodic.DriveWatermarkMonitor'> on ['a80596a2-f57b-4878-adc3-772363e42783'] (periodic:323)2018-03-05 05:21:40,109-0500 INFO (migsrc/a80596a2) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') migration took 6 seconds to complete (migration:514)2018-03-05 05:21:40,110-0500 INFO (migsrc/a80596a2) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') Changed state to Down: Migration succeeded (code=4) (vm:1677)2018-03-05 05:21:40,116-0500 INFO (migsrc/a80596a2) [virt.vm] (vmId='a80596a2-f57b-4878-adc3-772363e42783') Stopping connection (guestagent:438)2018-03-05 05:21:41,118-0500 WARN (periodic/3) [virt.periodic.VmDispatcher] could not run <class 'vdsm.virt.periodic.DriveWatermarkMonitor'> on ['a80596a2-f57b-4878-adc3-772363e42783'] (periodic:323)2018-03-05 05:21:42,063-0500 WARN (periodic/2) [virt.vmstats] Missing stat: 'balloon.current' for vm a80596a2-f57b-4878-adc3-772363e42783 (vmstats:552)2018-03-05 05:21:42,064-0500 ERROR (periodic/2) [virt.vmstats] VM metrics collection failed (vmstats:264)Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/virt/vmstats.py", line 197, in send_metrics data[prefix + '.cpu.usage'] = stat['cpuUsage']KeyError: 'cpuUsage'* *</error>*

1 0

[CQ]: 88323, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

A system test invoked by the "ovirt-master" change queue including change 88323,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (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 88402,4 (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/88323/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88402/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/6044/

1 0

[CQ]: 88432, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Mar '18

05 Mar '18

A system test invoked by the "ovirt-4.2" change queue including change 88432,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88404,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 88404,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/88432/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/88404/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1021/

1 0