[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 263
- Failure!
by jenkins@jenkins.phx.ovirt.org
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/263/
Build Number: 263
Build Status: Failure
Triggered By: Started by timer
-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #263
[Andrej Krejcir] HE: Test restarting HE VM
-----------------
Failed Tests:
-----------------
1 tests failed.
FAILED: 004_basic_sanity.snapshot_merge
Error Message:
status: 409
reason: Conflict
detail: Cannot create Snapshot. Snapshot is currently being created for VM vm0.
Stack Trace:
Traceback (most recent call last):
File "/usr/lib64/python2.7/unittest/case.py", line 369, in run
testMethod()
File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in wrapped_test
test()
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in wrapper
return func(get_test_prefix(), *args, **kwargs)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 68, in wrapper
return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs)
File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/004_basic_sanity.py", line 194, in snapshot_merge
api.vms.get(VM0_NAME).snapshots.add(dead_snap2_params)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 34511, in add
headers={"Correlation-Id":correlation_id, "Expect":expect}
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 79, in add
return self.request('POST', url, body, headers, cls=cls)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request
persistent_auth=self.__persistent_auth
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request
persistent_auth)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request
raise errors.RequestError(response_code, response_reason, response_body)
RequestError:
status: 409
reason: Conflict
detail: Cannot create Snapshot. Snapshot is currently being created for VM vm0.
6 years, 7 months
[JIRA] (OVIRT-2203) failure in update host caused patch to fail
by Dafna Ron (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2203?page=com.atlassian.jir... ]
Dafna Ron updated OVIRT-2203:
-----------------------------
Labels: ost_failures ost_infra ost_race (was: ost_failures ost_infra)
> failure in update host caused patch to fail
> -------------------------------------------
>
> Key: OVIRT-2203
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2203
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Dafna Ron
> Assignee: infra
> Labels: ost_failures, ost_infra, ost_race
>
> The patch failed due to failure to update the host:
> '2018-06-14 08:25:38,754-04 ERROR [org.ovirt.engine.core.bll.host.HostUpgradeManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [cb22fd71-b94d-4567-a8e4-78238868d2de] Failed to run check-update of host 'lago-basic-suite-master-
> host-0''
> I can see that the upgrade suite also failed for not seeing repos
> The next metrics build succeeded successfully so there is no need to do anything
> I cannot be sure but I think its probably a network glitch or jenkins issue which happened during the test run.
> here is the info from the mail:
> Change 92195,2 (ovirt-engine-metrics) 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/92195/2
> For failed test results see:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8213/
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[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)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2196?page=com.atlassian.jir... ]
Dafna Ron updated OVIRT-2196:
-----------------------------
Resolution: Fixed
Status: Done (was: To Do)
> 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)
6 years, 7 months
[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)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2196?page=com.atlassian.jir... ]
Dafna Ron commented on OVIRT-2196:
----------------------------------
lastest ovirt-engine passed successfully.
I am closing
> 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)
6 years, 7 months