Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-35651

Discovery page fails with "too many redirects" when User role uses unrecognized search fields.

XMLWordPrintable

    • Bug Fix
    • Hide
      .Error message when discovered hosts are filtered with invalid filter fields

      Before this update, when users filtered discovered hosts by using an invalid field, such as `hostgroup`, the browser produced infinite redirects and failed.
      This release fixes the infinite redirect issue in discovered hosts for invalid filter fields.
      As a result, discovered hosts now display no hosts and log an error message with a reason.
      Show
      .Error message when discovered hosts are filtered with invalid filter fields Before this update, when users filtered discovered hosts by using an invalid field, such as `hostgroup`, the browser produced infinite redirects and failed. This release fixes the infinite redirect issue in discovered hosts for invalid filter fields. As a result, discovered hosts now display no hosts and log an error message with a reason.
    • Done
    • Manual

      Description of problem:

      When the user Role uses a Host filter using fields that are not available for Discovered Hosts. (E.g: Hostgroup) the "Discovered Hosts" returns infinite 302 until the browser fails with a "ERR_TOO_MANY_REDIRECTS"

      How reproducible:

      Always

      Is this issue a regression from an earlier version:

      No

      Steps to Reproduce:

      • Create a User Rol with a Host filter using any non-valid field for the Discovery search. E.g: "hostgroup = RHEL9_Clients"
      • Log in to Satellite with a user on that Role.
      • Go to "Hosts > All Hosts", here the filter works as expected showing only Hosts in "RHEL9_Clients" Hostgroup.
      • Go to "Hosts > Discovered Hosts"

      Actual behavior:
      the page breaks showing the too many redirects error. 

      Expected behavior:

      • The page should show an error message about the invalid field, but still load and show all the discovered Hosts.
      • Note that if there is no filter for the role and an invalid search field is manually introduced in the Discovered Hosts search box, it shows the appropriate error message: "Error:, ,Field 'hostgroup' not recognized for searching!" 

      Business Impact / Additional info:

      • Assign host provisioning and management to specific users/usergroups based on Hostgroups impacted.

              rhn-engineering-lstejska Leos Stejskal
              rhn-support-pafernan Pablo Fernandez Rodriguez
              Shubham Ganar Shubham Ganar
              Lena Ansorgová (zuansorg) Lena Ansorgová (zuansorg)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: