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

LCE id is not passed on Refresh counts trigger from WebUI

XMLWordPrintable

    • Moderate
    • Automated
    • None

      Description of problem:

      When we try to Refresh content counts for particular CV in a particular LCE on a Capsule, the LCE id does not seem to be passed to the Update Content Count task, so the CV counts get updated in every LCE as the result.

       

      How reproducible:

      always

       

      Is this issue a regression from an earlier version:

      no

       

      Steps to Reproduce:

          :setup:
              1. Satellite with registered external Capsule.
              2. Disabled automatic content counts update.

          :steps:
              1. Create two LCEs, assign them to the Capsule.
              2. Create and sync a repo, publish it in two CVs, promote both CVs to both LCEs.
              3. Ensure no counts were calculated yet for both CVs, both LCEs.
              4. Refresh counts for the first CV in the first LCE, check entity IDs in the Update task.
              5. Ensure the counts were updated for the first CV and
                 the second CV stayed untouched, as well as the second LCE.

       

      Actual behavior:

              4. environment_id is not specified in the task input

      { "options": \{ "environment_id": null, "content_view_id": 6, "repository_id": null }

      , "smart_proxy_id": 2, ... }

              5. First CV in the second LCE gets updated too.

       

      Expected behavior:
              4. environment_id related to the appropriate LCE is passed.
              5. First CV in the second LCE stays untouched (N/A counts displayed).

       

      Business Impact / Additional info:

       

              rh-ee-pshekar Pavan Soma Shekar
              vsedmik@redhat.com Vladimír Sedmík
              Vladimír Sedmík Vladimír Sedmík
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: