-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'crm configure delete' don't complete existing id like before #1460
Comments
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jun 21, 2024
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jun 21, 2024
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jun 21, 2024
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jun 21, 2024
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jun 21, 2024
…sterLabs#1460 If you type $ crm configure delete of do it interactively $ crm configure crm(live/node1)configure# delete and then double press tab it, should propose possible resource options. And this commit makes it working again.
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jun 21, 2024
…lusterLabs#1460 If you type $ crm configure delete of do it interactively $ crm configure crm(live/node1)configure# delete and then double press tab it, should propose possible resource options. And this commit makes it working again.
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jun 25, 2024
…lusterLabs#1460 If you type $ crm configure delete of do it interactively $ crm configure crm(live/node1)configure# delete and then double press tab it, should propose possible resource options. And this commit makes it working again.
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jun 25, 2024
…lusterLabs#1460 If you type $ crm configure delete of do it interactively $ crm configure crm(live/node1)configure# delete and then double press tab it, should propose possible resource options. And this commit makes it working again.
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jun 25, 2024
…lusterLabs#1460 If you type $ crm configure delete of do it interactively $ crm configure crm(live/node1)configure# delete and then double press tab it, should propose possible resource options. And this commit makes it working again.
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jun 27, 2024
…lusterLabs#1460 If you type $ crm configure delete of do it interactively $ crm configure crm(live/node1)configure# delete and then double press tab it, should propose possible resource options. And this commit makes it working again.
liangxin1300
added a commit
that referenced
this issue
Jun 28, 2024
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jul 1, 2024
…lusterLabs#1460 If you type $ crm configure delete of do it interactively $ crm configure crm(live/node1)configure# delete and then double press tab it, should propose possible resource options. And this commit makes it working again.
aleksei-burlakov
pushed a commit
to aleksei-burlakov/crmsh
that referenced
this issue
Jul 1, 2024
…rLabs#1403 ClusterLabs#1460 backport ClusterLabs#1469 If you type $ crm configure delete of do it interactively $ crm configure crm(live/node1)configure# delete and then double press tab it, should propose possible resource options. And this commit makes it working again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It should be a regression issue which was introduced by #1403
The text was updated successfully, but these errors were encountered: