Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launching a JT which no longer exists does not surface an error to the user #3290

Closed
unlikelyzero opened this issue Feb 22, 2019 · 3 comments

Comments

@unlikelyzero
Copy link

ISSUE TYPE
  • Bug Report
COMPONENT NAME
  • UI
SUMMARY

If a job is deleted and then another user on the system attempts to launch that job, the API returns the proper 404 error but that's not presented to the user. They just have an inert button press. This happens for all launch buttons on all job types.

ENVIRONMENT
  • AWX version: 3.0.0
STEPS TO REPRODUCE
  1. Create A JT on one sessions
  2. Prepare to launch! on another
  3. Delete the JT on session 1
  4. Launch JT on session 2
EXPECTED RESULTS

404 Error presented to user

ACTUAL RESULTS

Inert button press

@unlikelyzero unlikelyzero changed the title Launching a JT which no longer exists doesn't surface an error to the user Launching a JT which no longer exists does not surface an error to the user Feb 22, 2019
@AlexSCorey AlexSCorey assigned mabashian and unassigned AlexSCorey Feb 27, 2019
@AlexSCorey
Copy link
Member

This issue will be addressed by PR # #3174

@mabashian
Copy link
Member

The underlying cause of this issue and #3319 are the same which is why the fix for #3319 in #3174 will address this issue as well.

@unlikelyzero
Copy link
Author

Verified by deleting a JT on session 1 and attempting to relaunch on session 2 (which has a stale representation of available JTs)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants