Back to bug 2175797
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-03-06 14:59:59 UTC | Pool ID | sst_high_availability_rhel_9 | |
| Red Hat One Jira (issues.redhat.com) | 2023-03-06 15:01:54 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-150796 | |
| Tomas Jelinek | 2023-03-06 15:18:09 UTC | Severity | unspecified | low |
| Priority | unspecified | medium | ||
| Keywords | Triaged | |||
| Tomas Jelinek | 2023-07-28 09:09:29 UTC | Status | NEW | ASSIGNED |
| Tomas Jelinek | 2023-07-28 13:01:34 UTC | Blocks | 2227234 | |
| Tomas Jelinek | 2023-08-09 08:33:48 UTC | Doc Type | If docs needed, set a value | Enhancement |
| Target Release | --- | 9.4 | ||
| Status | ASSIGNED | POST | ||
| Doc Text | Feature: Provide a guidance in error messages when adding or removing a node in a cluster with odd number of nodes, SBD enabled without disks, and auto_tie_breaker disabled. Reason: Originally, pcs in this situation just informed, that it was going to enable auto_tie_breaker, and then exited with an error saying corosync was running. This was not explanatory and it didn't provide enough information for users to solve this issue. Result: Error messages have been updated. They now explain that auto_tie_breaker must be enabled due to SBD and provide instructions to stop the cluster, enable auto_tie_breaker, start the cluster and run command for adding or removing a node again. |
|||
| Red Hat Bugzilla | 2023-08-10 15:40:57 UTC | QA Contact | cluster-qe | cluster-qe |
Back to bug 2175797