Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
The version of python-werkzeug in RHEL7/CentOS7 is currently problematic. Among other, it replaces "+" by " " in http forms, that breaks uploading ssh keys/deploy keys (which often contains "+").

All the unit-tests to pass on RHEL7 using a newer version of python-werkzeug (0.9.6, scratch-build: https://koji.fedoraproject.org/koji/taskinfo?taskID=32535657 )

Please upgrade werkzeug to at least 0.9.6 so that this issue goes away.

Version-Release number of selected component (if applicable):
0.9.1-2.el7

How reproducible:
Always

Steps to Reproduce:
1. Run the Pagure test suite as described here: https://pagure.io/pagure/commits/run_test_container


Actual results:
Test failures due to validation errors.

Expected results:
All tests pass.

Additional info:
This has a Fedora infrastructure ticket describing the issue too: https://pagure.io/fedora-infrastructure/issue/7542

For what it's worth, this is also a problem since Pagure is in EPEL7 proper, and we can't replace or update base packages for RHEL, including ones in Extras. I'd greatly appreciate this being fixed so this problem goes away.

This is definitely something that should be fixed upstream as it could affect multiple projects besides pagure.  As a licensed customer what do we need to do to have this looked at?

(In reply to Michael Watters from comment #3)
> This is definitely something that should be fixed upstream as it could
> affect multiple projects besides pagure.  As a licensed customer what do we
> need to do to have this looked at?

I think you need to file a request with Red Hat Support to have them fix it and reference this bug there.

Would be indeed good to have a status on this, as the scope is now wider, with CentOS having also git projects on pagure, so impacting CentOS contributors and also SIGs members (mostly Red Hat employees those days)

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.