Uploaded image for project: 'Red Hat Insights Engineering'
  1. Red Hat Insights Engineering
  2. RHINENG-11307

The Advisor Recommendations are not showing the correct affected system count always

XMLWordPrintable

    • Moderate
    • 5

      ** Note that this is a public ticket, please refrain from adding any sensitive data. **

      Description of Problem

      When checking out the Advisor Recommendations, Either some recommendations are not showing the correct system counts or the count is correct and when you go into the Recommendation, it either shows no systems or wrong count of systems listed. 

      How reproducible

      (Always with specific Recommendations I believe)

      Steps to Reproduce and Actual Behavior

      1. Access https://console.redhat.com/insights/advisor/recommendations
      2. Look at the table and search for "Unexpected behavior when using deprecated access control directives in httpd 2.4" recommendation
      1. Right now for the 540155 account, It shows `1` in the `Systems` column But if i click open the Recommendation or click on the `1`, It lists 0 systems and says `0 Total Systems`
      2. Similarly if we check the recommendation "The vmcore generation fails in RHEL 8.6 when "cgroup_disable=memory" is configured due to a known bug in the running kernel" , It shows `23` in the Systems column but going inside, It will show `19 Total systems`

       

      I am assuming that The System Count on the main Recommendations page, is not up-to-date for many Recommendations listed there

      Expected Behavior

      Whatever count is listed in Systems column, The same amount of systems should be listed when opening the actual recommendation and trying to check it's details. 

      Business Impact / Additional info

       

      Undefined list of systems or Incorrect display of affected systems

            pwayper-insights Paul Wayper
            rhn-support-saydas Sayan Das
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: