Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
I'm unable to preview hosts to execute the job on when query is too long (e.g. after "rerun failed" with 233 failed jobs as it generates query like "name = ... or name = ... or ...")
Version-Release number of selected component (if applicable):
satellite-6.2.4-1.0.el7sat.noarch
How reproducible:
Steps to Reproduce:
1. Have very long search query when scheduling new job. In my case it was 9910 characters of query like "name = docker18container107.example.com or name = docker8container103.example.com or ..."
2. Click "Preview" button
Actual results:
Empty window appears with no indication that something went wrong (BAD). Only FF network console shows that request returned "414 Request-URI Too Long" (well, BAD as well)
Expected results:
Either proper error message with explanation or it should work.
Additional info:
This made ma a bit confused as "Refresh" button seemed to work and sumber shown 233 hosts and when launched, job was really scheduled on 233 systems.