December 2016 - Infra - oVirt List Archives

Moving NGN system tests to fc24/fc25
by Eyal Edri 11 Dec '16

11 Dec '16

Hi, We're looking to move away from fc23 before it stops working, I see that the ngn system tests still uses it, do we know if it can move to fc24/fc25? I remember el7 wasn't possible when we moved it from fc22. [1] http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_4.0_image-ng… -- 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

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-931: ------------------------------------------------- [~gshinar] thanks for the quick debug, [~ederevea] can we have a list of "problematic hypervisors"? we might want to move them to Lago or production DC. > profile why ovirt-engine check-patch takes between 10-50 min > ------------------------------------------------------------- > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by Gil Shinar (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-931: ---------------------------------- I have checked two different slaves. One usually takes long 50~ minutes and the other one usually takes 10~ minutes. The one that takes 10~ minutes has 16 cores CPU and the one that takes 50~ minutes has two cores CPU. On top of that, some builds run dao tests and some don't (depend on files that had been changed. > profile why ovirt-engine check-patch takes between 10-50 min > ------------------------------------------------------------- > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4457 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 11 Dec '16

11 Dec '16

------=_Part_102_2066032100.1481459686602 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4457/, Build Number: 4457, Build Status: FAILURE ------=_Part_102_2066032100.1481459686602--

1 1

hot plug disk test failed on system tests
by Eyal Edri 11 Dec '16

11 Dec '16

FYI, We're seeing a single test 'add hotplug disk' failing recently on OST, the test only failed once on the jobs [1] and was fixed on its own after one run, but now I see it also on check-patch [2] jobs. Looking at the changelog, I can't find immediate suspects, and if this is a race it might make sense it got in at some point and didn't fail on the 1st time. Anyone can have a look to help debug this? it also failed once on 4.0 job. I see some exceptions on VDSM.LOG [3] [1] http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper… [2] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86… [3] 2016-12-11 04:51:19,055 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.getDeviceList succeeded in 0.39 seconds (__init__:515) 2016-12-11 04:51:19,106 INFO (jsonrpc/5) [dispatcher] Run and protect: getAllTasksInfo(spUUID=None, options=None) (logUtils:49) 2016-12-11 04:51:19,106 ERROR (jsonrpc/5) [storage.TaskManager.Task] (Task='ef8d6b6f-256c-4420-9998-bef8a140a20f') Unexpected error (task:870) Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 877, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 50, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 2193, in getAllTasksInfo allTasksInfo = self._pool.getAllTasksInfo() File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 77, in wrapper raise SecureError("Secured object is not in safe state") SecureError: Secured object is not in safe state 2016-12-11 04:51:19,109 INFO (jsonrpc/5) [storage.TaskManager.Task] (Task='ef8d6b6f-256c-4420-9998-bef8a140a20f') aborting: Task is aborted: u'Secured object is not in safe state' - code 100 (task:1175) 2016-12-11 04:51:19,109 ERROR (jsonrpc/5) [storage.Dispatcher] Secured object is not in safe state (dispatcher:80) Traceback (most recent call last): File "/usr/share/vdsm/storage/dispatcher.py", line 72, in wrapper result = ctask.prepare(func, *args, **kwargs) File "/usr/share/vdsm/storage/task.py", line 105, in wrapper return m(self, *a, **kw) File "/usr/share/vdsm/storage/task.py", line 1183, in prepare raise self.error second error: 2016-12-11 04:55:21,837 ERROR (libvirt/events) [vds] Error running VM callback (clientIF:543) Traceback (most recent call last): File "/usr/share/vdsm/clientIF.py", line 514, in dispatchLibvirtEvents v.onLibvirtLifecycleEvent(event, detail, None) File "/usr/share/vdsm/virt/vm.py", line 4318, in onLibvirtLifecycleEvent elif detail == libvirt.VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY: AttributeError: 'module' object has no attribute 'VIR_DOMAIN_EVENT_SUSPENDED_POSTCOPY' -- 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)

2 1

[JIRA] (OVIRT-926) check why 3.6 experimental job failed even if not error in shown on job
by Gil Shinar (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-926?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-926: ---------------------------------- [~ngoldin(a)redhat.com] These warning are coming from the emailext plugin I have used to send emails on failures/success. They have nothing to do with this issue IMO. > check why 3.6 experimental job failed even if not error in shown on job > ----------------------------------------------------------------------- > > Key: OVIRT-926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-926 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4322/ > [~gbenhaim@redhat.com][~ngoldin@redhat.com][~ederevea][~bkorren@redhat.com] any ideas? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

eyal edri [Administrator] created OVIRT-931: ----------------------------------------------- Summary: profile why ovirt-engine check-patch takes between 10-50 min Key: OVIRT-931 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: High Same job sometimes takes little as 10 min but sometimes high as 50 min. We need to understand why. http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-931) profile why ovirt-engine check-patch takes between 10-50 min
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-931?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-931: -------------------------------------------- Epic Link: OVIRT-400 > profile why ovirt-engine check-patch takes between 10-50 min > ------------------------------------------------------------- > > Key: OVIRT-931 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-931 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > Same job sometimes takes little as 10 min but sometimes high as 50 min. > We need to understand why. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/ > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/bui… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-930) check why ost 4.0 failed on vm run job even though not change was done
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

eyal edri [Administrator] created OVIRT-930: ----------------------------------------------- Summary: check why ost 4.0 failed on vm run job even though not change was done Key: OVIRT-930 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-930 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: eyal edri [Administrator] Assignee: infra Looks like false positive or race issue, but still needs to be debug for RCA. http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3389/consoleF… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-930) check why ost 4.0 failed on vm run job even though not change was done
by eyal edri [Administrator] (oVirt JIRA) 11 Dec '16

11 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-930?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-930: -------------------------------------------- Epic Link: OVIRT-400 > check why ost 4.0 failed on vm run job even though not change was done > ---------------------------------------------------------------------- > > Key: OVIRT-930 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-930 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > Looks like false positive or race issue, but still needs to be debug for RCA. > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3389/consoleF… -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0