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 1892685 - pcs should keep XML IDs to a reasonable length [rhel-7.7.z]
Summary: pcs should keep XML IDs to a reasonable length [rhel-7.7.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.7
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1824206
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-29 13:04 UTC by RAD team bot copy to z-stream
Modified: 2020-11-24 11:02 UTC (History)
20 users (show)

Fixed In Version: pcs-0.9.167-3.el7_7.2
Doc Type: Bug Fix
Doc Text:
Cause: User creates a set constraint referencing several resources. Pcs generates an ID for such constraint by concatenating all the resources' names. Consequence: Resulting IDs may be extremely long which causes various issues. The IDs do not fit in pcs output and logs and are generally hard to work with. Fix: Auto-generated set constraints' IDs no longer consist of all resources referenced in constraints. Result: Reasonably short IDs fit better in pcs output, logs and are generally easier to work with.
Clone Of: 1824206
Environment:
Last Closed: 2020-11-24 10:57:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix + tests (44.15 KB, patch)
2020-11-03 12:43 UTC, Tomas Jelinek 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1387358 1 None None None 2023-05-27 09:47:35 UTC
Red Hat Knowledge Base (Solution) 3570291 0 None None None 2020-10-29 13:04:36 UTC
Red Hat Knowledge Base (Solution) 5236281 0 None None None 2020-10-29 13:04:36 UTC
Red Hat Product Errata RHBA-2020:3964 0 None None None 2020-10-29 13:04:36 UTC
Red Hat Product Errata RHBA-2020:5207 0 None None None 2020-11-24 10:57:17 UTC

Description RAD team bot copy to z-stream 2020-10-29 13:04:30 UTC 
This bug has been copied from bug #1824206 and has been proposed to be backported to 7.7 z-stream (EUS).
Comment 2 Tomas Jelinek 2020-11-03 12:43:49 UTC 
Created attachment 1726194 [details]
proposed fix + tests

Changed the way IDs for set constraints are generated, they no longer consist of full names of all resources in the constraints.

Generating other IDs was not changed. Plain constraints reference two resources, therefore there is no risk of 1KB+ IDs (unless the resource IDs are that long). Other IDs are either provided by the user or reasonably short. If you find it's not the case, feel free to open another BZ with a reproducer. If plain constraint IDs are still too long, feel free to open a BZ for that as well.


Test: Create set constraints with several resources. Check that the auto-generated constraint IDs are reasonably short.
Comment 3 Ivan Devat 2020-11-09 08:16:41 UTC 
Before Fix

[kid76 ~] $ rpm -q pcs
pcs-0.9.167-3.el7_7.1.x86_64

[kid76 ~] $ pcs constraint colocation set A B C
[kid76 ~] $ pcs cluster cib |grep pcs_rsc_colocation_set_A_B_C
      <rsc_colocation score="INFINITY" id="pcs_rsc_colocation_set_A_B_C">

After Fix

[kid76 ~] $ rpm -q pcs
pcs-0.9.167-3.el7_7.2.x86_64

[kid76 ~] $ pcs constraint colocation set A B C
[kid76 ~] $ pcs cluster cib |grep colocation_set_AABBCC
      <rsc_colocation score="INFINITY" id="colocation_set_AABBCC">
        <resource_set id="colocation_set_AABBCC_set">
Comment 11 errata-xmlrpc 2020-11-24 10:57:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (pcs bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:5207
Note You need to log in before you can comment on or make changes to this bug.