-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix worker's name #3745
base: development
Are you sure you want to change the base?
Fix worker's name #3745
Conversation
cpd from #3685 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@amiraabouhadid it works fine with me, please try again and ensure you have the latest code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Screencast.from.2024-12-29.21-21-14.webm
the branch is updated with the remote one, i treid every thing to make sure that I'm on the correct branch, i notice that the branch name is similar to the old one maybe this is the problem
@0oM4R @amiraabouhadid I got it now, you guys are trying it on Caprover and it is fixed on k8s only, now it is fixed on Caprover too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@0oM4R fixed now |
its not enough the selected node is the same, which may lead to a resource error. |
Description
Rename worker after successful deployment
Changes
Related Issues
Tested Scenarios
Deploy a worker on any orchestrator instance. Don't close the dialog; instead, switch to the deploy tab and deploy another worker.
Checklist