- Infra - oVirt List Archives

[JIRA] (OVIRT-2196) 4.2 ovirt-engine failing on cpu 002_bootstrap.update_default_cluster on basic suite: The chosen CPU is not supported
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2196?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2196: ---------------------------------- A new build was created for 4.2: https://gerrit.ovirt.org/#/c/92179/2 it was suppose to have passed but the build change is failing due to https://gerrit.ovirt.org/#/c/91980/7 A system test invoked by the "ovirt-4.2" change queue including change 92179,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91980,7 (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 91980,7 (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/92179/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91980/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2387/ > 4.2 ovirt-engine failing on cpu 002_bootstrap.update_default_cluster on basic suite: The chosen CPU is not supported > -------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-2196 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2196 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_code_regression, ost_failures > > The error is: The chosen CPU is not supported > 2018-06-13 04:19:26,203-04 WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_CPU_NOT_FOUND,VAR__TYPE__CLUSTER > 2018-06-13 04:19:26,204-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' > 2018-06-13 04:19:26,204-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] method: runAction, params: [UpdateCluster, ManagementNetworkOnClusterOperationParameters:{commandId='bab8f4a9-1ad6-4650-b92b-52c622fb7fd7', user='null', commandType='Unknown'}], timeElapsed: 49ms > 2018-06-13 04:19:26,208-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-16) [] Operation Failed: [Cannot edit Cluster. The chosen CPU is not supported.] > 2018-06-13 04:19:26,272-04 DEBUG [org.ovirt.engine.core.utils.timer.FixedDelayJobListener] (DefaultQuartzScheduler6) [] Rescheduling DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterSyncJob.refreshLightWeightData#-9223372036854775795 as there is no unfired trigger. > This is caused due to this change: https://gerrit.ovirt.org/#/c/91980/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

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

13 Jun '18

A system test invoked by the "ovirt-4.2" change queue including change 92179,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91980,7 (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 91980,7 (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/92179/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91980/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2387/

1 0

[JIRA] (OVIRT-2139) enforce SSL on jenkins.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2139?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2139: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > enforce SSL on jenkins.ovirt.org > -------------------------------- > > Key: OVIRT-2139 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2139 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > SSL was enabled on Jenkins with OVIRT-1471, this ticket is to transform the non-SSL virtual host into a redirect to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

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

13 Jun '18

A system test invoked by the "ovirt-4.2" change queue including change 92164,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91980,7 (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 91980,7 (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/92164/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91980/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2385/

1 0

[JIRA] (OVIRT-2197) ovirt-engine build-artifacts job failed due to No space left on device on the vm
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2197?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2197: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > ovirt-engine build-artifacts job failed due to No space left on device on the vm > -------------------------------------------------------------------------------- > > Key: OVIRT-2197 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2197 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_build-arifacts, ost_failures, ost_infra > > A patch failed to run on CQ because of failed build-artifacts job. > the error was: > '08:13:09 [EnvInject] - Variables injected successfully. > 08:13:09 [EnvInject] - Injecting contributions. > 08:13:09 Building remotely on vm0092.workers-phx.ovirt.org (libvirt el7 phx nested) in workspace /home/jenkins/workspace/ovirt-engine_master_build-artifacts-el7-x86_64 > 08:13:09 [ssh-agent] Looking for ssh-agent implementation... > 08:13:09 [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) > 08:13:09 $ ssh-agent > 08:13:09 [ssh-agent] Java/JNR ssh-agent > 08:13:10 ERROR: [ssh-agent] Could not register BouncyCastle on the remote agent. > 08:13:10 java.nio.file.FileSystemException: /tmp/resource-673894941857540110: No space left on device > 08:13:10 at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) > 08:13:10 at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) > 08:13:10 at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)' > Evgheni looked at the vm and the df seems to be ok now so the cleanup jobs helped. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2197) ovirt-engine build-artifacts job failed due to No space left on device on the vm
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

Dafna Ron created OVIRT-2197: -------------------------------- Summary: ovirt-engine build-artifacts job failed due to No space left on device on the vm Key: OVIRT-2197 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2197 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra A patch failed to run on CQ because of failed build-artifacts job. the error was: '08:13:09 [EnvInject] - Variables injected successfully. 08:13:09 [EnvInject] - Injecting contributions. 08:13:09 Building remotely on vm0092.workers-phx.ovirt.org (libvirt el7 phx nested) in workspace /home/jenkins/workspace/ovirt-engine_master_build-artifacts-el7-x86_64 08:13:09 [ssh-agent] Looking for ssh-agent implementation... 08:13:09 [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) 08:13:09 $ ssh-agent 08:13:09 [ssh-agent] Java/JNR ssh-agent 08:13:10 ERROR: [ssh-agent] Could not register BouncyCastle on the remote agent. 08:13:10 java.nio.file.FileSystemException: /tmp/resource-673894941857540110: No space left on device 08:13:10 at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) 08:13:10 at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) 08:13:10 at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)' Evgheni looked at the vm and the df seems to be ok now so the cleanup jobs helped. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2196) 4.2 ovirt-engine failing on cpu 002_bootstrap.update_default_cluster on basic suite: The chosen CPU is not supported
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

Dafna Ron created OVIRT-2196: -------------------------------- Summary: 4.2 ovirt-engine failing on cpu 002_bootstrap.update_default_cluster on basic suite: The chosen CPU is not supported Key: OVIRT-2196 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2196 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra The error is: The chosen CPU is not supported 2018-06-13 04:19:26,203-04 WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,ACTION_TYPE_FAILED_CPU_NOT_FOUND,VAR__TYPE__CLUSTER 2018-06-13 04:19:26,204-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}' 2018-06-13 04:19:26,204-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-16) [593df572-8cee-424e-a106-ff584f2f0027] method: runAction, params: [UpdateCluster, ManagementNetworkOnClusterOperationParameters:{commandId='bab8f4a9-1ad6-4650-b92b-52c622fb7fd7', user='null', commandType='Unknown'}], timeElapsed: 49ms 2018-06-13 04:19:26,208-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-16) [] Operation Failed: [Cannot edit Cluster. The chosen CPU is not supported.] 2018-06-13 04:19:26,272-04 DEBUG [org.ovirt.engine.core.utils.timer.FixedDelayJobListener] (DefaultQuartzScheduler6) [] Rescheduling DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterSyncJob.refreshLightWeightData#-9223372036854775795 as there is no unfired trigger. This is caused due to this change: https://gerrit.ovirt.org/#/c/91980/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 91730,10 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 13 Jun '18

13 Jun '18

Change 91730,10 (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/91730/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8191/

1 0

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

13 Jun '18

A system test invoked by the "ovirt-4.2" change queue including change 92158,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91980,7 (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 91980,7 (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/92158/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91980/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2383/

1 0

[JIRA] (OVIRT-2195) race in 004_basic_sanity.verify_vm_import
by Dafna Ron (oVirt JIRA) 13 Jun '18

13 Jun '18

Dafna Ron created OVIRT-2195: -------------------------------- Summary: race in 004_basic_sanity.verify_vm_import Key: OVIRT-2195 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2195 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra We have a race that causes test: 004_basic_sanity.verify_vm_import to fail This build: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8183/ failed but there is nothing in the log to suggest that the import failed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0