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.

Description of problem:
While 'pcs booth ticket add' validates a new ticket, 'pcs constraint ticket add' does not. This may lead to situations where a constraint is created for a ticket which cannot be added to booth configuration. Moreover, when creating a ticket constraint, a ticket is used as a part of the constraint id unsanitized. This may lead to an invalid CIB being dumped to the terminal.


Version-Release number of selected component (if applicable):
pcs-0.10.11-1
pcs-0.11.1-4


How reproducible:
always, easily


Steps to Reproduce:
1. pcs constraint ticket add "my super ticket" d1


Actual results:
Error: Unable to update cib
Call cib_apply_diff failed (-203): Update does not conform to the configured schema


Expected results:
An error message informing the user that the ticket name is not valid.


Additional info:
# pcs booth ticket add "my super ticket"
Error: booth ticket name 'my super ticket' is not valid, use alphanumeric chars or dash

*** This bug has been marked as a duplicate of bug 2053177 ***