Invalid search term. 404 error. When trying to view second page of Approval drawer

[pjeanmonod]

ISSUE TYPE

• Bug Report

SUMMARY

404 invalid search when trying to view second page of notification drawer.

ENVIRONMENT

• AWX version: 11.0.0
• AWX install method: docker on linux
• Ansible version: 2.9.5
• Operating System: Linux
• Web Browser: Chrome

STEPS TO REPRODUCE

Go to second page of Approval notification drawer, get 404 error.

EXPECTED RESULTS

the second page of results.

ACTUAL RESULTS

Invalid search term entered. GET returned: 404 Invalid page.

ADDITIONAL INFORMATION

[pjeanmonod]

[pjeanmonod]

Bug is still unresolved, Closed in error.

[stefanmcshane]

Getting a similar error for notifications, that I assume is related. Means we cannot see anything past the first 5 jobs that require approval, which is a bit of a show stopper for production use.

• AWX Version 11.0.0

On opening the notifications drawer, the following is executed:
GET /api/v2/workflow_approvals/?page=1&page_size=5&order_by=created&status=pending

On using the pagination buttons, whether it is a number, or an arrow, the following is executed:
GET /v2/unified_job_templates/?page=2&page_size=5&order_by=created&status=pending

I'm not a frontend developer, but think this could be related to:

awx/awx/ui/client/lib/components/approvalsDrawer/approvalsDrawer.partial.html

Line 83 in a34a63e

base-path="unified_job_templates"

[unlikelyzero]

Notification Tray Tests:

• Verify that WFJT Approval details are accurate
• Verify that WFJT Link navigates user to correct JT
• User can click Approve button to approve a WFJT
• User can click Deny button to deny a WFJT.
• User can sort Approvals by Created Date
• User can Use Pagination controls to find the 21st Approval WFJT and approve

[chbmckeown]

Having the same issue, to confirm was this issue identified and fixed by update?
Unsure from labels/comments...
Thanks

[pjeanmonod]

The issue still persists and seems to be common... Has a fix been identified?

[pjeanmonod]

For anyone who finds themselves on this thread with the same issue, it has now been fixed in 11.2 as shown below:

commit b1b6af4
Author: John Mitchell [email protected]
Date: Fri Apr 24 15:31:20 2020 -0400

make sure right endpoint is getting called for notification paginationl