Hide Forgot
Description of problem: we are failing ost test 002_bootstrap.update_default_cluster with error: Fault reason is "Operation Failed". Fault detail is "[Cannot edit Cluster. The chosen CPU is not supported.]". HTTP response code is 400. Version-Release number of selected component (if applicable): 4.2 How reproducible: Steps to Reproduce: 1. run ost with lago on 4.2 master suite (./run_suite basic_suite_master) 2. 3. Actual results: we fail test 002_bootstrap.update_default_cluster Expected results: we should succeed. Additional info: logs located here: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/1181/artifact/exported-artifacts/basic-suit-4.2-el7/test_logs/basic-suite-4.2/post-002_bootstrap.py/
Michal - this is happening when trying to update the Cluster CPU to PPC.
Raz, please see if it reproduces on 4.1. The test is simple - change the CPU of a non-active cluster (with no hosts, etc.) from X86 to PPC.
Tested on rhevm-4.1.10.3-0.1.el7.noarch Edited CPU arch from x86_64 to PPC - Pass
(In reply to Raz Tamir from comment #3) > Tested on rhevm-4.1.10.3-0.1.el7.noarch > > Edited CPU arch from x86_64 to PPC - Pass that was probably not tested using API, was it? With the infra changes merged to 4.1 it's supposed to fail the same way as it did on 4.2 and master
Reproduced in automation on the upgraded engine from 4.1 to 4.2. When updating version of Default (not initialized) cluster form 4.1 to 4.2 Test Name: rhv_upgrade.common_upgrade_test.TestUpgradeCommon.test_upgrade_clusters Test Description: This tests upgrades all clusters to latest versions Iteration number: 4 Update cluster Default with {'version': '4.2'} Using Correlation-Id: clusters_update_71179464-6f42-4bd7 Failed to update element NOT as expected: Status: 400 Reason: Bad Request Detail: [Cannot edit Cluster. The chosen CPU is not supported.] Response code is not valid, expected is: [200, 201], actual is: 400 Failed to update cluster default with {'version': '4.2'} Assing Automation, Automation Blocker, and Regression - found in automation, blocking upgrade tests, regression as test-cases passed in previous runs.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
this is the same failure as discussed in bug 1585990 (this bug was reported quite a lot earlier but the other one has more details and tracks the actual fix, so closing it this way) *** This bug has been marked as a duplicate of bug 1585990 ***