Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-03 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-03 Thread Dan Kenigsberg 
On Tue, Apr 3, 2018 at 3:57 PM, Piotr Kliczewski  wrote:
> Dan,
>
> It looks like it was one of the calls triggered when vdsm was down:
>
> 2018-04-03 05:30:16,065-0400 INFO  (mailbox-hsm)
> [storage.MailBox.HsmMailMonitor] HSM_MailMonitor sending mail to SPM -
> ['/usr/bin/dd',
> 'of=/rhev/data-center/ddb765d2-2137-437d-95f8-c46dbdbc7711/mastersd/dom_md/inbox',
> 'iflag=fullblock', 'oflag=direct', 'conv=notrunc', 'bs=4096', 'count=1',
> 'seek=1'] (mailbox:387)
> 2018-04-03 05:31:22,441-0400 INFO  (MainThread) [vds] (PID: 20548) I am the
> actual vdsm 4.20.23-28.gitd11ed44.el7.centos lago-basic-suite-4-2-host-0
> (3.10.0-693.21.1.el7.x86_64) (vdsmd:149)
>
>
> which failed and caused timeout.
>
> Thanks,
> Piotr
>
> On Tue, Apr 3, 2018 at 1:57 PM, Dan Kenigsberg  wrote:
>>
>> On Tue, Apr 3, 2018 at 2:07 PM, Barak Korren  wrote:
>> > Test failed: [ 006_migrations.prepare_migration_attachments_ipv6 ]
>> >
>> > Link to suspected patches:
>> >
>> > (Patch seems unrelated - do we have sporadic communication issues
>> > arising in PST?)
>> > https://gerrit.ovirt.org/c/89737/1 - vdsm - automation: check-patch:
>> > attempt to install vdsm-gluster
>> >
>> > Link to Job:
>> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/
>> >
>> > Link to all logs:
>> >
>> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-006_migrations.py/
>> >
>> > Error snippet from log:
>> >
>> > 
>> >
>> > 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
>> > 78, in wrapper
>> > prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs
>> >   File
>> > "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/006_migrations.py",
>> > line 139, in prepare_migration_attachments_ipv6
>> > engine, host_service, MIGRATION_NETWORK, ip_configuration)
>> >   File
>> > "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test_utils/network_utils_v4.py",
>> > line 71, in modify_ip_config
>> > check_connectivity=True)
>> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
>> > line 36729, in setup_networks
>> > return self._internal_action(action, 'setupnetworks', None,
>> > headers, query, wait)
>> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
>> > 299, in _internal_action
>> > return future.wait() if wait else future
>> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
>> > 55, in wait
>> > return self._code(response)
>> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
>> > 296, in callback
>> > self._check_fault(response)
>> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
>> > 132, in _check_fault
>> > self._raise_error(response, body)
>> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
>> > 118, in _raise_error
>> > raise error
>> > Error: Fault reason is "Operation Failed". Fault detail is "[Network
>> > error during communication with the Host.]". HTTP response code is
>> > 400.
>>
>> The error occurred sometime in the interval
>>
>> 09:32:58 [basic-suit] @ Run test: 006_migrations.py:
>> 09:33:55 [basic-suit] Error occured, aborting
>>
>> and indeed
>>
>>
>> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-006_migrations.py/lago-basic-suite-4-2-engine/_var_log/ovirt-engine/engine.log/*view*/
>>
>> has Engine disconnected from the host at
>>
>> 2018-04-03 05:33:32,307-04 ERROR
>> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
>> (EE-ManagedThreadFactory-engineScheduled-Thread-39) [] Unable to
>> RefreshCapabilities: VDSNetworkException: VDSGenericException:
>> VDSNetworkException: Vds timeout occured
>>
>> Maybe Piotr can read more into it.

I should have thought of a down vdsm; but it was down because what
seems to be soft fencing

http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-006_migrations.py/lago-basic-suite-4-2-host-0/_var_log/messages/*view*/

Apr  3 05:30:01 lago-basic-suite-4-2-host-0 systemd: Started Session
46 of user root.
Apr  3 05:30:01 lago-basic-suite-4-2-host-0 systemd: Starting

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-03 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-03 Thread Piotr Kliczewski 
Dan,

It looks like it was one of the calls triggered when vdsm was down:

2018-04-03 05:30:16,065-0400 INFO  (mailbox-hsm)
[storage.MailBox.HsmMailMonitor] HSM_MailMonitor sending mail to SPM -
['/usr/bin/dd',
'of=/rhev/data-center/ddb765d2-2137-437d-95f8-c46dbdbc7711/mastersd/dom_md/inbox',
'iflag=fullblock', 'oflag=direct', 'conv=notrunc', 'bs=4096',
'count=1', 'seek=1'] (mailbox:387)
2018-04-03 05:31:22,441-0400 INFO  (MainThread) [vds] (PID: 20548) I
am the actual vdsm 4.20.23-28.gitd11ed44.el7.centos
lago-basic-suite-4-2-host-0 (3.10.0-693.21.1.el7.x86_64) (vdsmd:149)


which failed and caused timeout.

Thanks,
Piotr

On Tue, Apr 3, 2018 at 1:57 PM, Dan Kenigsberg  wrote:

> On Tue, Apr 3, 2018 at 2:07 PM, Barak Korren  wrote:
> > Test failed: [ 006_migrations.prepare_migration_attachments_ipv6 ]
> >
> > Link to suspected patches:
> >
> > (Patch seems unrelated - do we have sporadic communication issues
> > arising in PST?)
> > https://gerrit.ovirt.org/c/89737/1 - vdsm - automation: check-patch:
> > attempt to install vdsm-gluster
> >
> > Link to Job:
> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/
> >
> > Link to all logs:
> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/
> 1521/artifact/exported-artifacts/basic-suit-4.2-el7/
> test_logs/basic-suite-4.2/post-006_migrations.py/
> >
> > Error snippet from log:
> >
> > 
> >
> > 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
> > 78, in wrapper
> > prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs
> >   File "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/
> ovirt-system-tests/basic-suite-4.2/test-scenarios/006_migrations.py",
> > line 139, in prepare_migration_attachments_ipv6
> > engine, host_service, MIGRATION_NETWORK, ip_configuration)
> >   File "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/
> ovirt-system-tests/basic-suite-4.2/test_utils/network_utils_v4.py",
> > line 71, in modify_ip_config
> > check_connectivity=True)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
> > line 36729, in setup_networks
> > return self._internal_action(action, 'setupnetworks', None,
> > headers, query, wait)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> > 299, in _internal_action
> > return future.wait() if wait else future
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> > 55, in wait
> > return self._code(response)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> > 296, in callback
> > self._check_fault(response)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> > 132, in _check_fault
> > self._raise_error(response, body)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> > 118, in _raise_error
> > raise error
> > Error: Fault reason is "Operation Failed". Fault detail is "[Network
> > error during communication with the Host.]". HTTP response code is
> > 400.
>
> The error occurred sometime in the interval
>
> 09:32:58 [basic-suit] @ Run test: 006_migrations.py:
> 09:33:55 [basic-suit] Error occured, aborting
>
> and indeed
>
> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/
> 1521/artifact/exported-artifacts/basic-suit-4.2-el7/
> test_logs/basic-suite-4.2/post-006_migrations.py/lago-
> basic-suite-4-2-engine/_var_log/ovirt-engine/engine.log/*view*/
>
> has Engine disconnected from the host at
>
> 2018-04-03 05:33:32,307-04 ERROR
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
> (EE-ManagedThreadFactory-engineScheduled-Thread-39) [] Unable to
> RefreshCapabilities: VDSNetworkException: VDSGenericException:
> VDSNetworkException: Vds timeout occured
>
> Maybe Piotr can read more into it.
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-03 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-03 Thread Barak Korren 
On 3 April 2018 at 15:01, Greg Sheremeta  wrote:

> Barak, I was getting these 400s and 409s sporadically all last week while
> iterating on my docker stuff. I thought maybe it was my messing with the
> http_proxy stuff or doing docker rms. Is it possible I'm breaking things?
> I'm still working on it. Been working in straight for a while now:
> https://gerrit.ovirt.org/#/c/67166/
>
>
Greg, your work shouldn't be affecting other things unless you merge it...


-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-03 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-03 Thread Greg Sheremeta 
Barak, I was getting these 400s and 409s sporadically all last week while
iterating on my docker stuff. I thought maybe it was my messing with the
http_proxy stuff or doing docker rms. Is it possible I'm breaking things?
I'm still working on it. Been working in straight for a while now:
https://gerrit.ovirt.org/#/c/67166/




On Tue, Apr 3, 2018 at 7:51 AM, Barak Korren  wrote:

> On 3 April 2018 at 14:07, Barak Korren  wrote:
> > Test failed: [ 006_migrations.prepare_migration_attachments_ipv6 ]
> >
> > Link to suspected patches:
> >
> > (Patch seems unrelated - do we have sporadic communication issues
> > arising in PST?)
> > https://gerrit.ovirt.org/c/89737/1 - vdsm - automation: check-patch:
> > attempt to install vdsm-gluster
> >
> > Link to Job:
> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/
> >
> > Link to all logs:
> > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/
> 1521/artifact/exported-artifacts/basic-suit-4.2-el7/
> test_logs/basic-suite-4.2/post-006_migrations.py/
> >
> > Error snippet from log:
> >
> > 
> >
> > 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
> > 78, in wrapper
> > prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs
> >   File "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/
> ovirt-system-tests/basic-suite-4.2/test-scenarios/006_migrations.py",
> > line 139, in prepare_migration_attachments_ipv6
> > engine, host_service, MIGRATION_NETWORK, ip_configuration)
> >   File "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/
> ovirt-system-tests/basic-suite-4.2/test_utils/network_utils_v4.py",
> > line 71, in modify_ip_config
> > check_connectivity=True)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
> > line 36729, in setup_networks
> > return self._internal_action(action, 'setupnetworks', None,
> > headers, query, wait)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> > 299, in _internal_action
> > return future.wait() if wait else future
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> > 55, in wait
> > return self._code(response)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> > 296, in callback
> > self._check_fault(response)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> > 132, in _check_fault
> > self._raise_error(response, body)
> >   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> > 118, in _raise_error
> > raise error
> > Error: Fault reason is "Operation Failed". Fault detail is "[Network
> > error during communication with the Host.]". HTTP response code is
> > 400.
> >
> >
> >
> > 
> >
>
>
> Same failure seems to have happened again  - on a different patch -
> this time foe ovirt-engine:
> https://gerrit.ovirt.org/#/c/89748/1
>
> Failed test run:
> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1523/
>
>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>



-- 

GREG SHEREMETA

SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX

Red Hat NA



gsher...@redhat.comIRC: gshereme

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

Re: [ovirt-devel] How To Construct An Local Developing Enviroment?

2018-04-03 Thread Martin Perina 
On Tue, Apr 3, 2018 at 1:49 PM, Benny Zlotnik  wrote:

> Hi,
>
> Take a look here: https://www.ovirt.org/develop/
> developer-guide/engine/engine-development-environment/
>

Unfortunately we have a lot of outdated information in above page, please
use below instead:

https://github.com/oVirt/ovirt-engine/blob/master/README.adoc

And please don't forget about
postgresql-contrib/rh-postgresql95-postgresql-contrib package requirement:

http://lists.ovirt.org/pipermail/devel/2018-January/032452.html
​


>
>
> On Tue, Apr 3, 2018 at 1:56 PM, sundw  wrote:
>
>> Hi Guys!
>> I plan to construct an local developing environment for oVirt.
>> But I can not find any relative pages from the web site(www.ovirt.org).
>> Maybe I am not patient :).
>>
>> Could you please give me some advice or some links about
>> How To Construct An Local Developing Enviroment?
>>
>> Thanks!
>>
>> --
>> *孙大巍*
>> 北京科银京成技术有限公司/新产品研发部
>> 13378105625 <(337)%20810-5625>
>>
>> ___
>> 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
>



-- 
Martin Perina
Associate Manager, Software Engineering
Red Hat Czech s.r.o.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-03 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-03 Thread Dan Kenigsberg 
On Tue, Apr 3, 2018 at 2:07 PM, Barak Korren  wrote:
> Test failed: [ 006_migrations.prepare_migration_attachments_ipv6 ]
>
> Link to suspected patches:
>
> (Patch seems unrelated - do we have sporadic communication issues
> arising in PST?)
> https://gerrit.ovirt.org/c/89737/1 - vdsm - automation: check-patch:
> attempt to install vdsm-gluster
>
> Link to Job:
> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/
>
> Link to all logs:
> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-006_migrations.py/
>
> Error snippet from log:
>
> 
>
> 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
> 78, in wrapper
> prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs
>   File 
> "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/006_migrations.py",
> line 139, in prepare_migration_attachments_ipv6
> engine, host_service, MIGRATION_NETWORK, ip_configuration)
>   File 
> "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test_utils/network_utils_v4.py",
> line 71, in modify_ip_config
> check_connectivity=True)
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
> line 36729, in setup_networks
> return self._internal_action(action, 'setupnetworks', None,
> headers, query, wait)
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 299, in _internal_action
> return future.wait() if wait else future
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 55, in wait
> return self._code(response)
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 296, in callback
> self._check_fault(response)
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 132, in _check_fault
> self._raise_error(response, body)
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 118, in _raise_error
> raise error
> Error: Fault reason is "Operation Failed". Fault detail is "[Network
> error during communication with the Host.]". HTTP response code is
> 400.

The error occurred sometime in the interval

09:32:58 [basic-suit] @ Run test: 006_migrations.py:
09:33:55 [basic-suit] Error occured, aborting

and indeed

http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-006_migrations.py/lago-basic-suite-4-2-engine/_var_log/ovirt-engine/engine.log/*view*/

has Engine disconnected from the host at

2018-04-03 05:33:32,307-04 ERROR
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring]
(EE-ManagedThreadFactory-engineScheduled-Thread-39) [] Unable to
RefreshCapabilities: VDSNetworkException: VDSGenericException:
VDSNetworkException: Vds timeout occured

Maybe Piotr can read more into it.
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-03 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-03 Thread Barak Korren 
On 3 April 2018 at 14:07, Barak Korren  wrote:
> Test failed: [ 006_migrations.prepare_migration_attachments_ipv6 ]
>
> Link to suspected patches:
>
> (Patch seems unrelated - do we have sporadic communication issues
> arising in PST?)
> https://gerrit.ovirt.org/c/89737/1 - vdsm - automation: check-patch:
> attempt to install vdsm-gluster
>
> Link to Job:
> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/
>
> Link to all logs:
> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-006_migrations.py/
>
> Error snippet from log:
>
> 
>
> 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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
> 78, in wrapper
> prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs
>   File 
> "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/006_migrations.py",
> line 139, in prepare_migration_attachments_ipv6
> engine, host_service, MIGRATION_NETWORK, ip_configuration)
>   File 
> "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test_utils/network_utils_v4.py",
> line 71, in modify_ip_config
> check_connectivity=True)
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
> line 36729, in setup_networks
> return self._internal_action(action, 'setupnetworks', None,
> headers, query, wait)
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 299, in _internal_action
> return future.wait() if wait else future
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 55, in wait
> return self._code(response)
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 296, in callback
> self._check_fault(response)
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 132, in _check_fault
> self._raise_error(response, body)
>   File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
> 118, in _raise_error
> raise error
> Error: Fault reason is "Operation Failed". Fault detail is "[Network
> error during communication with the Host.]". HTTP response code is
> 400.
>
>
>
> 
>


Same failure seems to have happened again  - on a different patch -
this time foe ovirt-engine:
https://gerrit.ovirt.org/#/c/89748/1

Failed test run:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1523/


-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] How To Construct An Local Developing Enviroment?

2018-04-03 Thread Benny Zlotnik 
Hi,

Take a look here:
https://www.ovirt.org/develop/developer-guide/engine/engine-development-environment/

On Tue, Apr 3, 2018 at 1:56 PM, sundw  wrote:

> Hi Guys!
> I plan to construct an local developing environment for oVirt.
> But I can not find any relative pages from the web site(www.ovirt.org).
> Maybe I am not patient :).
>
> Could you please give me some advice or some links about
> How To Construct An Local Developing Enviroment?
>
> Thanks!
>
> --
> *孙大巍*
> 北京科银京成技术有限公司/新产品研发部
> 13378105625 <(337)%20810-5625>
>
> ___
> 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

[ovirt-devel] How To Construct An Local Developing Enviroment?

2018-04-03 Thread sundw 
Hi Guys!
I plan to construct an local developing environment for oVirt.
But I can not find any relative pages from the web site(www.ovirt.org).
Maybe I am not patient :).

Could you please give me some advice or some links about How To Construct An 
Local Developing Enviroment?

Thanks! 



孙大巍
北京科银京成技术有限公司/新产品研发部
13378105625
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Lago v0.43 Release Announcement

2018-04-03 Thread Gal Ben Haim 
Hi All,

On behalf of the Lago team, I'm pleased to announce Lago v0.43 is available!
For a detailed release announcement please refer to our Github page at:
https://github.com/lago-project/lago/releases/tag/0.43


Resources
==
Lago Docs: http://lago.readthedocs.io/en/latest/
GitHub: https://github.com/lago-project/lago/
YUM Repository: http://resources.ovirt.org/repos/lago/stable/0.0/rpm/
Pypi: https://pypi.python.org/pypi/lago
Changelog: http://lago.readthedocs.io/en/0.43/_static/ChangeLog.txt


As always, if you find any problems, or willing to contribute, visit our
GitHub page.

Enjoy!

-- 
*GAL bEN HAIM*
RHV DEVOPS
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] [ OST Failure Report ] [ oVirt 4.2 ] [ 2018-04-03 ] [006_migrations.prepare_migration_attachments_ipv6]

2018-04-03 Thread Barak Korren 
Test failed: [ 006_migrations.prepare_migration_attachments_ipv6 ]

Link to suspected patches:

(Patch seems unrelated - do we have sporadic communication issues
arising in PST?)
https://gerrit.ovirt.org/c/89737/1 - vdsm - automation: check-patch:
attempt to install vdsm-gluster

Link to Job:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/

Link to all logs:
http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1521/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-006_migrations.py/

Error snippet from log:



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 "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
78, in wrapper
prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs
  File 
"/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/006_migrations.py",
line 139, in prepare_migration_attachments_ipv6
engine, host_service, MIGRATION_NETWORK, ip_configuration)
  File 
"/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test_utils/network_utils_v4.py",
line 71, in modify_ip_config
check_connectivity=True)
  File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
line 36729, in setup_networks
return self._internal_action(action, 'setupnetworks', None,
headers, query, wait)
  File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
299, in _internal_action
return future.wait() if wait else future
  File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
55, in wait
return self._code(response)
  File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
296, in callback
self._check_fault(response)
  File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
132, in _check_fault
self._raise_error(response, body)
  File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
118, in _raise_error
raise error
Error: Fault reason is "Operation Failed". Fault detail is "[Network
error during communication with the Host.]". HTTP response code is
400.







-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] oVirt log analyzer

2018-04-03 Thread Barak Korren 
On 3 April 2018 at 12:55, Milan Zamazal  wrote:
> Barak Korren  writes:
>
>> On 29 March 2018 at 21:11, Tomas Jelinek  wrote:
>>
>>>
>>>
>>> On Thu, Mar 29, 2018 at 7:55 PM, Greg Sheremeta 
>>> wrote:
>>>
 Nice! I think a nice RFE would be to surface this info in the UI.

 On Thu, Mar 29, 2018 at 8:30 AM, Milan Zamazal 
 wrote:

> Hi, during last year Outreachy internship a tool for analyzing oVirt
> logs was created.  When it is provided with oVirt logs (such as SOS
> reports, logs gathered by Lago, single or multiple log files) it tries
> to identify and classify important lines from the logs and present them
> in a structured form.  Its primary purpose is to get a quick and easy
> overview of actions and errors.
>

>>> I would add that it can correlate more log files (from
>>> engine/vdsm/libvirt/quemu) and show a unified view of them.
>>> It can follow the life of one entity (such as a VM) and show what was
>>> going on with it across the system. I have used it a lot to look for races
>>> and it was pretty useful for that.
>>>
>>
>>
>> I wonder if we can automate running it on OST failures to get automated
>> failure analysis.
>
> Well, ovirt-log-analyzer doesn't provide failure analysis, it just tries
> to extract more important lines from the logs and add some information
> to them.  It may or may not be useful to add its output to OST failures
> in future, but some feedback and testing are needed first, I assume
> there are still bugs and things to improve.
>

I'll try to be more specific about the use case we're lookin at.

Right now, when a test fails in OST - al you get is the traceback from
nose of the oVirt API cll you've made. For some tests additional
information is provided by having nise collect it from  STDOUT.

It could be very useful if we could use some information about the API
call that had been made, and use it to extract relevant information
about the call from the vdms and engine logs,

Can ovirt-log-analyzer be used for that?




-- 
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] oVirt log analyzer

2018-04-03 Thread Milan Zamazal 
Barak Korren  writes:

> On 29 March 2018 at 21:11, Tomas Jelinek  wrote:
>
>>
>>
>> On Thu, Mar 29, 2018 at 7:55 PM, Greg Sheremeta 
>> wrote:
>>
>>> Nice! I think a nice RFE would be to surface this info in the UI.
>>>
>>> On Thu, Mar 29, 2018 at 8:30 AM, Milan Zamazal 
>>> wrote:
>>>
 Hi, during last year Outreachy internship a tool for analyzing oVirt
 logs was created.  When it is provided with oVirt logs (such as SOS
 reports, logs gathered by Lago, single or multiple log files) it tries
 to identify and classify important lines from the logs and present them
 in a structured form.  Its primary purpose is to get a quick and easy
 overview of actions and errors.

>>>
>> I would add that it can correlate more log files (from
>> engine/vdsm/libvirt/quemu) and show a unified view of them.
>> It can follow the life of one entity (such as a VM) and show what was
>> going on with it across the system. I have used it a lot to look for races
>> and it was pretty useful for that.
>>
>
>
> I wonder if we can automate running it on OST failures to get automated
> failure analysis.

Well, ovirt-log-analyzer doesn't provide failure analysis, it just tries
to extract more important lines from the logs and add some information
to them.  It may or may not be useful to add its output to OST failures
in future, but some feedback and testing are needed first, I assume
there are still bugs and things to improve.

 The tool analyses given logs and produces text files with the extracted
 information.  There is an Emacs user interface that presents the output
 in a nice way with added functionality such as filtering.  Emacs haters
 can use the plain text files or write another user interface. :-)

 You can get ovirt-log-analyzer from
 https://github.com/mz-pdm/ovirt-log-analyzer
 README.md explains how to use it.

 Note that ovirt-log-analyzer has been created within the limited
 resources of an Outreachy internship with some additional work and not
 everything is perfect.  Feel free to make improvements.

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

>>>
>>>
>>>
>>> --
>>>
>>> GREG SHEREMETA
>>>
>>> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>>>
>>> Red Hat NA
>>>
>>> 
>>>
>>> gsher...@redhat.comIRC: gshereme
>>> 
>>>
>>> ___
>>> 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
>>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] oVirt log analyzer

2018-04-03 Thread Milan Zamazal 
Yaniv Kaul  writes:

> On Thu, Mar 29, 2018 at 9:11 PM, Tomas Jelinek  wrote:
>
>>
>>
>> On Thu, Mar 29, 2018 at 7:55 PM, Greg Sheremeta 
>> wrote:
>>
>>> Nice! I think a nice RFE would be to surface this info in the UI.
>>>
>>> On Thu, Mar 29, 2018 at 8:30 AM, Milan Zamazal 
>>> wrote:
>>>
 Hi, during last year Outreachy internship a tool for analyzing oVirt
 logs was created.  When it is provided with oVirt logs (such as SOS
 reports, logs gathered by Lago, single or multiple log files) it tries
 to identify and classify important lines from the logs and present them
 in a structured form.  Its primary purpose is to get a quick and easy
 overview of actions and errors.

>>>
>> I would add that it can correlate more log files (from
>> engine/vdsm/libvirt/quemu) and show a unified view of them.
>> It can follow the life of one entity (such as a VM) and show what was
>> going on with it across the system. I have used it a lot to look for races
>> and it was pretty useful for that.
>>
>
> This is not very clear from the readme, which only says 'Assuming your *oVirt
> logs* are stored in DIRECTORY ' - what logs exactly are in that
> directory?

Whatever logs you have got, unpacked (i.e. not in tar), either
uncompressed or compressed with xz or gzip.  The analyzer looks for
Engine, Vdsm, libvirt, QEMU, sanlock, and SPM lock logs by default,
identified by file names.  Directory structure doesn't matter.

> Is that the result of logs from ovirt-log-collector ?  Y.
>
>
>>
>>>
 The tool analyses given logs and produces text files with the extracted
 information.  There is an Emacs user interface that presents the output
 in a nice way with added functionality such as filtering.  Emacs haters
 can use the plain text files or write another user interface. :-)

 You can get ovirt-log-analyzer from
 https://github.com/mz-pdm/ovirt-log-analyzer
 README.md explains how to use it.

 Note that ovirt-log-analyzer has been created within the limited
 resources of an Outreachy internship with some additional work and not
 everything is perfect.  Feel free to make improvements.

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

>>>
>>>
>>>
>>> --
>>>
>>> GREG SHEREMETA
>>>
>>> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>>>
>>> Red Hat NA
>>>
>>> 
>>>
>>> gsher...@redhat.comIRC: gshereme
>>> 
>>>
>>> ___
>>> 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
>>
> ___
> 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][HC] HE fails to deploy

2018-04-03 Thread Simone Tiraboschi 
On Tue, Apr 3, 2018 at 10:14 AM, Simone Tiraboschi 
wrote:

>
>
> On Mon, Apr 2, 2018 at 4:44 PM, Sahina Bose  wrote:
>
>> HE fails to deploy at waiting for host to be up in the local HE VM.
>> The setup logs does not indicate why it failed - atleast I couldn't find
>> anything
>>
>
> I see:
>
> "status": "install_failed"
>
> So I think that something went wrong with host-deploy on that host but we
> definitively need host-deploy logs for that and they are just on the engine
> VM.
>

According to the timestamps it could be related to:
Apr  2 09:58:13 lago-hc-basic-suite-master-host-0 systemd: Starting Open
vSwitch Database Unit...
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 ovs-ctl: runuser: System
error
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 ovs-ctl:
/etc/openvswitch/conf.db does not exist ... (warning).
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 ovs-ctl: Creating empty
database /etc/openvswitch/conf.db runuser: System error
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 ovs-ctl: [FAILED]
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd:
ovsdb-server.service: control process exited, code=exited status=1
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd: Failed to start
Open vSwitch Database Unit.
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd: Unit
ovsdb-server.service entered failed state.
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd:
ovsdb-server.service failed.
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd: Cannot add
dependency job for unit lvm2-lvmetad.socket, ignoring: Invalid request
descriptor
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd: Assertion failed
for Open vSwitch Delete Transient Ports.
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd:
ovsdb-server.service holdoff time over, scheduling restart.
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd: Cannot add
dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd: start request
repeated too quickly for ovsdb-server.service
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd: Failed to start
Open vSwitch Database Unit.
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd: Unit
ovsdb-server.service entered failed state.
Apr  2 09:58:14 lago-hc-basic-suite-master-host-0 systemd:
ovsdb-server.service failed.


>
>
>>
>> -- Forwarded message --
>> From: 
>> Date: Mon, Apr 2, 2018 at 7:50 PM
>> Subject: [oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master -
>> Build # 276 - Still Failing!
>> To: in...@ovirt.org, sab...@redhat.com
>>
>>
>> Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-sui
>> te-master/
>> Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-sui
>> te-master/276/
>> Build Number: 276
>> Build Status:  Still Failing
>> Triggered By: Started by timer
>>
>> -
>> Changes Since Last Success:
>> -
>> Changes for Build #265
>> [Gal Ben Haim] Check if the prefix exists before printing its size
>>
>> [Sandro Bonazzola] ovirt-engine: add jobs for 4.1.10 async
>>
>>
>> Changes for Build #266
>> [Gal Ben Haim] Check if the prefix exists before printing its size
>>
>>
>> Changes for Build #267
>> [Gal Ben Haim] Check if the prefix exists before printing its size
>>
>> [Daniel Belenky] ppc repos: Use qemu EV release instead of test
>>
>> [Daniel Belenky] global_setup: Add generic package remove function
>>
>> [Daniel Belenky] Fix package verification in verify_packages
>>
>>
>> Changes for Build #268
>> [Gal Ben Haim] Check if the prefix exists before printing its size
>>
>>
>> Changes for Build #269
>> [Gal Ben Haim] Check if the prefix exists before printing its size
>>
>>
>> Changes for Build #270
>> [Gal Ben Haim] Check if the prefix exists before printing its size
>>
>>
>> Changes for Build #271
>> [Gal Ben Haim] Check if the prefix exists before printing its size
>>
>>
>> Changes for Build #272
>> [Gal Ben Haim] Check if the prefix exists before printing its size
>>
>>
>> Changes for Build #273
>> [Eitan Raviv] network: macpool: test disallowing dups while dups exist
>>
>> [Daniel Belenky] docker cleanup:Fix edge case for unamed containers
>>
>> [Daniel Belenky] nested_config: Count nesting level of options
>>
>> [Daniel Belenky] Introduce conditional execution in STDCI DSL
>>
>> [Daniel Belenky] Add OST STDCI V2 jobs
>>
>>
>> Changes for Build #274
>> [Gal Ben Haim] he-iscsi-master: Temporarily exclude in check-patch
>>
>>
>> Changes for Build #275
>> [Gal Ben Haim] he-iscsi-master: Temporarily exclude in check-patch
>>
>>
>> Changes for Build #276
>> [Barak Korren] Force STDCI V2 job to use physical host
>>
>> [Daniel Belenky] Build container on changes to docker_cleanup
>>
>>
>>
>>
>> -
>> Failed Tests:
>> -
>> No tests ran.

Re: [ovirt-devel] [OST][HC] HE fails to deploy

2018-04-03 Thread Simone Tiraboschi 
On Mon, Apr 2, 2018 at 4:44 PM, Sahina Bose  wrote:

> HE fails to deploy at waiting for host to be up in the local HE VM.
> The setup logs does not indicate why it failed - atleast I couldn't find
> anything
>

I see:

"status": "install_failed"

So I think that something went wrong with host-deploy on that host but we
definitively need host-deploy logs for that and they are just on the engine
VM.


>
> -- Forwarded message --
> From: 
> Date: Mon, Apr 2, 2018 at 7:50 PM
> Subject: [oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build
> # 276 - Still Failing!
> To: in...@ovirt.org, sab...@redhat.com
>
>
> Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-sui
> te-master/
> Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-sui
> te-master/276/
> Build Number: 276
> Build Status:  Still Failing
> Triggered By: Started by timer
>
> -
> Changes Since Last Success:
> -
> Changes for Build #265
> [Gal Ben Haim] Check if the prefix exists before printing its size
>
> [Sandro Bonazzola] ovirt-engine: add jobs for 4.1.10 async
>
>
> Changes for Build #266
> [Gal Ben Haim] Check if the prefix exists before printing its size
>
>
> Changes for Build #267
> [Gal Ben Haim] Check if the prefix exists before printing its size
>
> [Daniel Belenky] ppc repos: Use qemu EV release instead of test
>
> [Daniel Belenky] global_setup: Add generic package remove function
>
> [Daniel Belenky] Fix package verification in verify_packages
>
>
> Changes for Build #268
> [Gal Ben Haim] Check if the prefix exists before printing its size
>
>
> Changes for Build #269
> [Gal Ben Haim] Check if the prefix exists before printing its size
>
>
> Changes for Build #270
> [Gal Ben Haim] Check if the prefix exists before printing its size
>
>
> Changes for Build #271
> [Gal Ben Haim] Check if the prefix exists before printing its size
>
>
> Changes for Build #272
> [Gal Ben Haim] Check if the prefix exists before printing its size
>
>
> Changes for Build #273
> [Eitan Raviv] network: macpool: test disallowing dups while dups exist
>
> [Daniel Belenky] docker cleanup:Fix edge case for unamed containers
>
> [Daniel Belenky] nested_config: Count nesting level of options
>
> [Daniel Belenky] Introduce conditional execution in STDCI DSL
>
> [Daniel Belenky] Add OST STDCI V2 jobs
>
>
> Changes for Build #274
> [Gal Ben Haim] he-iscsi-master: Temporarily exclude in check-patch
>
>
> Changes for Build #275
> [Gal Ben Haim] he-iscsi-master: Temporarily exclude in check-patch
>
>
> Changes for Build #276
> [Barak Korren] Force STDCI V2 job to use physical host
>
> [Daniel Belenky] Build container on changes to docker_cleanup
>
>
>
>
> -
> Failed Tests:
> -
> No tests ran.
>
>
> ___
> 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