Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-18825

As a Discovery dev, I want to optimize the search parameters in Discovery when querying OCM for subscription data

XMLWordPrintable

    • Installer Sprint 2025-56, Installer Sprint 2025-57
    • None

      Value Statement

      In MCE 2.8, we identified an issue where querying OCM for a large subscription data set resulted in some subscriptions being lost. Increasing the request size from 1000 to 1500 helped recover the missing clusters, but a more efficient solution would be to refine the search parameters used in our queries to OCM.

      The attached screenshot displays the parameters OCM is using, so we should aim to align our search criteria accordingly.

      Current query:

      "search":["updated_at >= '2025-03-09T13:45:23'"],"size":["1000"] 
      

      New query:

      {"orderBy":["created_at desc"],"page":["1"],"search":["status NOT IN ('Deprovisioned', 'Archived', 'Reserved')","updated_at >= '2025-03-31T12:21:17'", "external_cluster_id is not null"],"size":["1000"]} 

      Definition of Done for Engineering Story Owner (Checklist)

      • [x] Discovery can query OCM for subscription data more efficiently.
      • [x] Discovery can retrieve all relevant clusters based on the selected filters.

      Development Complete

      • The code is complete.
      • Functionality is working.
      • Any required downstream Docker file changes are made.

      Tests Automated

      • [ ] Unit/function tests have been automated and incorporated into the
        build.
      • [ ] 100% automated unit/function test coverage for new or changed APIs.

      Secure Design

      • [ ] Security has been assessed and incorporated into your threat model.

      Multidisciplinary Teams Readiness

      • [ ] Create an informative documentation issue using the Customer

      Portal Doc template that you can access from [The Playbook](

      https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

      and ensure doc acceptance criteria is met.

      • Call out this sentence as it's own action:
      • [ ] Link the development issue to the doc issue.

      Support Readiness

      • [ ] The must-gather script has been updated.

              dbennett@redhat.com Disaiah Bennett
              dbennett@redhat.com Disaiah Bennett
              Matthew Smigielski Matthew Smigielski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: