Awx: AWX Jobs view failing on UI

Created on 21 Jun 2018  ยท  9Comments  ยท  Source: ansible/awx

ISSUE TYPE
  • Bug Report
COMPONENT NAME
  • API
  • UI
SUMMARY

Unable to fetch job details on AWX. Getting
ERROR! Invalid search term entered. GET returned: -1

ENVIRONMENT
  • AWX version: 1.0.6.16
  • AWX install method: docker on linux, docker for mac
  • Ansible version: 2.3.1.0, 2.4.0.0
  • Operating System: Linux, Mac
  • Web Browser: Chrome, Firefox
STEPS TO REPRODUCE

Launch any SCM job from UI and click on jobs. API call gets failed and error is shown on UI.

EXPECTED RESULTS

Jobs view should work

ACTUAL RESULTS

screen shot 2018-06-20 at 3 27 51 pm

ADDITONAL INFORMATION

Please find the screen recording.
jobs_issue.zip

api ui needs_info bug

Most helpful comment

Disable your AdBlocker on AWX. Had this issue for a while too, but it's always been because of uBlock. If you check on that failed request, you'll see that it errors out with ERR_BLOCKED_BY_CLIENT.

All 9 comments

I can confirm this, happens at least since 1.0.6.8 and is still present in 1.0.6.17. Happens only with project syncs.

In the API I can find the job output at /project_updates/:id/stdout so it's definitely being stored in the database, just that it's not accessible anymore from the UI.

Are there any console errors you can find on the web console?

@jaredevantabor Please find the screenshot. xhr calls are failing for playbook_on_stats event.
screen shot 2018-06-21 at 10 17 55 am

@jaredevantabor Any update on the issue ?

With a fresh, non-upgraded install of the latest devel container image I'm not seeing this bug:

project_sync

At any rate, that specific api query has been removed downstream - This will be resolved when those code changes reach devel.

@jakemcdermott I tried awx_web:latest container image. I'm still seeing the issue. Can you please suggest some fix?

I am also seeing the issue and just installed today.

Disable your AdBlocker on AWX. Had this issue for a while too, but it's always been because of uBlock. If you check on that failed request, you'll see that it errors out with ERR_BLOCKED_BY_CLIENT.

That solved the issue for me, thanks.

Was this page helpful?
0 / 5 - 0 ratings