- Infra - oVirt List Archives

[CQ]: 87136, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '18

08 Feb '18

A system test invoked by the "ovirt-master" change queue including change 87136,6 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 87181,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87181,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87136/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87181/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5413/

1 0

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

08 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87274,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87244,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87244,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87274/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/630/

1 0

[ OST Failure Report ] [ oVirt Master (vdsm) ] [ 08-02-2018 ] [ 002_bootstrap.get_host_numa_nodes+ 004_basic_sanity.vm_run]
by Dafna Ron 08 Feb '18

08 Feb '18

Hi, We have a failure on 002_bootstrap.get_host_numa_nodes in basic suite and 004_basic_sanity.vm_run on upgrade from release suite. Eli, can you please take a look? it seems to be the same reason - host is down or not suitable *Link and headline of suspected patches: Link to Job:Link to all logs:(Relevant) error snippet from the log: <error>* *basic suite *: 2018-02-08 00:14:23,852-05 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (ServerService Thread Pool -- 41) [] SqlCall for procedure [GetAllFromVdcOption] compiled 2018-02-08 00:14:23,864-05 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (ServerService Thread Pool -- 41) [] Could not find enum value for option: 'ConfigDir' 2018-02-08 00:14:23,869-05 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (ServerService Thread Pool -- 41) [] Could not find enum value for option: 'DbJustRestored' 2018-02-08 00:14:23,871-05 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (ServerService Thread Pool -- 41) [] Could not find enum value for option: 'ConfigDir' 2018-02-08 00:14:23,881-05 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (ServerService Thread Pool -- 41) [] Could not find enum value for option: 'DbJustRestored' 2018-02-08 00:14:23,882-05 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (ServerService Thread Pool -- 41) [] Could not find enum value for option: 'ConfigDir' 2018-02-08 00:14:23,915-05 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (ServerService Thread Pool -- 41) [] Could not find enum value for option: 'DbJustRestored' 2018-02-08 00:14:23,919-05 INFO [org.ovirt.engine.core.utils.osinfo.OsInfoPreferencesLoader] (ServerService Thread Pool -- 41) [] Loading file '/etc/ovirt-engine/osinfo.conf.d/00-defaults.properties' 2018-02-08 00:14:23,971-05 DEBUG [org.ovirt.engine.core.utils.OsRepositoryImpl] (ServerService Thread Pool -- 41) [] Osinfo Repository: backwardCompatibility OtherLinux=5 Windows2008R2x64=17 Windows2003=3 Windows2003x64=10 RHEL3x64=15 Windows8x64=21 Windows8=20 Windows7=11 Windows7x64=12 Windows2008=4 RHEL4=8 RHEL6x64=19 RHEL5x64=13 Windows2012x64=23 WindowsXP=1 RHEL4x64=14 Unassigned=0 Windows2008x64=16 RHEL6=18 RHEL5=7 Other=0 REHL3=9 emptyNode os.debian_7.derivedFrom value=ubuntu_12_04 os.debian_7.id value=1300 os.debian_7.name value=Debian 7 os.freebsd.bus value=32 os.freebsd.derivedFrom value=other os.freebsd.id value=1500 os.freebsd.name value=FreeBSD 9.2 os.freebsdx64.bus value=64 os.freebsdx64.derivedFrom : upgrade suite: 2018-02-08 00:12:07,451-05 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (ServerService Thread Pool -- 51) [] Could not find enum value for option: 'DbJustRestored' 2018-02-08 00:12:07,451-05 WARN [org.ovirt.engine.core.utils.ConfigUtilsBase] (ServerService Thread Pool -- 51) [] Could not find enum value for option: 'ConfigDir' 2018-02-08 00:12:07,452-05 INFO [org.ovirt.engine.core.utils.osinfo.OsInfoPreferencesLoader] (ServerService Thread Pool -- 51) [] Loading file '/etc/ovirt-engine/osinfo.conf.d/00-defaults.properties' 2018-02-08 00:12:07,505-05 DEBUG [org.ovirt.engine.core.utils.OsRepositoryImpl] (ServerService Thread Pool -- 51) [] Osinfo Repository: backwardCompatibility OtherLinux=5 Windows2008R2x64=17 Windows2003=3 Windows2003x64=10 RHEL3x64=15 Windows8x64=21 Windows8=20 Windows7=11 Windows7x64=12 Windows2008=4 RHEL4=8 RHEL6x64=19 RHEL5x64=13 Windows2012x64=23 WindowsXP=1 RHEL4x64=14 Unassigned=0 Windows2008x64=16 RHEL6=18 RHEL5=7 Other=0 REHL3=9 emptyNode os.debian_7.derivedFrom value=ubuntu_12_04 os.debian_7.id value=1300 os.debian_7.name value=Debian 7 os.freebsd.bus value=32 os.freebsd.derivedFrom value=other os.freebsd.id value=1500 os.freebsd.name value=FreeBSD 9.2 os.freebsdx64.bus value=64 os.freebsdx64.derivedFrom value=freebsd os.freebsdx64.id value=1501 os.freebsdx64.name value=FreeBSD 9.2 x64 os.other.bus value=64 os.other.cpu.hotplugSupport value=true os.other.cpu.hotunplugSupport value=false os.other.cpu.unsupported value= *</error>*

2 5

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

08 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87272,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87244,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87244,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87272/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/627/

1 0

[CQ]: 86949, 5 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '18

08 Feb '18

A system test invoked by the "ovirt-master" change queue including change 86949,5 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 86920,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86920,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86949/5 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86920/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5406/

1 0

[oVirt CI] standard-enqueue - Build #9839 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 Feb '18

08 Feb '18

------=_Part_149_93651221.1518100761736 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/9839/ Build Name: #9839 Build Description: Gerrit: 87331 - ovirt-engine (3.6.13) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/87331 - title: build: post ovirt-engine-3.6.13.1 - project: ovirt-engine - branch: ovirt-engine-3.6-els - author: Sandro Bonazzola <sbonazzo(a)redhat.com> ------=_Part_149_93651221.1518100761736--

1 1

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

08 Feb '18

A system test invoked by the "ovirt-master" change queue including change 86860,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 86920,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86920,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86860/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86920/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5400/

1 0

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

08 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87271,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87244,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87244,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87271/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/624/

1 0

[CQ]: 87246,1 (otopi) failed "ovirt-master" system tests
by oVirt Jenkins 08 Feb '18

08 Feb '18

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

3 2

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

08 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87270,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87244,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87244,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87270/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/621/

1 0

[JIRA] (OVIRT-1867) Allow embedded secrets inside the source repo for CI
by Barak Korren (oVirt JIRA) 08 Feb '18

08 Feb '18

This is a multi-part message in MIME format... ------------=_1518096517-16706-206 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1867: ------------------------------------- Here is an implementation scheme that can meet [~rmohr(a)redhat.com]'s UX requirements while still allowing STDCI projects to be portable between CI systems. First, we adopt or setup an online credentials storage service that has the following features: # It has a UI where users can login and upload or download credentials # It has functionality where it can generate key pairs while storing the private key and making the public key visible. # It supports a oAuth-like flow where a system can request access to certain credentials and the user can confirm or deny it. Second, we write a secrets provider that allows the user to refer to a set of credentials in the service above (As well as the service itself). When trying to provide the secrets, the system would request access via the credentials storage service. Third, we write an STDCI service that encapsulates the special-case flow where we get a private key from the secrets provider and use it tio decrypt files from the Git repo. > Allow embedded secrets inside the source repo for CI > ---------------------------------------------------- > > Key: OVIRT-1867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Roman Mohr > Assignee: infra > Labels: credentials > > In order to improve the self-service capabilities of standard-ci it is > important for projects, that they can add their own secrets to projects (to > reach external services, e.g. docker hub, ...). > Travis has a very nice system which helps engineers there: > https://docs.travis-ci.com/user/encryption-keys/ > Basically the CI system needs to generate a public/private key pair for > every enabled git repo. The engineer simply fetches the public key via a > well know URL and encrypts the secrets. Then the encrypted secret can be > made part of the source repo. Before the tests are run the CI system > decrypts the secrets. Than can play together pretty well with Jenkinsfiles > too. > Benefit: > * Less manual intervention from CI team to add secrets to jobs > * Strengthen the config-in-code thinking -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518096517-16706-206 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1867:</h3> <p>Here is an implementation scheme that can meet [~rmohr(a)redhat.com]'s UX requirements while still allowing STDCI projects to be portable between CI systems.</p> <p>First, we adopt or setup an online credentials storage service that has the following features: # It has a UI where users can login and upload or download credentials # It has functionality where it can generate key pairs while storing the private key and making the public key visible. # It supports a oAuth-like flow where a system can request access to certain credentials and the user can confirm or deny it.</p> <p>Second, we write a secrets provider that allows the user to refer to a set of credentials in the service above (As well as the service itself). When trying to provide the secrets, the system would request access via the credentials storage service.</p> <p>Third, we write an STDCI service that encapsulates the special-case flow where we get a private key from the secrets provider and use it tio decrypt files from the Git repo.</p> <blockquote><h3>Allow embedded secrets inside the source repo for CI</h3> <pre> Key: OVIRT-1867 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Standard CI (Pipelines), STDCI DSL Reporter: Roman Mohr Assignee: infra Labels: credentials</pre> <p>In order to improve the self-service capabilities of standard-ci it is important for projects, that they can add their own secrets to projects (to reach external services, e.g. docker hub, …). Travis has a very nice system which helps engineers there: <a href="https://docs.travis-ci.com/user/encryption-keys/">https://docs.travis-ci.com/user/encryption-keys/</a> Basically the CI system needs to generate a public/private key pair for every enabled git repo. The engineer simply fetches the public key via a well know URL and encrypts the secrets. Then the encrypted secret can be made part of the source repo. Before the tests are run the CI system decrypts the secrets. Than can play together pretty well with Jenkinsfiles too. Benefit:</p> <pre>* Less manual intervention from CI team to add secrets to jobs * Strengthen the config-in-code thinking</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1518096517-16706-206--

1 0

[JIRA] (OVIRT-1867) Allow embedded secrets inside the source repo for CI
by Barak Korren (oVirt JIRA) 08 Feb '18

08 Feb '18

This is a multi-part message in MIME format... ------------=_1518095376-22378-218 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1867: -------------------------------- Labels: credentials (was: ) > Allow embedded secrets inside the source repo for CI > ---------------------------------------------------- > > Key: OVIRT-1867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Roman Mohr > Assignee: infra > Labels: credentials > > In order to improve the self-service capabilities of standard-ci it is > important for projects, that they can add their own secrets to projects (to > reach external services, e.g. docker hub, ...). > Travis has a very nice system which helps engineers there: > https://docs.travis-ci.com/user/encryption-keys/ > Basically the CI system needs to generate a public/private key pair for > every enabled git repo. The engineer simply fetches the public key via a > well know URL and encrypts the secrets. Then the encrypted secret can be > made part of the source repo. Before the tests are run the CI system > decrypts the secrets. Than can play together pretty well with Jenkinsfiles > too. > Benefit: > * Less manual intervention from CI team to add secrets to jobs > * Strengthen the config-in-code thinking -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518095376-22378-218 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1867:</h3> <pre>Labels: credentials (was: )</pre> <blockquote><h3>Allow embedded secrets inside the source repo for CI</h3> <pre> Key: OVIRT-1867 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Standard CI (Pipelines), STDCI DSL Reporter: Roman Mohr Assignee: infra Labels: credentials</pre> <p>In order to improve the self-service capabilities of standard-ci it is important for projects, that they can add their own secrets to projects (to reach external services, e.g. docker hub, …). Travis has a very nice system which helps engineers there: <a href="https://docs.travis-ci.com/user/encryption-keys/">https://docs.travis-ci.com/user/encryption-keys/</a> Basically the CI system needs to generate a public/private key pair for every enabled git repo. The engineer simply fetches the public key via a well know URL and encrypts the secrets. Then the encrypted secret can be made part of the source repo. Before the tests are run the CI system decrypts the secrets. Than can play together pretty well with Jenkinsfiles too. Benefit:</p> <pre>* Less manual intervention from CI team to add secrets to jobs * Strengthen the config-in-code thinking</pre></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1518095376-22378-218--

1 0

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

08 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87269,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87244,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87244,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87269/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/618/

1 0

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

08 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87268,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87244,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87244,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87268/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/615/

1 0

[CQ]: 87050, 8 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 08 Feb '18

08 Feb '18

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

1 0

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

08 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87267,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87244,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87244,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87267/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/611/

1 0

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 08-02-2018 ] [ 001_initialize_engine.initialize_engine ]
by Dafna Ron 08 Feb '18

08 Feb '18

Hi, We are failing test 001_initialize_engine.initialize_engine It seems that the issue is related to the ovirt-engine-dwhd.service not starting. *Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/86920/ <https://gerrit.ovirt.org/#/c/86920/> - * *core: adding key to bundles/AuditLogMessagesLink to Job:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5365/ <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5365/>Link to all logs:http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5365/art… <http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5365/artifact/>(Relevant) error snippet from the log: <error>Feb 7 22:43:23 lago-basic-suite-master-engine dbus[525]: [system] Reloaded configurationFeb 7 22:43:24 lago-basic-suite-master-engine firewalld[565]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.Feb 7 22:43:24 lago-basic-suite-master-engine firewalld[565]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.Feb 7 22:43:24 lago-basic-suite-master-engine firewalld[565]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.Feb 7 22:43:24 lago-basic-suite-master-engine firewalld[565]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.Feb 7 22:43:24 lago-basic-suite-master-engine firewalld[565]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.Feb 7 22:43:24 lago-basic-suite-master-engine firewalld[565]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.Feb 7 22:43:28 lago-basic-suite-master-engine firewalld[565]: WARNING: ICMP type 'beyond-scope' is not supported by the kernel for ipv6.Feb 7 22:43:28 lago-basic-suite-master-engine firewalld[565]: WARNING: beyond-scope: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.Feb 7 22:43:28 lago-basic-suite-master-engine firewalld[565]: WARNING: ICMP type 'failed-policy' is not supported by the kernel for ipv6.Feb 7 22:43:28 lago-basic-suite-master-engine firewalld[565]: WARNING: failed-policy: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.Feb 7 22:43:28 lago-basic-suite-master-engine firewalld[565]: WARNING: ICMP type 'reject-route' is not supported by the kernel for ipv6.Feb 7 22:43:28 lago-basic-suite-master-engine firewalld[565]: WARNING: reject-route: INVALID_ICMPTYPE: No supported ICMP type., ignoring for run-time.Feb 7 22:43:28 lago-basic-suite-master-engine systemd: Starting oVirt Engine fence_kdump listener...Feb 7 22:43:28 lago-basic-suite-master-engine systemd: Started oVirt Engine fence_kdump listener.Feb 7 22:43:28 lago-basic-suite-master-engine systemd: Reloading.Feb 7 22:43:28 lago-basic-suite-master-engine systemd: Starting oVirt Engine...Feb 7 22:43:28 lago-basic-suite-master-engine journal: 2018-02-07 22:43:28,908-0500 ovirt-engine: INFO _detectJBossVersion:187 Detecting JBoss version. Running: /usr/lib/jvm/jre/bin/java ['ovirt-engine-version', '-server', '-XX:+TieredCompilation', '-Xms1024M', '-Xmx1024M', '-Djava.awt.headless=true', '-Dsun.rmi.dgc.client.gcInterval=3600000', '-Dsun.rmi.dgc.server.gcInterval=3600000', '-Djsse.enableSNIExtension=false', '-XX:+HeapDumpOnOutOfMemoryError', '-XX:HeapDumpPath=/var/log/ovirt-engine/dump', '-Djava.util.logging.manager=org.jboss.logmanager', '-Dlogging.configuration=file:///var/lib/ovirt-engine/jboss_runtime/config/ovirt-engine-logging.properties', '-Dorg.jboss.resolver.warning=true', '-Djboss.modules.system.pkgs=org.jboss.byteman', '-Djboss.server.default.config=ovirt-engine', '-Djboss.home.dir=/usr/share/ovirt-engine-wildfly', '-Djboss.server.base.dir=/usr/share/ovirt-engine', '-Djboss.server.data.dir=/var/lib/ovirt-engine', '-Djboss.server.log.dir=/var/log/ovirt-engine', '-Djboss.server.config.dir=/var/lib/ovirt-engine/jboss_runtime/config', '-Djboss.server.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp', '-Djboss.controller.temp.dir=/var/lib/ovirt-engine/jboss_runtime/tmp', '-jar', '/usr/share/ovirt-engine-wildfly/jboss-modules.jar', '-mp', '/usr/share/ovirt-engine-wildfly-overlay/modules:/usr/share/ovirt-engine/modules/common:/usr/share/ovirt-engine-extension-aaa-jdbc/modules:/usr/share/ovirt-engine-extension-aaa-ldap/modules:/usr/share/ovirt-engine-wildfly/modules', '-jaxpmodule', 'javax.xml.jaxp-provider', 'org.jboss.as.standalone', '-v']Feb 7 22:43:29 lago-basic-suite-master-engine journal: 2018-02-07 22:43:29,481-0500 ovirt-engine: INFO _detectJBossVersion:207 Return code: 0, | stdout: '[u'WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final)'], | stderr: '[]'Feb 7 22:43:29 lago-basic-suite-master-engine systemd: Started oVirt Engine.Feb 7 22:43:29 lago-basic-suite-master-engine systemd: Reloading.Feb 7 22:43:29 lago-basic-suite-master-engine systemd: Starting oVirt Engine Data Warehouse...Feb 7 22:43:29 lago-basic-suite-master-engine systemd: Started oVirt Engine Data Warehouse.Feb 7 22:43:29 lago-basic-suite-master-engine systemd: Reloading.Feb 7 22:43:30 lago-basic-suite-master-engine systemd: Starting oVirt ImageIO Proxy...Feb 7 22:43:30 lago-basic-suite-master-engine systemd: Started oVirt ImageIO Proxy.Feb 7 22:43:30 lago-basic-suite-master-engine systemd: Reloading.Feb 7 22:43:30 lago-basic-suite-master-engine journal: 2018-02-07 22:43:30,301-0500 ovirt-engine-dwhd: ERROR run:554 Error: process terminated with status code 1Feb 7 22:43:30 lago-basic-suite-master-engine systemd: ovirt-engine-dwhd.service: main process exited, code=exited, status=1/FAILUREFeb 7 22:43:30 lago-basic-suite-master-engine systemd: Unit ovirt-engine-dwhd.service entered failed state.Feb 7 22:43:30 lago-basic-suite-master-engine systemd: ovirt-engine-dwhd.service failed.</error>*

1 0

[CQ]: 87194, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '18

08 Feb '18

A system test invoked by the "ovirt-master" change queue including change 87194,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 87181,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87181,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87194/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87181/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5385/

1 0

[CQ]: 87193, 2 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '18

08 Feb '18

A system test invoked by the "ovirt-master" change queue including change 87193,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 87181,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87181,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87193/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87181/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5380/

1 0

[CQ]: 86622, 16 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '18

08 Feb '18

A system test invoked by the "ovirt-master" change queue including change 86622,16 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 86920,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86920,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86622/16 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86920/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5375/

1 0

[CQ]: 87129, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Feb '18

08 Feb '18

A system test invoked by the "ovirt-master" change queue including change 87129,6 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 87181,2 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87181,2 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87129/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87181/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5370/

1 0

[CQ]: 86920,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 08 Feb '18

08 Feb '18

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

1 0

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

08 Feb '18

A system test invoked by the "ovirt-master" change queue including change 84401,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87116,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87116,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84401/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87116/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5359/

1 0

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

07 Feb '18

A system test invoked by the "ovirt-master" change queue including change 84400,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87116,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87116,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84400/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87116/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5353/

1 0

[CQ]: 84184, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-master" change queue including change 84184,7 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87116,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87116,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/84184/7 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87116/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5347/

1 0

[CQ]: 87285, 2 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87285,2 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86910,1 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86910,1 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87285/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86910/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/609/

1 0

[CQ]: 87286, 1 (ovirt-hosted-engine-setup) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87286,1 (ovirt-hosted-engine-setup) failed. However, this change seems not to be the root cause for this failure. Change 86910,1 (ovirt-hosted-engine-setup) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86910,1 (ovirt-hosted-engine- setup) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87286/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86910/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/608/

1 0

[CQ]: 87284, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87284,1 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86692,1 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86692,1 (ovirt-engine-api- model) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87284/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86692/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/606/

1 0

[CQ]: 87283, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87283,1 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86692,1 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86692,1 (ovirt-engine-api- model) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87283/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86692/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/604/

1 0

[CQ]: 87282, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87282,1 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86692,1 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86692,1 (ovirt-engine-api- model) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87282/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86692/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/601/

1 0

[CQ]: 82018, 9 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-master" change queue including change 82018,9 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87116,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87116,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/82018/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87116/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5341/

1 0

[CQ]: 87281, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87281,1 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86692,1 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86692,1 (ovirt-engine-api- model) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87281/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86692/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/599/

1 0

[CQ]: 87266, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87266,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87244,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87244,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87266/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/597/

1 0

[CQ]: 69504,1 (ovirt-engine-cli) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Feb '18

07 Feb '18

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

1 0

[CQ]: 87262, 2 (ovirt-wgt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87262,2 (ovirt-wgt) failed. However, this change seems not to be the root cause for this failure. Change 85162,1 (ovirt-wgt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85162,1 (ovirt-wgt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87262/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85162/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/594/

1 0

[CQ]: 87231, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-master" change queue including change 87231,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87116,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87116,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87231/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87116/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5336/

1 0

oVirt infra weekly meeting notes 07.02.2018
by Evgheni Dereveanchin 07 Feb '18

07 Feb '18

Hi everyone, Please find the topics of this week's infra meeting below: - New security advisory for Jenkins, patch updated OVIRT-1858 <https://ovirt-jira.atlassian.net/browse/OVIRT-1858> - Enable REST API for Gerrit OVIRT-1889 <https://ovirt-jira.atlassian.net/browse/OVIRT-1889> - ManageIQ deployed on Staging OVIRT-1803 <https://ovirt-jira.atlassian.net/browse/OVIRT-1803> - Request to deploy beaker OVIRT-1881 <https://ovirt-jira.atlassian.net/browse/OVIRT-1881> -- Regards, Evgheni Dereveanchin

1 0

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

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87258,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87244,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87244,1 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87258/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87244/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/592/

1 0

[oVirt CI] standard-enqueue - Build #9777 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 07 Feb '18

07 Feb '18

------=_Part_131_307129312.1518017524322 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/9777/ Build Name: #9777 Build Description: Gerrit: 69504 - ovirt-engine-cli (3.6, 4.1, 4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/69504 - title: cli: Fix SDK dependency - project: ovirt-engine-cli - branch: cli_3.6 - author: Juan Hernandez <juan.hernandez(a)redhat.com> ------=_Part_131_307129312.1518017524322--

1 0

[CQ]: 82234,1 (vcredist-x86) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Feb '18

07 Feb '18

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

1 0

[CQ]: 86867, 3 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 86867,3 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86692,1 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 86692,1 (ovirt-engine-api- model) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86867/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/86692/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/588/

1 0

[CQ]: 87244,1 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Feb '18

07 Feb '18

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

1 0

[JIRA] (OVIRT-1888) can_sudo function has to accept multiple positional parameters
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1518013245-10002-297 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1888?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1888: ---------------------------------- Assignee: Daniel Belenky (was: infra) Status: In Progress (was: To Do) > can_sudo function has to accept multiple positional parameters > -------------------------------------------------------------- > > Key: OVIRT-1888 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1888 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Currently, can_sudo function in global_setup and slave_cleanup is accepting only one param but in it's calls sometimes we pass more than one param to check for permissions. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518013245-10002-297 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1888?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1888:</h3> <pre>Assignee: Daniel Belenky (was: infra) Status: In Progress (was: To Do)</pre> <blockquote><h3>can_sudo function has to accept multiple positional parameters</h3> <pre> Key: OVIRT-1888 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1888 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Daniel Belenky Assignee: Daniel Belenky</pre> <p>Currently, can_sudo function in global_setup and slave_cleanup is accepting only one param but in it's calls sometimes we pass more than one param to check for permissions.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1518013245-10002-297--

1 0

[JIRA] (OVIRT-1890) Kill all lago processes during slave cleanup
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1890?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1890: ---------------------------------- Assignee: Daniel Belenky (was: infra) Status: In Progress (was: To Do) > Kill all lago processes during slave cleanup > -------------------------------------------- > > Key: OVIRT-1890 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1890 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Lago, oVirt CI > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Sometimes we end up having stale lago processes after builds are being aborted. > Until we'll find a permanent solution (such as a new runner for CI), we should add an ugly cleanup function to our slave cleanup to ensure lago is being killed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1890) Kill all lago processes during slave cleanup
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1518013160-31541-247 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1890?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-1890: ---------------------------------- Epic Link: OVIRT-400 > Kill all lago processes during slave cleanup > -------------------------------------------- > > Key: OVIRT-1890 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1890 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Lago, oVirt CI > Reporter: Daniel Belenky > Assignee: infra > > Sometimes we end up having stale lago processes after builds are being aborted. > Until we'll find a permanent solution (such as a new runner for CI), we should add an ugly cleanup function to our slave cleanup to ensure lago is being killed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518013160-31541-247 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1890?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky updated OVIRT-1890:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Kill all lago processes during slave cleanup</h3> <pre> Key: OVIRT-1890 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1890 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Lago, oVirt CI Reporter: Daniel Belenky Assignee: infra</pre> <p>Sometimes we end up having stale lago processes after builds are being aborted. Until we'll find a permanent solution (such as a new runner for CI), we should add an ugly cleanup function to our slave cleanup to ensure lago is being killed.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1518013160-31541-247--

1 0

[JIRA] (OVIRT-1890) Kill all lago processes during slave cleanup
by Daniel Belenky (oVirt JIRA) 07 Feb '18

07 Feb '18

Daniel Belenky created OVIRT-1890: ------------------------------------- Summary: Kill all lago processes during slave cleanup Key: OVIRT-1890 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1890 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Lago, oVirt CI Reporter: Daniel Belenky Assignee: infra Sometimes we end up having stale lago processes after builds are being aborted. Until we'll find a permanent solution (such as a new runner for CI), we should add an ugly cleanup function to our slave cleanup to ensure lago is being killed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1889) Configure gerrit-trigger plugin to use REST API
by Evgheni Dereveanchin (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1889?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1889: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Configure gerrit-trigger plugin to use REST API > ----------------------------------------------- > > Key: OVIRT-1889 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1889 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Currently Jenkins is configured to use SSH to query Gerrit. There is an option to enable the REST API as well which is useful when event-log plugin is installed on the Gerrit ( OVIRT-1196 ). > Jenkins tries to connect to the API to confirm if the plugin is installed which is currently flooding the logs with messages like this: > INFO: Started GerritMissedEventsPlaybackEnabledChecker > Feb 07, 2018 12:57:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.utils.GerritPluginChecker buildURL > WARNING: REST API is not enabled. > Feb 07, 2018 12:57:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.utils.GerritPluginChecker isPluginEnabled > WARNING: Not able to verify if Gerrit plugin events-log is installed. REST URL cannot be null. Is the REST API Enabled? > We should [configure|https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger#GerritTrigger-SetupRequirements] usage of the API to get rid of this message. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1889) Configure gerrit-trigger plugin to use REST API
by Evgheni Dereveanchin (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1518009294-31322-340 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Evgheni Dereveanchin created OVIRT-1889: ------------------------------------------- Summary: Configure gerrit-trigger plugin to use REST API Key: OVIRT-1889 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1889 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Currently Jenkins is configured to use SSH to query Gerrit. There is an option to enable the REST API as well which is useful when event-log plugin is installed on the Gerrit ( OVIRT-1196 ). Jenkins tries to connect to the API to confirm if the plugin is installed which is currently flooding the logs with messages like this: INFO: Started GerritMissedEventsPlaybackEnabledChecker Feb 07, 2018 12:57:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.utils.GerritPluginChecker buildURL WARNING: REST API is not enabled. Feb 07, 2018 12:57:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.utils.GerritPluginChecker isPluginEnabled WARNING: Not able to verify if Gerrit plugin events-log is installed. REST URL cannot be null. Is the REST API Enabled? We should [configure|https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger#GerritTrigger-SetupRequirements] usage of the API to get rid of this message. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1518009294-31322-340 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Evgheni Dereveanchin created OVIRT-1889:</h3> <pre> Summary: Configure gerrit-trigger plugin to use REST API Key: OVIRT-1889 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1889 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra</pre> <p>Currently Jenkins is configured to use SSH to query Gerrit. There is an option to enable the REST API as well which is useful when event-log plugin is installed on the Gerrit ( OVIRT-1196 ).</p> <p>Jenkins tries to connect to the API to confirm if the plugin is installed which is currently flooding the logs with messages like this: INFO: Started GerritMissedEventsPlaybackEnabledChecker Feb 07, 2018 12:57:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.utils.GerritPluginChecker buildURL WARNING: REST API is not enabled. Feb 07, 2018 12:57:06 PM com.sonyericsson.hudson.plugins.gerrit.trigger.utils.GerritPluginChecker isPluginEnabled WARNING: Not able to verify if Gerrit plugin events-log is installed. REST URL cannot be null. Is the REST API Enabled?</p> <p>We should [configure|<a href="https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger#GerritTrigger-SetupR…">https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger#GerritTrigger-SetupR…</a>] usage of the API to get rid of this message.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1518009294-31322-340--

1 0

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

07 Feb '18

A system test invoked by the "ovirt-master" change queue including change 86092,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 87116,5 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 87116,5 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/86092/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/87116/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5331/

1 0

[CQ]: 85162,1 (ovirt-wgt) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Feb '18

07 Feb '18

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

1 0