Description of problem: customer would like to have option to rename HostedEngine VM name to the format location-HostedEngine - for example brq-HostedEngine Version-Release number of selected component (if applicable): RHV 4.2.7 Currently once vm name is altered, engine is not capable of adding hosted engine enabled hosts, reinstalling them or migrating HostedEngine VM, as engine consider hosted engine as not imported yet
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag.
Moving to 4.3.2 not being identified as blocker for 4.3.1.
Looking for workaround this problem year from 4.2.4 version
According to Simone this should be now easy enough to fix. In the past the engine was detecting the engine VM based on the name but now (>=4.2) with node 0 we have a specif flag in the DB and we are setting it at setup time regardless of VM name. It will require a proper testing for the CLI utilities, the cockpit summary page and so on
Sorted out it requires a bit more work.
Re-targeting to 4.3.6 not being identified as blocker for 4.3.5.
I'm not able to edit the name in existing engine, is this supposed to be working only for new engines? I'm getting: <fault> <detail>[There was an attempt to change Hosted Engine VM values that are locked.]</detail> <reason>Operation Failed</reason> </fault> I think it's more important for this to work with existing engines rather than only new ones. Tested on ovirt-engine-4.3.7.2-0.1.el7.noarch
(In reply to Petr Matyáš from comment #10) > I'm not able to edit the name in existing engine, is this supposed to be > working only for new engines? Yes, it was for new deployments only. If we want to unlock it as a day-2 operation on existing deployments we also need something like: https://gerrit.ovirt.org/104769
(In reply to Simone Tiraboschi from comment #11) > (In reply to Petr Matyáš from comment #10) > > I'm not able to edit the name in existing engine, is this supposed to be > > working only for new engines? > > Yes, it was for new deployments only. > If we want to unlock it as a day-2 operation on existing deployments we also > need something like: > https://gerrit.ovirt.org/104769 I think rename day-2 is most good solution, and it what needed. We use name convention, and must hack our code for correct behavior for name "HostedEngine".
do you want to continue on improving this as a day-2 in 4.4.z or defer to 4.5? It doesn't sound like too high prio (and the original targeting to 4.4.2 is from 2020-01-10) so 4.5 makes sense
(In reply to Michal Skrivanek from comment #14) > do you want to continue on improving this as a day-2 in 4.4.z or defer to > 4.5? It doesn't sound like too high prio (and the original targeting to > 4.4.2 is from 2020-01-10) so 4.5 makes sense it's in :-)
Verified on ovirt-engine-4.4.3.3-0.19.el8ev.noarch
Hi Asaf, please review this doc text for the errata: This enhancement allows the user to customize the HostedEngine VM name in a Self-Hosted Engine deployment.
(In reply to Eli Marcus from comment #21) > Hi Asaf, please review this doc text for the errata: > > This enhancement allows the user to customize the HostedEngine VM name in a > Self-Hosted Engine deployment. I've updated the doc text, now, with this RFE, we can rename the HostedEngine VM name after the deployment.
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 (Low: Red Hat Virtualization security, bug fix, and enhancement update), 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:5179