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

Ansible Automation Platform 2.5 changed API

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Integration
    • None
    • Incidents & Support
    • False
    • Hide

      None

      Show
      None
    • False
    • None

       Description of problem:

      On Ansible Automation Platform 2.5, there is new Unified UI which should be also used as API endpoint for Ansible Automation Platform. When user try to connect ACM with AAP2.5 with Unified UI (Gateway) URL then it's throwing 404 errors.

       

      As workaround, customer used:

      Then I created a Personal Access Token on controller API and gave the controller URL on ACM, this scenario works for me

      Version-Release number of selected component (if applicable):

      N/A

      How reproducible:

      • Install ACM
      • Install AAP 2.5
      • Try to connect ACM with AAP2.5

      Steps to Reproduce:

      1. Install ACM
      2. Install AAP 2.5
      3. Try to connect ACM with AAP2.5

      Actual results:

      When user define Unified UI address (Gateway), then it's using old api and user get 404 errors:

       

      2024-10-11 12:15:49,809 WARNING   django.request Not Found: /api/v2/job_templates/
      [pid: 47|app: -|req: -/-] 127.0.0.1 (-) {52 vars in 2197 bytes} [Fri Oct 11 12:15:49 2024] GET /api/v2/job_templates/ => generated 179 bytes in 1 msecs (HTTP/1.1 404) 7 headers in 228 bytes (1 switches on core 0) x-request-id: 11abb1ef-a3de-4446-8ce1-4a24c1c35df3
      127.0.0.1 - - [11/Oct/2024:12:15:49 +0000] "GET /api/v2/job_templates/ HTTP/1.1" 404 179 (0.002) "-" "-" "172.27.48.73,100.114.0.2" request-id: "11abb1ef-a3de-4446-8ce1-4a24c1c35df3"
      2024-10-11 12:15:49,810 WARNING   django.request Not Found: /api/v2/inventories/
      2024-10-11 12:15:49,810 WARNING   django.request Not Found: /api/v2/inventories/
      127.0.0.1 - - [11/Oct/2024:12:15:49 +0000] "GET /api/v2/inventories/ HTTP/1.1" 404 179 (0.002) "-" "-" "100.114.0.8,100.114.0.2" request-id: "86b1da28-89fb-425a-8eb1-c1f9dccd661e"
      [pid: 44|app: -|req: -/-] 127.0.0.1 (-) {52 vars in 2189 bytes} [Fri Oct 11 12:15:49 2024] GET /api/v2/inventories/ => generated 179 bytes in 1 msecs (HTTP/1.1 404) 7 headers in 228 bytes (1 switches on core 0) x-request-id: 86b1da28-89fb-425a-8eb1-c1f9dccd661e 

       

       

      Expected results:

      It should be able to connect correctly.

      Additional info:

      I assume there should be some ways how to connect 2.4 and older versions and then 2.5 version.

              jpacker@redhat.com Joshua Packer
              rhn-support-jskacel Jindrich Skacel (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: