Bug 2008575
| Summary: | Doc-Only BZ for RHEL 9 release notes: Automatic removal of location constraint | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Steven J. Levine <slevine> |
| Component: | doc-Release_Notes-9-en-US | Assignee: | Lenka Špačková <lkuprova> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | RHEL DPM <rhel-docs> |
| Severity: | unspecified | Docs Contact: | Steven J. Levine <slevine> |
| Priority: | medium | ||
| Version: | 9.0 | CC: | rhel-docs |
| Target Milestone: | beta | Keywords: | Documentation |
| Target Release: | 9.0 Beta | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
.Automatic removal of location constraint following resource move
When you execute the `pcs resource move` command, this adds a constraint to the resource to prevent it from running on the node on which it is currently running. By default, the location constraint that the command creates is automatically removed once the resource has been moved. This does not necessarily move the resources back to the original node; where the resources can run at that point depends on how you have configured your resources initially. If you would like to move a resource and leave the resulting constraint in place, use the `pcs resource move-with-contraint` command.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-08 10:03:52 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: | |||
|
Description
Steven J. Levine
2021-09-28 15:14:00 UTC
Original doc text: .Automatic removal of location constraint following resource move available as a Technology Preview When you execute the `pcs resource move` command, this adds a constraint to the resource to prevent it from running on the node on which it is currently running. A new --autodelete` option for the `pcs resource move`command is now available as a Technology Preview. When you specify this option, the location constraint that the command creates is automatically removed once the resource has been moved. New doc text: .Automatic removal of location constraint following resource move When you execute the `pcs resource move` command, this adds a constraint to the resource to prevent it from running on the node on which it is currently running. A new --autodelete` option for the `pcs resource move`command is now available. When you specify this option, the location constraint that the command creates is automatically removed once the resource has been moved. |