Bug 1467699
| Summary: | (degenerate) case of running "pcs cluster stop" on a single node cluster should either not complain about quorum loss, or suggest --all rather than --force | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Jan Pokorný [poki] <jpokorny> |
| Component: | pcs | Assignee: | Tomas Jelinek <tojeline> |
| Status: | CLOSED WONTFIX | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9.0 | CC: | cluster-maint, idevat, mlisik, mpospisi, nhostako, omular, tojeline |
| Target Milestone: | rc | Keywords: | Reopened, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-24 07:27:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
(In reply to Jan Pokorný from comment #0) > There's no real notion of quorum in such a case, hence the warning > > > Error: Stopping the node will cause a loss of the quorum, use --force > > to override > > doesn't make much sense (at least without quorum devices at play). Running a one-node cluster doesn't make much sense either as it's not really HA. > Furthermore, it might be wise to suggest --all with an "if you indeed > want to stop whole cluster (X nodes) at once" subtext all the time, > because "cluster stop" may be the first choice when one wants to > achieve exactly this objective :) Fair point, we can add this. And I would also consider it a fix for the one-node cluster case. Re [comment 2]: > Running a one-node cluster doesn't make much sense either as it's > not really HA. That shifts discussion out of the scope -- can pcs bring you a single node setup? Certainly yes in the current shape. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |
There's no real notion of quorum in such a case, hence the warning > Error: Stopping the node will cause a loss of the quorum, use --force > to override doesn't make much sense (at least without quorum devices at play). Furthermore, it might be wise to suggest --all with an "if you indeed want to stop whole cluster (X nodes) at once" subtext all the time, because "cluster stop" may be the first choice when one wants to achive exactly this objective :)