+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1751215 +++ ====================================================================== Description of problem: After upgrading RHV environment, unable to change Graphical Console of HE VM which fails with message:- ~~~ Error while executing action: HostedEngine: There was an attempt to change Hosted Engine VM values that are locked. ~~~ In new HE deployment there is no lock for changing Graphical Console. Version-Release number of selected component (if applicable): ovirt-engine-4.3.5.5-0.1.el7.noarch ovirt-hosted-engine-setup-2.3.11-1.el7ev.noarch ovirt-ansible-hosted-engine-setup-1.0.26-1.el7ev.noarch How reproducible: Always Steps to Reproduce: 1. Deploy 4.1 HE environment. 2. Upgrade this environment to latest version 3. Change "Graphical Console" by editing HE VM Actual results: There was an attempt to change Hosted Engine VM values that are locked. Expected results: Should be able to change "Graphical Console" as in new deployment of HE environments of version 4.2 or 4.3 we do not have such lock. Additional info: (Originally by Ameya Charekar)
Let's try to fix this on engine-setup and warn engine vm needs restart (Originally by Sandro Bonazzola)
Moving back to assigned, due to the inability to make basic installation of 4.1 on my hosts. I'll check it back later, when corrected repos will be available for QA.
(In reply to Nikolai Sednev from comment #12) > Moving back to assigned, due to the inability to make basic installation of > 4.1 on my hosts. > I'll check it back later, when corrected repos will be available for QA. The fact you can't install 4.1 doesn't change that this bug is ON_QA. Nothing to be done on development side for this bug.
Bug #1815004 is not blocking this, it's just an issue on deploying the test environment.
As it was agreed, moving to verified forth to https://bugzilla.redhat.com/show_bug.cgi?id=1751215#c7.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1308