[ https://ovirt-jira.atlassian.net/browse/OVIRT-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37063#comment-37063 ] 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)