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

User is redirected to 404 page not found when clicking a collection version in the approval dashboard

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Normal Normal
    • None
    • cloud-2022-04-12
    • None
    • None

      https://console.stage.redhat.com/beta/ansible/automation-hub/approval-dashboard#workloads=Ansible+Automation+Platform&SIDs=&tags=

      clicking the version tag of a collection in the approval dashboard leads to a 404 error message page. Check screenshots for details.

            [AAH-1473] User is redirected to 404 page not found when clicking a collection version in the approval dashboard

            The PR https://github.com/ansible/galaxy_ng/pull/1169 caused this problem but it is already reverted, so the Issue is obsolete.

            Milan Pospisil added a comment - The PR https://github.com/ansible/galaxy_ng/pull/1169 caused this problem but it is already reverted, so the Issue is obsolete.

            Introduced in https://github.com/ansible/galaxy_ng/pull/1169, the error is:

            'CollectionVersion' object has no attribute 'deprecated' 

            Andrew Crosby (Inactive) added a comment - Introduced in https://github.com/ansible/galaxy_ng/pull/1169 , the error is: 'CollectionVersion' object has no attribute 'deprecated'

            Initial analysis: 

            Andrew Crosby (Inactive) added a comment - Initial analysis:  The _ui collections-detail viewset gives a 500 when using query parameter for version https://console.stage.redhat.com/api/automation-hub/_ui/v1/repo/staging/autohubtest2/collection_dep_a_gezypilb/?version=1.0.0   Reproduced in stage, currently b3f716a2e526084f6430e86fd722570aabcb247a, and dev environment. This is ok in production c.rh.c.

              mipospis@redhat.com Milan Pospisil
              ctorrens@redhat.com Christian Torrens (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: