Search results

WARN for the node level maintenance mode

Status: Open.

#2147 In ClusterLabs/crmsh;

· zzhou1 opened on Jul 2, 2026

False positive Qdevice vote warning during cluster start

Status: Open.

#2146 In ClusterLabs/crmsh;

· nicholasyang2022 opened on Jul 2, 2026

Command crm configure user should be dropped

Status: Open.

#2137 In ClusterLabs/crmsh;

· liangxin1300 opened on Jun 19, 2026

crmsh.log lack marker to distinguish user command from internal sub-commands

Status: Open.

#2134 In ClusterLabs/crmsh;

· zzhou1 opened on Jun 17, 2026

Improve completers

Status: Open.

#2115 In ClusterLabs/crmsh;

· liangxin1300 opened on May 21, 2026

The -e option of crm report is not implemented yet

Status: Open.

#2109 In ClusterLabs/crmsh;

· liangxin1300 opened on May 9, 2026

Modernize crmsh configs: defaults in /usr/etc, custom in /etc

Status: Open.

#2096 In ClusterLabs/crmsh;

· zzhou1 opened on Apr 22, 2026

Refactor confusing -F/-f/--force/force/-y/--yes option handling, scope and man page

Status: Open.

#2095 In ClusterLabs/crmsh;

· zzhou1 opened on Apr 22, 2026

Reject or add --force to bootstrap qnetd with the same cluster name when the existing one is stopped

Status: Open.

#2080 In ClusterLabs/crmsh;

· zzhou1 opened on Apr 13, 2026

Add corosync checker function to warn users to restart corosync

Status: Open.

#2066 In ClusterLabs/crmsh;

· zzhou1 opened on Mar 27, 2026

Regression: remove powered-off node from cluster

Status: Open.

#2064 In ClusterLabs/crmsh;

· zzhou1 opened on Mar 26, 2026

Shouldn't set fencing-enabled back to false

Status: Open.

#2057 In ClusterLabs/crmsh;

· liangxin1300 opened on Mar 19, 2026