Bug 1537630 - Hosted engine VM cannot be edited using the UI, because it has priority 0
Summary: Hosted engine VM cannot be edited using the UI, because it has priority 0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-setup
Classification: oVirt
Component: General
Version: 2.2.6
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ovirt-4.2.1
: ---
Assignee: Simone Tiraboschi
QA Contact: Nikolai Sednev
URL:
Whiteboard:
Depends On:
Blocks: 1458709
TreeView+ depends on / blocked
 
Reported: 2018-01-23 16:32 UTC by Andrej Krejcir
Modified: 2018-02-12 11:49 UTC (History)
3 users (show)

Fixed In Version: ovirt-hosted-engine-setup-2.2.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-12 11:49:50 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: blocker+
sbonazzo: devel_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 86731 0 'None' MERGED ansible: target_vm: force priority at DB level 2020-06-17 13:03:25 UTC

Description Andrej Krejcir 2018-01-23 16:32:07 UTC
Description of problem:
After the hosted engine is deployed using ansible, the created VM has priority 0.
When the VM is edited in the UI, the update command wants to change the priority, which is not allowed for the HE VM.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup - 2.2.7-0.0.master.20180122124130
ovirt-hosted-engine-ha - 2.2.5-0.0.master.20180117160214
ovirt-engine - 4.2.1.2-0.0.master.20180115100502

How reproducible:
Always

Steps to Reproduce:
1. Deploy hosted engine using ansible. (`hosted-engine --deploy --ansible`)
2. In the UI, open the edit VM dialog for the HE, do not change anything and click OK.

Actual results:
The edit fails with error "There was an attempt to change Hosted Engine VM values that are locked.".

Expected results:
Edit succeeds.

Comment 1 Simone Tiraboschi 2018-01-23 17:46:25 UTC
According to its documentation we cannot set the priority with the current ovirt_vms ansible module:
http://docs.ansible.com/ansible/latest/ovirt_vms_module.html

Comment 2 Yaniv Kaul 2018-01-24 07:47:47 UTC
(In reply to Simone Tiraboschi from comment #1)
> According to its documentation we cannot set the priority with the current
> ovirt_vms ansible module:
> http://docs.ansible.com/ansible/latest/ovirt_vms_module.html

Is there a bug about this? Seems like we need to fix this ASAP?

Comment 3 Simone Tiraboschi 2018-01-24 09:18:43 UTC
(In reply to Yaniv Kaul from comment #2)
> Is there a bug about this?

I just filed it: https://github.com/ansible/ansible/issues/35268

> Seems like we need to fix this ASAP?

Yes, absolutely: being able to edit the engine VM from the engine is a must.
If a proper fix takes too much we should at least implement a workaround as https://gerrit.ovirt.org/#/c/86731/

Comment 4 Nikolai Sednev 2018-01-28 16:25:59 UTC
Works for me on these components:
ovirt-hosted-engine-ha-2.2.5-0.0.master.20180125081710.20180125081707.git6046986.el7.centos.noarch
ovirt-hosted-engine-setup-2.2.9-0.0.master.20180124164059.git097610a.el7.centos.noarch
ovirt-engine-appliance-4.2-20180127.1.el7.centos.noarch
Linux 3.10.0-693.17.1.el7.x86_64 #1 SMP Sun Jan 14 10:36:03 EST 2018 x86_64 x86_64 x86_64 GNU/Linux

After editing and clicking on OK, UI acted like it was saving with visually spinning blue circle and closed the UI edit prompt without any issues.

Moving to verified.

Comment 5 Sandro Bonazzola 2018-02-12 11:49:50 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.