Failed to export assets Not Found (404) received

[ansiblejunky]

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that AWX is open source software provided for free and that I might not receive a timely response.
• I am NOT reporting a (potential) security vulnerability. (These should be emailed to security@ansible.com instead.)

Bug Summary

I'm running the following playbook to export objects from AAP 2.5.x single-node container installation. However, the playbook fails with an error. I'm using latest version of the Ansible Collections.

PLAY [Export objects from Ansible Platform Environment (using API)] ************************************************************************************************************************

TASK [Export assets] ***********************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {
    "changed": false,
    "msg": "Failed to export assets Not Found (404) received - {}"
}

PLAY RECAP *********************************************************************************************************************************************************************************
localhost                  : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

AWX version

awxkit-24.6.1

Select the relevant components

• UI
• UI (tech preview)
• API
• Docs
• Collection
• CLI
• Other

Installation method

N/A

Modifications

no

Ansible version

2.18.5

Operating system

MacOS

Web browser

No response

Steps to reproduce

Run the following playbook to perform the export:

---
- name: Export objects from Ansible Platform Environment (using API)
  hosts: localhost
  connection: local
  gather_facts: false

  tasks:

    - name: Export assets
      awx.awx.export:
        controller_host: "{{ aap_hostname }}"
        controller_username: "{{ aap_username }}"
        controller_password: "{{ aap_password }}"
        validate_certs: "{{ aap_validate_certs | default(false) }}"
        all: true
      register: results

    - name: Display exported information
      ansible.builtin.debug:
        var: results

Expected results

Objects exported from system

Actual results

Nothing exported, and error occurs

Additional information

No response

[ansiblejunky]

It appears the issue is the export code assumes the api endpoint for controller. This has changed with AAP 2.5 with the inclusion of Gateway. So the new endpoint is now:

The traceback is the following that shows the export.py going to the module_utils/awxkit.py function get_api_v2_object() which assumes the api endpoint for controller.

The full traceback is:
  File "/var/folders/s5/m2xyqvzj6_zbzjbt_dr87qr40000gn/T/ansible_ansible.controller.export_payload_t19lmy2y/ansible_ansible.controller.export_payload.zip/ansible_collections/ansible/controller/plugins/modules/export.py", line 184, in main
  File "/var/folders/s5/m2xyqvzj6_zbzjbt_dr87qr40000gn/T/ansible_ansible.controller.export_payload_t19lmy2y/ansible_ansible.controller.export_payload.zip/ansible_collections/ansible/controller/plugins/module_utils/awxkit.py", line 49, in get_api_v2_object
    v2_index = get_registered_page('/api/v2/')(self.connection).get()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/jwadleig/.pyenv/versions/dev/lib/python3.11/site-packages/awxkit/api/pages/page.py", line 254, in get
    page = self.page_identity(r)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/Users/jwadleig/.pyenv/versions/dev/lib/python3.11/site-packages/awxkit/api/pages/page.py", line 199, in page_identity
    raise exception(exc_str, data)

Here's the function

    def get_api_v2_object(self):
        if not self.apiV2Ref:
            if not self.authenticated:
                self.authenticate()
            v2_index = get_registered_page('/api/v2/')(self.connection).get()
            self.api_ref = ApiV2(connection=self.connection, **{'json': v2_index})
        return self.api_ref

The new endpoint is /api/controller/v2/.