Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-11-13 ] [add_master_storage_domain]

[Barak Korren]

On 13 November 2017 at 12:44, Allon Mureinik  wrote:
> Both are merged, let's see how OST fares
>
The 1st one failed, but the 2nd passed:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3792

So we're over this hill.

-- 
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] failing check-patch on ovirt-engine

[Daniel Belenky]

Hey,

It's a trailing issue from [1] as Allon mentioned.
Our CI slaves generated mock cache during the outage of the snapshot repos,
and it caused your build to fail.
I've cleaned the cache - everything should work now.

[1] http://lists.ovirt.org/pipermail/devel/2017-November/031840.html

Thanks,

On Mon, Nov 13, 2017 at 12:14 PM, Allon Mureinik 
wrote:

> Probably another instead of [1].
> Retriggering the job should probably clear the issue up.
>
> [1] http://lists.ovirt.org/pipermail/devel/2017-November/031840.html
>
> On Sun, Nov 12, 2017 at 5:53 PM, Greg Sheremeta 
> wrote:
>
>> Hi,
>>
>> I'm seeing a weird issue in ovirt-engine check-patch.
>>
>> There's no way this failure is related to my patch [
>> https://gerrit.ovirt.org/#/c/83950/], which is a 1 character typo fix in
>> the constants file.
>>
>> Anyone have any ideas or also seeing this? It seems random, too --
>> sometimes 1 or 2 of the jobs will succeed [el7, fc25] but the other will
>> fail. Etc.
>>
>>
>> *14:48:08* + automation/packaging-setup-tests.sh*14:48:08* + trap popd 
>> 0*14:48:08* +++ readlink -f automation/packaging-setup-tests.sh*14:48:08* ++ 
>> dirname 
>> /home/jenkins/workspace/ovirt-engine_master_check-patch-fc26-x86_64/ovirt-engine/automation/packaging-setup-tests.sh*14:48:08*
>>  + pushd 
>> /home/jenkins/workspace/ovirt-engine_master_check-patch-fc26-x86_64/ovirt-engine/automation/..*14:48:08*
>>  ~ ~*14:48:08* + export 
>> PYTHONPATH=packaging/pythonlib:packaging/setup:*14:48:08* + 
>> PYTHONPATH=packaging/pythonlib:packaging/setup:*14:48:08* + python -m pytest 
>> packaging/setup*14:48:08* = test session starts 
>> ==*14:48:08* platform linux2 -- Python 2.7.14, 
>> pytest-3.2.3, py-1.4.34, pluggy-0.4.0*14:48:08* rootdir: 
>> /home/jenkins/workspace/ovirt-engine_master_check-patch-fc26-x86_64/ovirt-engine,
>>  inifile:*14:48:08* collected 0 items / 1 errors*14:48:08* *14:48:08* 
>>  ERRORS 
>> *14:48:08*  ERROR collecting 
>> packaging/setup/tests/ovirt_engine_setup/engine_common/test_database.py 
>> *14:48:08* ImportError while importing test module 
>> '/home/jenkins/workspace/ovirt-engine_master_check-patch-fc26-x86_64/ovirt-engine/packaging/setup/tests/ovirt_engine_setup/engine_common/test_database.py'.*14:48:08*
>>  Hint: make sure your test modules/packages have valid Python 
>> names.*14:48:08* Traceback:*14:48:08* 
>> packaging/setup/tests/ovirt_engine_setup/engine_common/test_database.py:19: 
>> in *14:48:08* import ovirt_engine_setup.engine_common.database 
>> as under_test  # isort:skip # noqa: E402*14:48:08* 
>> packaging/setup/ovirt_engine_setup/engine_common/database.py:30: in 
>> *14:48:08* from otopi import base*14:48:08* E   ImportError: No 
>> module named otopi*14:48:08* !!! Interrupted: 1 errors 
>> during collection *14:48:08* === 
>> 1 error in 0.33 seconds *14:48:08* + 
>> popd*14:48:08* ~
>>
>>
>>
>> -- Forwarded message --
>> From: Code Review 
>> Date: Sun, Nov 12, 2017 at 10:31 AM
>> Subject: Change in ovirt-engine[master]: engine: typo fix snaphot ->
>> snapshot
>> To: Greg Sheremeta 
>>
>>
>> Jenkins CI *posted comments* on this change.
>>
>> View Change 
>>
>> Patch set 1:Continuous-Integration -1
>>
>> Build Failed
>>
>> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch
>> -fc25-x86_64/17231/ : FAILURE
>>
>> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch
>> -fc26-x86_64/157/ : FAILURE
>>
>> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch
>> -el7-x86_64/33193/ : SUCCESS
>>
>>
>> To view, visit change 83950 . To
>> unsubscribe, visit settings .
>> Gerrit-Project: ovirt-engine
>> Gerrit-Branch: master
>> Gerrit-MessageType: comment
>> Gerrit-Change-Id: I88b4d75855c0abe2f0eddd8b282c172205db2e42
>> Gerrit-Change-Number: 83950
>> Gerrit-PatchSet: 1
>> Gerrit-Owner: Greg Sheremeta 
>> Gerrit-Reviewer: Alexander Wels 
>> Gerrit-Reviewer: Greg Sheremeta 
>> Gerrit-Reviewer: Jenkins CI
>> Gerrit-Reviewer: Tal Nisan 
>> Gerrit-Reviewer: Vojtech Szocs 
>> Gerrit-Reviewer: gerrit-hooks 
>> Gerrit-Comment-Date: Sun, 12 Nov 2017 15:31:27 +
>> Gerrit-HasComments: No
>>
>>
>>
>> --
>>
>> GREG SHEREMETA
>>
>> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>>
>> Red Hat NA
>>
>> 
>>
>> gsher...@redhat.comIRC: gshereme
>> 
>>
>> ___
>> Infra mailing list
>> in...@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>


-- 

DANIEL 

[ovirt-devel] oVirt 4.1.9 will be the last 4.1 release

[Sandro Bonazzola]

Hi,
we are now targeting oVirt 4.2.0 GA around December 12th and oVirt 4.1.8
around December 5th.
Against tradition that would have set 4.1.8 as last 4.1 release, this round
we'll release also oVIrt 4.1.9 being it already in development just before
4.2.0 GA.

We suggest to be prepared to upgrade to 4.2 since 4.1 won't receive any
further update after 4.1.9 release.

-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R

Red Hat EMEA 

TRIED. TESTED. TRUSTED. 

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

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-11-13 ] [add_master_storage_domain]

[Allon Mureinik]

Both are merged, let's see how OST fares

On Mon, Nov 13, 2017 at 12:00 PM, Allon Mureinik 
wrote:

> I merged 83920 with dependencies. Perhaps gerrit doesn't handle such
> chains properly (or perhaps our CI is misusing the API?).
>
> WRT current issues, posted two patches upstream:
> - https://gerrit.ovirt.org/#/c/83986/ - fixes the GWT build that was
> broken this morning, preventing a proper build altogether
> - https://gerrit.ovirt.org/#/c/83987/ - should fix the OST regression you
> noted.
>
> I'm waiting for the CI to finish running on both and will merge.
>
> On Mon, Nov 13, 2017 at 11:26 AM, Barak Korren  wrote:
>
>> On 13 November 2017 at 11:10, Allon Mureinik  wrote:
>> > Commit 86bf82e746404145e8b97df46f514086e4f82e69 is probably the
>> offending
>> > commit, taking a deeper look now, should have a fix within the hour
>> >
>>
>> Hmm, I see what happened there, that commit is
>> https://gerrit.ovirt.org/c/83920, so it was tested at:
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3769
>> and passed.
>>
>> BUT, it was tested along with https://gerrit.ovirt.org/#/c/83918/2
>> that was merged earlier as far as git ordering goes, but somehow was
>> assumed to be a later patch. When we test multiple patches from the
>> same project we essentially use packages built from the one we deem to
>> be the latest. So in this case only the packages from 83918 were
>> actually tested.
>>
>> We went to great lengths to preserve correct patch ordering by
>> preserving the order of event notifications reaching us from gerrit.
>> But here it seems we ended out with out-of-order patches. Do you have
>> any idea how did we end up with this? Do you remember what was the
>> sequence in which you clicked the 'merge' button on the different
>> patches?
>>
>> --
>> 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] failing check-patch on ovirt-engine

[Allon Mureinik]

Probably another instead of [1].
Retriggering the job should probably clear the issue up.

[1] http://lists.ovirt.org/pipermail/devel/2017-November/031840.html

On Sun, Nov 12, 2017 at 5:53 PM, Greg Sheremeta  wrote:

> Hi,
>
> I'm seeing a weird issue in ovirt-engine check-patch.
>
> There's no way this failure is related to my patch [
> https://gerrit.ovirt.org/#/c/83950/], which is a 1 character typo fix in
> the constants file.
>
> Anyone have any ideas or also seeing this? It seems random, too --
> sometimes 1 or 2 of the jobs will succeed [el7, fc25] but the other will
> fail. Etc.
>
>
> *14:48:08* + automation/packaging-setup-tests.sh*14:48:08* + trap popd 
> 0*14:48:08* +++ readlink -f automation/packaging-setup-tests.sh*14:48:08* ++ 
> dirname 
> /home/jenkins/workspace/ovirt-engine_master_check-patch-fc26-x86_64/ovirt-engine/automation/packaging-setup-tests.sh*14:48:08*
>  + pushd 
> /home/jenkins/workspace/ovirt-engine_master_check-patch-fc26-x86_64/ovirt-engine/automation/..*14:48:08*
>  ~ ~*14:48:08* + export 
> PYTHONPATH=packaging/pythonlib:packaging/setup:*14:48:08* + 
> PYTHONPATH=packaging/pythonlib:packaging/setup:*14:48:08* + python -m pytest 
> packaging/setup*14:48:08* = test session starts 
> ==*14:48:08* platform linux2 -- Python 2.7.14, 
> pytest-3.2.3, py-1.4.34, pluggy-0.4.0*14:48:08* rootdir: 
> /home/jenkins/workspace/ovirt-engine_master_check-patch-fc26-x86_64/ovirt-engine,
>  inifile:*14:48:08* collected 0 items / 1 errors*14:48:08* *14:48:08* 
>  ERRORS 
> *14:48:08*  ERROR collecting 
> packaging/setup/tests/ovirt_engine_setup/engine_common/test_database.py 
> *14:48:08* ImportError while importing test module 
> '/home/jenkins/workspace/ovirt-engine_master_check-patch-fc26-x86_64/ovirt-engine/packaging/setup/tests/ovirt_engine_setup/engine_common/test_database.py'.*14:48:08*
>  Hint: make sure your test modules/packages have valid Python 
> names.*14:48:08* Traceback:*14:48:08* 
> packaging/setup/tests/ovirt_engine_setup/engine_common/test_database.py:19: 
> in *14:48:08* import ovirt_engine_setup.engine_common.database as 
> under_test  # isort:skip # noqa: E402*14:48:08* 
> packaging/setup/ovirt_engine_setup/engine_common/database.py:30: in 
> *14:48:08* from otopi import base*14:48:08* E   ImportError: No 
> module named otopi*14:48:08* !!! Interrupted: 1 errors during 
> collection *14:48:08* === 1 error 
> in 0.33 seconds *14:48:08* + popd*14:48:08* ~
>
>
>
> -- Forwarded message --
> From: Code Review 
> Date: Sun, Nov 12, 2017 at 10:31 AM
> Subject: Change in ovirt-engine[master]: engine: typo fix snaphot ->
> snapshot
> To: Greg Sheremeta 
>
>
> Jenkins CI *posted comments* on this change.
>
> View Change 
>
> Patch set 1:Continuous-Integration -1
>
> Build Failed
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch
> -fc25-x86_64/17231/ : FAILURE
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch
> -fc26-x86_64/157/ : FAILURE
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch
> -el7-x86_64/33193/ : SUCCESS
>
>
> To view, visit change 83950 . To
> unsubscribe, visit settings .
> Gerrit-Project: ovirt-engine
> Gerrit-Branch: master
> Gerrit-MessageType: comment
> Gerrit-Change-Id: I88b4d75855c0abe2f0eddd8b282c172205db2e42
> Gerrit-Change-Number: 83950
> Gerrit-PatchSet: 1
> Gerrit-Owner: Greg Sheremeta 
> Gerrit-Reviewer: Alexander Wels 
> Gerrit-Reviewer: Greg Sheremeta 
> Gerrit-Reviewer: Jenkins CI
> Gerrit-Reviewer: Tal Nisan 
> Gerrit-Reviewer: Vojtech Szocs 
> Gerrit-Reviewer: gerrit-hooks 
> Gerrit-Comment-Date: Sun, 12 Nov 2017 15:31:27 +
> Gerrit-HasComments: No
>
>
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> 
>
> gsher...@redhat.comIRC: gshereme
> 
>
> ___
> Infra mailing list
> in...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-11-13 ] [add_master_storage_domain]

[Allon Mureinik]

I merged 83920 with dependencies. Perhaps gerrit doesn't handle such chains
properly (or perhaps our CI is misusing the API?).

WRT current issues, posted two patches upstream:
- https://gerrit.ovirt.org/#/c/83986/ - fixes the GWT build that was broken
this morning, preventing a proper build altogether
- https://gerrit.ovirt.org/#/c/83987/ - should fix the OST regression you
noted.

I'm waiting for the CI to finish running on both and will merge.

On Mon, Nov 13, 2017 at 11:26 AM, Barak Korren  wrote:

> On 13 November 2017 at 11:10, Allon Mureinik  wrote:
> > Commit 86bf82e746404145e8b97df46f514086e4f82e69 is probably the
> offending
> > commit, taking a deeper look now, should have a fix within the hour
> >
>
> Hmm, I see what happened there, that commit is
> https://gerrit.ovirt.org/c/83920, so it was tested at:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3769
> and passed.
>
> BUT, it was tested along with https://gerrit.ovirt.org/#/c/83918/2
> that was merged earlier as far as git ordering goes, but somehow was
> assumed to be a later patch. When we test multiple patches from the
> same project we essentially use packages built from the one we deem to
> be the latest. So in this case only the packages from 83918 were
> actually tested.
>
> We went to great lengths to preserve correct patch ordering by
> preserving the order of event notifications reaching us from gerrit.
> But here it seems we ended out with out-of-order patches. Do you have
> any idea how did we end up with this? Do you remember what was the
> sequence in which you clicked the 'merge' button on the different
> patches?
>
> --
> 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 master ] [ 2017-11-13 ] [add_master_storage_domain]

[Barak Korren]

On 13 November 2017 at 11:10, Allon Mureinik  wrote:
> Commit 86bf82e746404145e8b97df46f514086e4f82e69 is probably the offending
> commit, taking a deeper look now, should have a fix within the hour
>

Hmm, I see what happened there, that commit is
https://gerrit.ovirt.org/c/83920, so it was tested at:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3769
and passed.

BUT, it was tested along with https://gerrit.ovirt.org/#/c/83918/2
that was merged earlier as far as git ordering goes, but somehow was
assumed to be a later patch. When we test multiple patches from the
same project we essentially use packages built from the one we deem to
be the latest. So in this case only the packages from 83918 were
actually tested.

We went to great lengths to preserve correct patch ordering by
preserving the order of event notifications reaching us from gerrit.
But here it seems we ended out with out-of-order patches. Do you have
any idea how did we end up with this? Do you remember what was the
sequence in which you clicked the 'merge' button on the different
patches?

-- 
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 master ] [ 2017-11-13 ] [add_master_storage_domain]

[Allon Mureinik]

Commit 86bf82e746404145e8b97df46f514086e4f82e69 is probably the offending
commit, taking a deeper look now, should have a fix within the hour

On Mon, Nov 13, 2017 at 9:55 AM, Barak Korren  wrote:

> Test failed: [ add_master_storage_domain ]
>
> Link to suspected patches:
> - https://gerrit.ovirt.org/#/c/83849/4
> This seems to be a fairly consistent regression as all patches that
> follow the patch above exhibit the same issue when tested, this list
> of similarly failing patches includes:
> - https://gerrit.ovirt.org/#/c/83940/2
> - https://gerrit.ovirt.org/#/c/83608/7
> - https://gerrit.ovirt.org/#/c/83815/3
> The following patch is an exception because it simply failed to build:
> - https://gerrit.ovirt.org/#/c/83370/9
>
> Link to Job:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3770/
>
> Link to all logs:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-
> tester/3770/artifact/exported-artifacts/basic-suit-master-
> el7/test_logs/basic-suite-master/post-002_bootstrap.py/
>
> Error snippet from log:
>
> 
>
> Fault reason is "Operation Failed". Fault detail is "[Failed to attach
> Storage due to an error on the Data Center master Storage Domain.
> -Please activate the master Storage Domain first.]". HTTP response code is
> 409.
>
> 
>
>
>
> --
> 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
>
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-11-13 ] [add_master_storage_domain]

[Allon Mureinik]

It's most definitely not THAT patch.
Could be one of the earlier patches in the series, though.

Looking.

On Mon, Nov 13, 2017 at 10:54 AM, Barak Korren  wrote:

> On 13 November 2017 at 10:08, Nir Soffer  wrote:
> >
> >
> > On Mon, Nov 13, 2017 at 9:56 AM Barak Korren  wrote:
> >>
> >> Test failed: [ add_master_storage_domain ]
> >>
> >> Link to suspected patches:
> >> - https://gerrit.ovirt.org/#/c/83849/4
> >
> >
> > This fixes grammar in few error messages, I don't see how this can cause
> > failures unless someone is depending on the error text...
> >
> Previous test with engine patches before it was successful:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3769
> This one included the following patches which were the two commits
> leading up to the failing one:
> - https://gerrit.ovirt.org/#/c/83920/4
> - https://gerrit.ovirt.org/#/c/83918/2
>
> Also following tests with no engine patches were also successful:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3780/
> so this eliminates suspicion for unrelated infra issues.
>
> I think that is sufficient grounds for suspicion.
>
> >>
> >> This seems to be a fairly consistent regression as all patches that
> >> follow the patch above exhibit the same issue when tested, this list
> >> of similarly failing patches includes:
> >> - https://gerrit.ovirt.org/#/c/83940/2
> >> - https://gerrit.ovirt.org/#/c/83608/7
> >> - https://gerrit.ovirt.org/#/c/83815/3
> >> The following patch is an exception because it simply failed to build:
> >> - https://gerrit.ovirt.org/#/c/83370/9
> >>
> >> Link to Job:
> >> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3770/
> >>
> >> Link to all logs:
> >>
> >> http://jenkins.ovirt.org/job/ovirt-master_change-queue-
> tester/3770/artifact/exported-artifacts/basic-suit-master-
> el7/test_logs/basic-suite-master/post-002_bootstrap.py/
> >>
> >> Error snippet from log:
> >>
> >> 
> >>
> >> Fault reason is "Operation Failed". Fault detail is "[Failed to attach
> >> Storage due to an error on the Data Center master Storage Domain.
> >> -Please activate the master Storage Domain first.]". HTTP response code
> is
> >> 409.
> >>
> >> 
> >>
> >>
> >>
> >> --
> >> 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
>
>
>
> --
> 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
>
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 2017-11-13 ] [add_master_storage_domain]

[Barak Korren]

On 13 November 2017 at 10:08, Nir Soffer  wrote:
>
>
> On Mon, Nov 13, 2017 at 9:56 AM Barak Korren  wrote:
>>
>> Test failed: [ add_master_storage_domain ]
>>
>> Link to suspected patches:
>> - https://gerrit.ovirt.org/#/c/83849/4
>
>
> This fixes grammar in few error messages, I don't see how this can cause
> failures unless someone is depending on the error text...
>
Previous test with engine patches before it was successful:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3769
This one included the following patches which were the two commits
leading up to the failing one:
- https://gerrit.ovirt.org/#/c/83920/4
- https://gerrit.ovirt.org/#/c/83918/2

Also following tests with no engine patches were also successful:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3780/
so this eliminates suspicion for unrelated infra issues.

I think that is sufficient grounds for suspicion.

>>
>> This seems to be a fairly consistent regression as all patches that
>> follow the patch above exhibit the same issue when tested, this list
>> of similarly failing patches includes:
>> - https://gerrit.ovirt.org/#/c/83940/2
>> - https://gerrit.ovirt.org/#/c/83608/7
>> - https://gerrit.ovirt.org/#/c/83815/3
>> The following patch is an exception because it simply failed to build:
>> - https://gerrit.ovirt.org/#/c/83370/9
>>
>> Link to Job:
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3770/
>>
>> Link to all logs:
>>
>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3770/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-suite-master/post-002_bootstrap.py/
>>
>> Error snippet from log:
>>
>> 
>>
>> Fault reason is "Operation Failed". Fault detail is "[Failed to attach
>> Storage due to an error on the Data Center master Storage Domain.
>> -Please activate the master Storage Domain first.]". HTTP response code is
>> 409.
>>
>> 
>>
>>
>>
>> --
>> 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



-- 
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