On Wed, Aug 10, 2016 at 11:52 AM, Yedidyah Bar David <didi(a)redhat.com>
wrote:
>
> Can you give an update on this?
Should be fixed in 4.0.2:
https://bugzilla.redhat.com/show_bug.cgi?id=1348907
As a general note, if you see a bug on 4.0.z in MODIFIED or QA,
the fix is already in the nightly 4.0 repos, in case you feel like trying:
http://www.ovirt.org/develop/dev-process/install-nightly-snapshot/
Best,
--
Didi
Ok, thanks for the update and clarifications.
From an operational point of view, what will change?
RIght now,
in 4.0, if I select Default cluster and try to edit it and
upgrade its Compatibility Version to 4.0, it seems I don't get any message
in the gui, or at least I don't see it; it's something similar to when you
have sort of syntactical or incomplete error in your input) ...
and in engine.log I see
2016-08-10 11:59:43,780 WARN
[org.ovirt.engine.core.bll.storage.pool.UpdateStoragePoolCommand] (default
task-11) [6f626a79] Validation of action 'UpdateStoragePool' failed for
user admin@internal-authz. Reasons:
VAR__TYPE__STORAGE__POOL,VAR__ACTION__UPDATE,$ClustersList
Default,ERROR_CANNOT_UPDATE_STORAGE_POOL_COMPATIBILITY_VERSION_BIGGER_THAN_CLUSTERS
Instead in 4.0.2 it should allow me to do it so that I should see all
running VMs, inlcluded the hosted engine VM, marked with configuration
change needed symbol?
In this case for engine VM would it be sufficient to run something like
thsi to commit its modifications?
hosted-engine --set-maintenance --mode=global
shutdown engine VM from os console
hosted-engine --set-maintenance --mode=none
verify engine VM is automatically started and without the flag about
configuration changes needed?
Thanks,
Gianluca