[JIRA] (OVIRT-2139) enforce SSL on jenkins.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-2139:
-------------------------------------------
Summary: 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: infra
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)
6 years, 7 months
[JIRA] (OVIRT-2137) default updated cluster test fails -
ACTION_TYPE_FAILED_CPU_NOT_FOUND
by Dafna Ron (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2137?page=com.atlassian.jir... ]
Dafna Ron reassigned OVIRT-2137:
--------------------------------
Assignee: Dafna Ron (was: infra)
> default updated cluster test fails - ACTION_TYPE_FAILED_CPU_NOT_FOUND
> ---------------------------------------------------------------------
>
> Key: OVIRT-2137
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2137
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Dafna Ron
> Assignee: Dafna Ron
> Labels: cq-issue-traking, ost_code_regression, ost_failures
>
> Change 91888,3 (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/91888/3
> For failed test results see:
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8033/
> I think that we are sending a request to cpu and because of the change done on NULL strings we are failing to get type of cpu which fails the test:
> ' 2018-06-04 11:57:19,852-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Lock Acquired to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}'
> 2018-06-04 11:57:19,857-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Compiled stored procedure. Call string is [{call getvdsbyclusteri
> d(?, ?, ?)}]
> 2018-06-04 11:57:19,857-04 DEBUG [org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] SqlCall for procedure [GetVdsByClusterId] compiled
> 2018-06-04 11:57:19,878-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] method: getAllForCluster, params: [9cbb05e6-680f-11e8-b07e-5452c0a8c904], timeE
> lapsed: 25ms
> 2018-06-04 11:57:19,879-04 WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUST
> ER,VAR__ACTION__UPDATE,VAR__TYPE__CLUSTER,ACTION_TYPE_FAILED_CPU_NOT_FOUND
> 2018-06-04 11:57:19,881-04 INFO [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] Lock freed to object 'EngineLock:{exclusiveLocks='[]', sharedLocks='[]'}'
> 2018-06-04 11:57:19,881-04 DEBUG [org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor] (default task-6) [72cc0877-c16d-4539-a3d0-90cd3c4a7a84] method: runAction, params: [UpdateCluster, ManagementNetworkOnClusterOperationP
> arameters:{commandId='36bf82e7-eec8-4b36-99af-db5ade902593', user='null', commandType='Unknown'}], timeElapsed: 58ms
> 2018-06-04 11:57:19,886-04 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-6) [] Operation Failed: [Cannot edit Cluster. The chosen CPU is not supported.]
> '
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months