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

Clicking on a worker machine in a worker pool when upgrades available navigates to the wrong page #8666

Closed
shaunmarx opened this issue Mar 4, 2024 · 2 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving

Comments

@shaunmarx
Copy link

Severity

Not blocking, however workarounds are not great

Version

2024.1.6784

Latest Version

I could reproduce the problem in the latest build

What happened?

When expanding a worker pool, clicking on the worker machine will result in an empty page with a Resource not found or it doesn't exist in the current space error.

Reproduction

Ensure a you have a worker pool that includes a worker with an older version of tentacle i.e. requires upgrades. Expand the Worker pool and notice the Upgrade Available message for the worker. Click on the worker and notice the empty page with the error being presented.

Error and Stacktrace

Resource not found or it doesn't exist in the current space. Please contact your administrator for more information.

More Information

This issue only occurs when upgrades are available for worker machines, it does not affect deployment targets.

Workaround

Upgrade the tentacle version for the worker or manually change the link location in the url from /infrastructure/machines to /infrastructure/workers

@shaunmarx shaunmarx added the kind/bug This issue represents a verified problem we are committed to solving label Mar 4, 2024
@octoreleasebot
Copy link

octoreleasebot commented Mar 4, 2024

Release Note: Fixed an issue where clicking on a worker machine that requires a tentacle upgrade will navigate to the wrong page and display a not found error

@Octobob
Copy link
Member

Octobob commented May 16, 2024

🎉 The fix for this issue has been released in:

Release stream Release
2024.2 2024.2.1420
2024.3+ all releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

3 participants