Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-11 Thread Tomas Jelinek 
On Fri, Jan 12, 2018 at 8:18 AM, Yaniv Kaul  wrote:

>
>
> On Fri, Jan 12, 2018 at 9:06 AM, Yaniv Kaul  wrote:
>
>> See[1] - do we need to update Lago / Lago OST plugin?
>>
>
> Something like https://github.com/lago-project/lago-ost-plugin/pull/31
> perhaps (not tested, don't have the HW).
>

yes, seems like that should do the trick.


> Y.
>
>
>> Error Message
>>
>> Unsupported CPU model: Haswell-noTSX-IBRS. Supported models: 
>> IvyBridge,Westmere,Skylake,Penryn,Haswell,Broadwell,Nehalem,Skylake-Client,Broadwell-noTSX,Conroe,SandyBridge,Haswell-noTSX
>>
>> Stacktrace
>>
>> Traceback (most recent call last):
>>   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 129, in 
>> wrapped_test
>> test()
>>   File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in 
>> wrapper
>> return func(get_test_prefix(), *args, **kwargs)
>>   File 
>> "/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py",
>>  line 277, in add_cluster
>> add_cluster_4(prefix)
>>   File 
>> "/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py",
>>  line 305, in add_cluster_4
>> cpu_family = prefix.virt_env.get_ovirt_cpu_family()
>>   File "/usr/lib/python2.7/site-packages/ovirtlago/virt.py", line 151, in 
>> get_ovirt_cpu_family
>> ','.join(cpu_map[host.cpu_vendor].iterkeys())
>> RuntimeError: Unsupported CPU model: Haswell-noTSX-IBRS. Supported models: 
>> IvyBridge,Westmere,Skylake,Penryn,Haswell,Broadwell,Nehalem,Skylake-Client,Broadwell-noTSX,Conroe,SandyBridge,Haswell-noTSX
>>
>>
>>
>> Y.
>>
>> [1] 
>> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/3498/testReport/junit/(root)/002_bootstrap/add_cluster/
>>
>>
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-11 Thread Yaniv Kaul 
On Fri, Jan 12, 2018 at 9:06 AM, Yaniv Kaul  wrote:

> See[1] - do we need to update Lago / Lago OST plugin?
>

Something like https://github.com/lago-project/lago-ost-plugin/pull/31
perhaps (not tested, don't have the HW).
Y.


> Error Message
>
> Unsupported CPU model: Haswell-noTSX-IBRS. Supported models: 
> IvyBridge,Westmere,Skylake,Penryn,Haswell,Broadwell,Nehalem,Skylake-Client,Broadwell-noTSX,Conroe,SandyBridge,Haswell-noTSX
>
> Stacktrace
>
> Traceback (most recent call last):
>   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 129, in 
> wrapped_test
> test()
>   File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in 
> wrapper
> return func(get_test_prefix(), *args, **kwargs)
>   File 
> "/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py",
>  line 277, in add_cluster
> add_cluster_4(prefix)
>   File 
> "/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py",
>  line 305, in add_cluster_4
> cpu_family = prefix.virt_env.get_ovirt_cpu_family()
>   File "/usr/lib/python2.7/site-packages/ovirtlago/virt.py", line 151, in 
> get_ovirt_cpu_family
> ','.join(cpu_map[host.cpu_vendor].iterkeys())
> RuntimeError: Unsupported CPU model: Haswell-noTSX-IBRS. Supported models: 
> IvyBridge,Westmere,Skylake,Penryn,Haswell,Broadwell,Nehalem,Skylake-Client,Broadwell-noTSX,Conroe,SandyBridge,Haswell-noTSX
>
>
>
> Y.
>
> [1] 
> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/3498/testReport/junit/(root)/002_bootstrap/add_cluster/
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] OST Regression in add cluster (IBRS related)

2018-01-11 Thread Yaniv Kaul 
See[1] - do we need to update Lago / Lago OST plugin?
Error Message

Unsupported CPU model: Haswell-noTSX-IBRS. Supported models:
IvyBridge,Westmere,Skylake,Penryn,Haswell,Broadwell,Nehalem,Skylake-Client,Broadwell-noTSX,Conroe,SandyBridge,Haswell-noTSX

Stacktrace

Traceback (most recent call last):
  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
129, in wrapped_test
test()
  File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
59, in wrapper
return func(get_test_prefix(), *args, **kwargs)
  File 
"/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py",
line 277, in add_cluster
add_cluster_4(prefix)
  File 
"/home/jenkins/workspace/ovirt-system-tests_master_check-patch-el7-x86_64/ovirt-system-tests/basic-suite-master/test-scenarios/002_bootstrap.py",
line 305, in add_cluster_4
cpu_family = prefix.virt_env.get_ovirt_cpu_family()
  File "/usr/lib/python2.7/site-packages/ovirtlago/virt.py", line 151,
in get_ovirt_cpu_family
','.join(cpu_map[host.cpu_vendor].iterkeys())
RuntimeError: Unsupported CPU model: Haswell-noTSX-IBRS. Supported
models: 
IvyBridge,Westmere,Skylake,Penryn,Haswell,Broadwell,Nehalem,Skylake-Client,Broadwell-noTSX,Conroe,SandyBridge,Haswell-noTSX



Y.

[1] 
http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/3498/testReport/junit/(root)/002_bootstrap/add_cluster/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [VDSM] loop device tests fail again on jenkins

2018-01-11 Thread Nir Soffer 
On Thu, Jan 11, 2018 at 9:08 PM Yuval Turgeman  wrote:

> from ovirt-node-ng:
>
> build-artifacts.sh:  seq 0 9 | xargs -I {} mknod /dev/loop{} b 7 {} || :
>

Thanks, will try that.


>
>
> On Thu, Jan 11, 2018 at 8:38 PM, Nir Soffer  wrote:
>
>> On Thu, Jan 11, 2018 at 8:31 PM Barak Korren  wrote:
>>
>>> I thought I explained this before.
>>>
>>> Writing to losetup from inside mock gets you a device outside mock that
>>> is invisible inside.
>>>
>>
>> How the tests work 99.9% of the time?
>>
>>
>>> The way to solve this is to run mknod a few times to get the needed
>>> device files.
>>>
>>> You can see examples of this in the ovirt-node build scripts.
>>>
>>
>> "git grep mknod" in ovirt-node source does not show anything.
>>
>>
>>>
>>> Barak Korren
>>> bkor...@redhat.com
>>> RHCE, RHCi, RHV-DevOps Team
>>> https://ifireball.wordpress.com/
>>>
>>> בתאריך 11 בינו׳ 2018 04:35 PM,‏ "Nir Soffer"  כתב:
>>>
>>> We have random failures of loop device tests on jenkins (see example
 bellow).

 Barak commented that losetup -f /path does not work sometimes in the CI
 but I don't recall what it the alternative way to get a loop device.

 We need a reliable way to create a loop device for vdsm tests. What
 is the recommended way to do this?

 Until we have a reliable solution I'm going to mark this test as broken
 on ovirt CI:
 https://gerrit.ovirt.org/#/c/86241/

 Please report if you see other tests fail with this error - typically:

 Error: Command ['losetup', '--find', '--show', '/tmp/tmp17Wqri/file'] 
 failed with rc=1 out='' err='losetup: /tmp/tmp17Wqri/file: failed to set 
 up loop device: No such file or directory\n'



 http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/20862/consoleFull

 *00:05:48.766* 
 ==*00:05:48.766*
  ERROR: test_attach_detach_manually 
 (loopback_test.TestDevice)*00:05:48.767* 
 --*00:05:48.767*
  Traceback (most recent call last):*00:05:48.767*   File 
 "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/testValidation.py",
  line 191, in wrapper*00:05:48.768* return f(*args, 
 **kwargs)*00:05:48.768*   File 
 "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/loopback_test.py",
  line 56, in test_attach_detach_manually*00:05:48.768* 
 device.attach()*00:05:48.768*   File 
 "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/loopback.py",
  line 56, in attach*00:05:48.769* raise cmdutils.Error(cmd, rc, out, 
 err)*00:05:48.769* Error: Command ['losetup', '--find', '--show', 
 '/tmp/tmp17Wqri/file'] failed with rc=1 out='' err='losetup: 
 /tmp/tmp17Wqri/file: failed to set up loop device: No such file or 
 directory\n'*00:05:48.770*  >> begin captured logging 
 << *00:05:48.770* 2018-01-11 13:42:45,676 DEBUG 
 (MainThread) [root] /usr/bin/taskset --cpu-list 0-1 losetup --find --show 
 /tmp/tmp17Wqri/file (cwd None) (commands:65)*00:05:48.771* 2018-01-11 
 13:42:45,733 DEBUG (MainThread) [root] FAILED:  = 'losetup: 
 /tmp/tmp17Wqri/file: failed to set up loop device: No such file or 
 directory\n';  = 1 (commands:86)*00:05:48.772* - 
 >> end captured logging << -



>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [VDSM] loop device tests fail again on jenkins

2018-01-11 Thread Yuval Turgeman 
from ovirt-node-ng:

build-artifacts.sh:  seq 0 9 | xargs -I {} mknod /dev/loop{} b 7 {} || :


On Thu, Jan 11, 2018 at 8:38 PM, Nir Soffer  wrote:

> On Thu, Jan 11, 2018 at 8:31 PM Barak Korren  wrote:
>
>> I thought I explained this before.
>>
>> Writing to losetup from inside mock gets you a device outside mock that
>> is invisible inside.
>>
>
> How the tests work 99.9% of the time?
>
>
>> The way to solve this is to run mknod a few times to get the needed
>> device files.
>>
>> You can see examples of this in the ovirt-node build scripts.
>>
>
> "git grep mknod" in ovirt-node source does not show anything.
>
>
>>
>> Barak Korren
>> bkor...@redhat.com
>> RHCE, RHCi, RHV-DevOps Team
>> https://ifireball.wordpress.com/
>>
>> בתאריך 11 בינו׳ 2018 04:35 PM,‏ "Nir Soffer"  כתב:
>>
>> We have random failures of loop device tests on jenkins (see example
>>> bellow).
>>>
>>> Barak commented that losetup -f /path does not work sometimes in the CI
>>> but I don't recall what it the alternative way to get a loop device.
>>>
>>> We need a reliable way to create a loop device for vdsm tests. What
>>> is the recommended way to do this?
>>>
>>> Until we have a reliable solution I'm going to mark this test as broken
>>> on ovirt CI:
>>> https://gerrit.ovirt.org/#/c/86241/
>>>
>>> Please report if you see other tests fail with this error - typically:
>>>
>>> Error: Command ['losetup', '--find', '--show', '/tmp/tmp17Wqri/file'] 
>>> failed with rc=1 out='' err='losetup: /tmp/tmp17Wqri/file: failed to set up 
>>> loop device: No such file or directory\n'
>>>
>>>
>>> http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-
>>> x86_64/20862/consoleFull
>>>
>>> *00:05:48.766* 
>>> ==*00:05:48.766*
>>>  ERROR: test_attach_detach_manually 
>>> (loopback_test.TestDevice)*00:05:48.767* 
>>> --*00:05:48.767*
>>>  Traceback (most recent call last):*00:05:48.767*   File 
>>> "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/testValidation.py",
>>>  line 191, in wrapper*00:05:48.768* return f(*args, 
>>> **kwargs)*00:05:48.768*   File 
>>> "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/loopback_test.py",
>>>  line 56, in test_attach_detach_manually*00:05:48.768* 
>>> device.attach()*00:05:48.768*   File 
>>> "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/loopback.py",
>>>  line 56, in attach*00:05:48.769* raise cmdutils.Error(cmd, rc, out, 
>>> err)*00:05:48.769* Error: Command ['losetup', '--find', '--show', 
>>> '/tmp/tmp17Wqri/file'] failed with rc=1 out='' err='losetup: 
>>> /tmp/tmp17Wqri/file: failed to set up loop device: No such file or 
>>> directory\n'*00:05:48.770*  >> begin captured logging 
>>> << *00:05:48.770* 2018-01-11 13:42:45,676 DEBUG 
>>> (MainThread) [root] /usr/bin/taskset --cpu-list 0-1 losetup --find --show 
>>> /tmp/tmp17Wqri/file (cwd None) (commands:65)*00:05:48.771* 2018-01-11 
>>> 13:42:45,733 DEBUG (MainThread) [root] FAILED:  = 'losetup: 
>>> /tmp/tmp17Wqri/file: failed to set up loop device: No such file or 
>>> directory\n';  = 1 (commands:86)*00:05:48.772* - >> 
>>> end captured logging << -
>>>
>>>
>>>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [VDSM] loop device tests fail again on jenkins

2018-01-11 Thread Nir Soffer 
On Thu, Jan 11, 2018 at 8:31 PM Barak Korren  wrote:

> I thought I explained this before.
>
> Writing to losetup from inside mock gets you a device outside mock that is
> invisible inside.
>

How the tests work 99.9% of the time?


> The way to solve this is to run mknod a few times to get the needed device
> files.
>
> You can see examples of this in the ovirt-node build scripts.
>

"git grep mknod" in ovirt-node source does not show anything.


>
> Barak Korren
> bkor...@redhat.com
> RHCE, RHCi, RHV-DevOps Team
> https://ifireball.wordpress.com/
>
> בתאריך 11 בינו׳ 2018 04:35 PM,‏ "Nir Soffer"  כתב:
>
> We have random failures of loop device tests on jenkins (see example
>> bellow).
>>
>> Barak commented that losetup -f /path does not work sometimes in the CI
>> but I don't recall what it the alternative way to get a loop device.
>>
>> We need a reliable way to create a loop device for vdsm tests. What
>> is the recommended way to do this?
>>
>> Until we have a reliable solution I'm going to mark this test as broken
>> on ovirt CI:
>> https://gerrit.ovirt.org/#/c/86241/
>>
>> Please report if you see other tests fail with this error - typically:
>>
>> Error: Command ['losetup', '--find', '--show', '/tmp/tmp17Wqri/file'] failed 
>> with rc=1 out='' err='losetup: /tmp/tmp17Wqri/file: failed to set up loop 
>> device: No such file or directory\n'
>>
>>
>>
>> http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/20862/consoleFull
>>
>> *00:05:48.766* 
>> ==*00:05:48.766*
>>  ERROR: test_attach_detach_manually (loopback_test.TestDevice)*00:05:48.767* 
>> --*00:05:48.767*
>>  Traceback (most recent call last):*00:05:48.767*   File 
>> "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/testValidation.py",
>>  line 191, in wrapper*00:05:48.768* return f(*args, 
>> **kwargs)*00:05:48.768*   File 
>> "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/loopback_test.py",
>>  line 56, in test_attach_detach_manually*00:05:48.768* 
>> device.attach()*00:05:48.768*   File 
>> "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/loopback.py",
>>  line 56, in attach*00:05:48.769* raise cmdutils.Error(cmd, rc, out, 
>> err)*00:05:48.769* Error: Command ['losetup', '--find', '--show', 
>> '/tmp/tmp17Wqri/file'] failed with rc=1 out='' err='losetup: 
>> /tmp/tmp17Wqri/file: failed to set up loop device: No such file or 
>> directory\n'*00:05:48.770*  >> begin captured logging << 
>> *00:05:48.770* 2018-01-11 13:42:45,676 DEBUG 
>> (MainThread) [root] /usr/bin/taskset --cpu-list 0-1 losetup --find --show 
>> /tmp/tmp17Wqri/file (cwd None) (commands:65)*00:05:48.771* 2018-01-11 
>> 13:42:45,733 DEBUG (MainThread) [root] FAILED:  = 'losetup: 
>> /tmp/tmp17Wqri/file: failed to set up loop device: No such file or 
>> directory\n';  = 1 (commands:86)*00:05:48.772* - >> 
>> end captured logging << -
>>
>>
>>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [VDSM] loop device tests fail again on jenkins

2018-01-11 Thread Barak Korren 
I thought I explained this before.

Writing to losetup from inside mock gets you a device outside mock that is
invisible inside.

The way to solve this is to run mknod a few times to get the needed device
files.

You can see examples of this in the ovirt-node build scripts.

Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/

בתאריך 11 בינו׳ 2018 04:35 PM,‏ "Nir Soffer"  כתב:

> We have random failures of loop device tests on jenkins (see example
> bellow).
>
> Barak commented that losetup -f /path does not work sometimes in the CI
> but I don't recall what it the alternative way to get a loop device.
>
> We need a reliable way to create a loop device for vdsm tests. What
> is the recommended way to do this?
>
> Until we have a reliable solution I'm going to mark this test as broken
> on ovirt CI:
> https://gerrit.ovirt.org/#/c/86241/
>
> Please report if you see other tests fail with this error - typically:
>
> Error: Command ['losetup', '--find', '--show', '/tmp/tmp17Wqri/file'] failed 
> with rc=1 out='' err='losetup: /tmp/tmp17Wqri/file: failed to set up loop 
> device: No such file or directory\n'
>
>
> http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-
> x86_64/20862/consoleFull
>
> *00:05:48.766* 
> ==*00:05:48.766*
>  ERROR: test_attach_detach_manually (loopback_test.TestDevice)*00:05:48.767* 
> --*00:05:48.767*
>  Traceback (most recent call last):*00:05:48.767*   File 
> "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/testValidation.py",
>  line 191, in wrapper*00:05:48.768* return f(*args, 
> **kwargs)*00:05:48.768*   File 
> "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/loopback_test.py",
>  line 56, in test_attach_detach_manually*00:05:48.768* 
> device.attach()*00:05:48.768*   File 
> "/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/loopback.py",
>  line 56, in attach*00:05:48.769* raise cmdutils.Error(cmd, rc, out, 
> err)*00:05:48.769* Error: Command ['losetup', '--find', '--show', 
> '/tmp/tmp17Wqri/file'] failed with rc=1 out='' err='losetup: 
> /tmp/tmp17Wqri/file: failed to set up loop device: No such file or 
> directory\n'*00:05:48.770*  >> begin captured logging << 
> *00:05:48.770* 2018-01-11 13:42:45,676 DEBUG (MainThread) 
> [root] /usr/bin/taskset --cpu-list 0-1 losetup --find --show 
> /tmp/tmp17Wqri/file (cwd None) (commands:65)*00:05:48.771* 2018-01-11 
> 13:42:45,733 DEBUG (MainThread) [root] FAILED:  = 'losetup: 
> /tmp/tmp17Wqri/file: failed to set up loop device: No such file or 
> directory\n';  = 1 (commands:86)*00:05:48.772* - >> 
> end captured logging << -
>
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [VDSM] loop device tests fail again on jenkins

2018-01-11 Thread Nir Soffer 
We have random failures of loop device tests on jenkins (see example
bellow).

Barak commented that losetup -f /path does not work sometimes in the CI
but I don't recall what it the alternative way to get a loop device.

We need a reliable way to create a loop device for vdsm tests. What
is the recommended way to do this?

Until we have a reliable solution I'm going to mark this test as broken
on ovirt CI:
https://gerrit.ovirt.org/#/c/86241/

Please report if you see other tests fail with this error - typically:

Error: Command ['losetup', '--find', '--show', '/tmp/tmp17Wqri/file']
failed with rc=1 out='' err='losetup: /tmp/tmp17Wqri/file: failed to
set up loop device: No such file or directory\n'


http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/20862/consoleFull

*00:05:48.766* 
==*00:05:48.766*
ERROR: test_attach_detach_manually
(loopback_test.TestDevice)*00:05:48.767*
--*00:05:48.767*
Traceback (most recent call last):*00:05:48.767*   File
"/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/testValidation.py",
line 191, in wrapper*00:05:48.768* return f(*args,
**kwargs)*00:05:48.768*   File
"/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/loopback_test.py",
line 56, in test_attach_detach_manually*00:05:48.768*
device.attach()*00:05:48.768*   File
"/home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64/vdsm/tests/loopback.py",
line 56, in attach*00:05:48.769* raise cmdutils.Error(cmd, rc,
out, err)*00:05:48.769* Error: Command ['losetup', '--find', '--show',
'/tmp/tmp17Wqri/file'] failed with rc=1 out='' err='losetup:
/tmp/tmp17Wqri/file: failed to set up loop device: No such file or
directory\n'*00:05:48.770*  >> begin captured
logging << *00:05:48.770* 2018-01-11 13:42:45,676
DEBUG (MainThread) [root] /usr/bin/taskset --cpu-list 0-1 losetup
--find --show /tmp/tmp17Wqri/file (cwd None)
(commands:65)*00:05:48.771* 2018-01-11 13:42:45,733 DEBUG (MainThread)
[root] FAILED:  = 'losetup: /tmp/tmp17Wqri/file: failed to set up
loop device: No such file or directory\n';  = 1
(commands:86)*00:05:48.772* - >> end captured
logging << -
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] ovirt-engine-metrics is now required for running host deploy

2018-01-11 Thread Eyal Edri 
Does it mean we need to update the reposync file in OST for it?

On Thu, Jan 4, 2018 at 4:16 PM, Shirly Radco  wrote:

> ​Hi,
>
> Please note, we plan to merge patch [1], which will add
> ovirt-engine-metrics
> package to requirements for engine development environment, because metrics
> setup will now be part of host deploy.
>
> You will need to install ovirt-engine-metrics rpm package or host deploy
> will fail.
>
> Minimal required package version: ovirt-engine-metrics-1.1.2-0.0
> .master.2018010100.el7.centos.noarch.rpm
>
>
> [1] https://gerrit.ovirt.org/#/c/84331/
>
> Best regards,
>
> --
>
> SHIRLY RADCO
>
> BI SeNIOR SOFTWARE ENGINEER
>
> Red Hat Israel 
> 
> TRIED. TESTED. TRUSTED. 
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>



-- 

Eyal edri


MANAGER

RHV DevOps

EMEA VIRTUALIZATION R&D


Red Hat EMEA 
 TRIED. TESTED. TRUSTED. 
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] vdsm stable branch maitainership

2018-01-11 Thread Yaniv Bronheim 
On Wed, Jan 10, 2018 at 6:04 PM Nir Soffer  wrote:

> On Wed, Jan 10, 2018 at 11:38 AM Francesco Romani 
> wrote:
>
>> On 01/09/2018 06:54 PM, Michal Skrivanek wrote:
>>
>>
>>
>> On 9 Jan 2018, at 18:48, Nir Soffer  wrote:
>>
>> On Tue, Jan 9, 2018 at 3:55 PM Adam Litke  wrote:
>>
>>> +1
>>>
>>> On Tue, Jan 9, 2018 at 8:17 AM, Francesco Romani 
>>> wrote:
>>>
 On 01/09/2018 12:43 PM, Dan Kenigsberg wrote:
 > Hello,
 >
 > I would like to nominate Milan Zamazal and Petr Horacek as maintainers
 > of vdsm stable branches. This job requires understanding of vdsm
 > packaging and code, a lot of attention to details and awareness of the
 > requirements of other components and teams.
 >
 > I believe that both Milan and Petr have these qualities. I am certain
 > they would work in responsive caution when merging and tagging patches
 > to the stable branches.
 >
 > vdsm maintainers, please confirm if you approve.

>>>
>> Why do we need 4 maintainers for the stable branch?
>>
>> Currently Yaniv and Francesco maintain this branch.
>>
>>
>> they both have quite a few other duties recently, and less and less time
>> to attend to vdsm
>> if it wasn’t so noticable for Francesco yet, then it is going to be quite
>> soon.
>>
>> I believe it makes sense to ramp up others before it happens.
>>
>>
>> I'd like to stress that I plan to float around as backup and to help
>> people during the ramp up phase
>> (and for any general advice/help that could be needed).
>>
>
> I see, the proposal was not clear before.
>
> +1 for Milan, I worked with him a lot and I'm sure he will do great job
>
> I never worked with Petr, but seems that everyone is happy, good enough
> for me.
>
> I think we need to keep Yaniv or someone else from the tlv office, so we
> have a way
> to push urgent patches on weekends or holidays when nobody is available in
> Brno.
>

I keep this hat whenever needed


> Nir
>


-- 
Yaniv Bronhaim.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] fc27 job failing on missing vmconsole

2018-01-11 Thread Viktor Mihajlovski 
On 07.01.2018 11:11, Barak Korren wrote:
[...]
> 
> I looked into what happened there.
> 
> It seems that Sandro added fc27 jobs a few weeks ago ago, and he also
> took the time to trigger the jobs manually to get an FC27 build.
> 
> The issue is that this is not enough to get a build to properly go
> through the automated test and release processes,
> 
> The CI system is build to respond on code changes. For most projects
> that is enough because new patches are merged frequently and as new
> jobs are added, patches show up soon after and trigger them.
> 
> The root cause for this issue is that the set of platforms a project
> targets is currently maintained separately from the project's source
> code, so adding a new target platform is not always manifest in a code
> change to the project. We're working on resolving this by making the
> set of target platform be specified in the project's own source code.
> This would eventually mean that adding a new target platfrom will
> always require a patch to the project.
> 
> For now, I've emulated a merge event on the latest patch to
> ovirt-vmconsole. This will cause the fc27 build (as well as others) to
> get recreated and pushed through the change-queue.
> 

I think we face a similar problem for the s390x builds of ovirt-host.
Looks like the last changes to ovirt-host have been done before the
s390x fc27 jobs have been merged, so there are no s390x RPMS in the
repository.
Could you or someone else trigger a full ovirt-host build?

-- 

Mit freundlichen Grüßen/Kind Regards
   Viktor Mihajlovski

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel