Description of problem:
Running rhevm-cli-22.214.171.124-3.el6ev.noarch with rhevm 3.5 (master)
trying to update policy to powersaving
update cluster RestCluster7 --scheduling_policy-thresholds-low 20 --scheduling_policy-policy 'power_saving' --correlation_id 316
doesn't update and the policy remains as it were before.
can you please test with matching versions of cli and engine? We did some changes to the REST API with regards to scheduling policy and we would like to know if it works 3.4-3.4 and 3.5-3.5.
now that there is a 3.5 tag available
any chance of providing us a brew build of rhevm-cli 3.5?
Ohad, can you please re-test as Martin asked in comment 2?
I dont see that test in the new unittest regression_mixed job.
it's running with the latest rhevm-cli from brew.
The only test that seems to be related is:
is it the same test?
if it is, then it's still failing
this bug is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1118384 (opened in upstream) & it was fixed in the previos build --> REST & Java are working (run the same test on them and you will see it passes or see our Jenkins http://jenkins.qa.lab.tlv.redhat.com:8080/view/Infra/job/3.5-regression_mixed/68/testReport/)
SDK & CLI are still failing but I believe it is related to this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1122546 - update fails in SDK & CLI for several entities
(In reply to Nelly Credi from comment #10)
> this bug is a duplicate of
> https://bugzilla.redhat.com/show_bug.cgi?id=1118384 (opened in upstream) &
> it was fixed in the previos build --> REST & Java are working (run the same
> test on them and you will see it passes or see our Jenkins
> SDK & CLI are still failing but I believe it is related to this bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1122546 - update fails in SDK &
> CLI for several entities
Since Bug 1122546 is in modified can you check if it resolves the problem?
Either way, can we close this issue as a dup of 1118384?
It can only be tested in dev CI
Ohad, can you please check it?
& is it ok to close this bug as a duplicate? as I wrote it was verified in upstream with REST API
we can close it.
it's working properly
*** This bug has been marked as a duplicate of bug 1118384 ***