Description of problem:
In a HC scenario, I'm trying to move to hosts to maint.
- Ignore Gluster Quorum and Self-Heal validations
- Stop Gluster service
(which is the default), yet it still fails with:
Error while executing action: Cannot switch the following Host(s) to Maintenance mode: lago-hc-basic-suite-4-2-host1,lago-hc-basic-suite-4-2-host2.
Gluster quorum will be lost for the following Volumes: vmstore,engine,data.
Version-Release number of selected component (if applicable):
(In reply to Yaniv Kaul from comment #0)
> Description of problem:
> In a HC scenario, I'm trying to move to hosts to maint.
> I've *unchecked*:
> - Ignore Gluster Quorum and Self-Heal validations
If I don't check this, in HC, I cannot move hosts to maintenance. So why allow it just to fail?
I think this is the confusion here.
You cannot move more than one host to maintenance if you want a working environment. In this case it looks like lago-hc-basic-suite-4-2-host1,lago-hc-basic-suite-4-2-host2 are being moved.
When a host is being moved to maintenance, we don't correlate with the value of "Stop Gluster service" - it is assumed that there will be an issue with host. This I think, is the confusion
An option is to prompt user and ask whether to ignore checks as more than 1 host is moved with a warning - will that work?
(In reply to Sahina Bose from comment #3)
> An option is to prompt user and ask whether to ignore checks as more than 1
> host is moved with a warning - will that work?
Anything that will not make the user click 'OK' then fail makes sense to me. There's no point in letting him fail if we know this is going to be the result.
This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
What's the next step?
Will add validation and include it in 4.3.1
(In reply to Yaniv Kaul from comment #6)
> What's the next step?
Addressed in 4.3.1
Moving this to ovirt-4.3.2 as ovirt-4.3.1 already released.
Moving this to ovirt-4.3.3 as ovirt-4.3.2 has been already released.
As ovirt-4.3.3 next build includes only blockers, so moving this to 4.3.4
Moving the bug to verified state.
Fixed version: rhvh-126.96.36.199
Now, its possible to move the host's into maintenance without unchecking ( which is by default) - Ignore Gluster Quorum and Self-Heal validations without any error messages.
This bugzilla is included in oVirt 4.3.7 release, published on November 21st 2019.
Since the problem described in this bug report should be
resolved in oVirt 4.3.7 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.