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

The Last Job Status of the Project update can lead to the update job of the different project #14431

Open
6 of 11 tasks
elibogomolnyi opened this issue Sep 12, 2023 · 1 comment

Comments

@elibogomolnyi
Copy link

elibogomolnyi commented Sep 12, 2023

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 [email protected] instead.)

Bug Summary

Here is an example of a project in AWX
image
The Last Job Status leads to the last successful project update of the current project.

But when this status is changed to Running...
image

...the link starts leading to the latest project update job from the whole AWX system and not the running project update of this particular project.

This bug may be related to another bug:
#14430

AWX version

22.5

Select the relevant components

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

Installation method

kubernetes

Modifications

no

Ansible version

No response

Operating system

No response

Web browser

No response

Steps to reproduce

Check the link in the Running Last Job Status status of the Project

Expected results

The link leads to the latest running project of this particular project

Actual results

The link leads to the latest running project update in AWX

Additional information

No response

@fosterseth
Copy link
Member

was able to reproduce on latest

@mabashian added this to ui enhancement, hopefully that is good enough to track this bug

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

2 participants