Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-2347

Collections in `staging` repo are not deleted after selecting a repo for approval- on console.stage

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • Unspecified
    • Backend
    • False
    • Hide

      None

      Show
      None
    • False
    • Moderate

      When selecting a repo for approval, `validated` or `certified`, the collection is copied to the selected repo but also remains in `staging` with the approval button available to select.

      Steps to Reproduce

      1. Sign a collection
      2. Click Approve
      3. Repo selection screen appears
      4. Select a repository
      5. Click Select at the bottom of the screen
      6. Exit out of the window

      Actual Behavior

      Task `pulp_ansible.app.tasks.copy.copy_or_move_and_sign`kicks off after selecting a repository. When this task completes, the collection can be viewed in the selected repo. Going back to the approval-dashboard shows the collection still present in the `staging` repo as well. 

      Example: autohubtest2.collection_dep_a_psaqiytz:1.0.0 is in both `validated` and `staging`. 

      https://console.stage.redhat.com/ansible/automation-hub/repo/staging/autohubtest2/collection_dep_a_psaqiytz/?version=1.0.0

      https://console.stage.redhat.com/ansible/automation-hub/repo/validated/autohubtest2/collection_dep_a_psaqiytz/?version=1.0.0

      Expected Behavior

      After the `pulp_ansible.app.tasks.copy.copy_or_move_and_sign`task completes, the collection should only be present in the selected repo and removed from staging. 

              jtanner@redhat.com James Tanner
              alhart@redhat.com Alison Hart
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: