RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2008575 - Doc-Only BZ for RHEL 9 release notes: Automatic removal of location constraint
Summary: Doc-Only BZ for RHEL 9 release notes: Automatic removal of location constraint
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: doc-Release_Notes-9-en-US
Version: 9.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: beta
: 9.0 Beta
Assignee: Lenka Špačková
QA Contact: RHEL DPM
Steven J. Levine
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-28 15:14 UTC by Steven J. Levine
Modified: 2021-11-08 10:03 UTC (History)
1 user (show)

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.
Clone Of:
Environment:
Last Closed: 2021-11-08 10:03:52 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-98364 0 None None None 2021-09-28 15:16:50 UTC

Description Steven J. Levine 2021-09-28 15:14:00 UTC 
This is a doc-only BZ for the RHEL 9 release notes, to document the feature noted in the RHEL 8.5 BZ https://bugzilla.redhat.com/show_bug.cgi?id=1847102.

For 8.5, this feature is in technology preview.  But for 9-Beta the HA product manager does not consider this tech preview (all of beta is tech preview), so the release note needs to reflect that.
Comment 1 Steven J. Levine 2021-09-28 15:20:40 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.
Comment 4 Lenka Špačková 2021-11-08 10:03:52 UTC 
Published:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9-beta/html-single/9.0_release_notes/index
Note You need to log in before you can comment on or make changes to this bug.