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.

Created attachment 436650 [details]
case creation failing

report currently displays the http headers in it's GTK screens to the customers. See attached screenshots.

Created attachment 436651 [details]
case creation succeeding

Sly / Denise -- this is a very easy fix for us which I'd like to get in if possible. It's very ugly in the GTK screens for report users, eg, selinux.

for the failure case, we should just display the message returned; for the success case, we should just say "thank you" and a reference to the newly created case in the portal.

In the end the safest change to accomplish this was just to not print out anything except the messages that the server sent for cases of success (http response codes 200 and 201) and user errror (400<=x<500).  For server error response codes (500 <= x < 600) we print out as much info as we have.

This means that to fully fix this we will need the server to improve the messages it sends.  This is in progress.

Someone, likely me, who knows what messages the server is sending will have to verify this bug.

Created attachment 439432 [details]
QA - server messages in report gui after moving bug to ON_QA

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.