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

Self-hosted agents ending up in wrong runner-group when './config.sh --replace --runnergroup abcd ' is used #3585

Open
srcinemo opened this issue Nov 20, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@srcinemo
Copy link

Describe the bug
New agent ends up in wrong runner group when instance is replaced

To Reproduce
Steps to reproduce the behavior:

  1. Setup new agent using ./config.sh --replace option. The generated runner name should exist already and this script replaces it
  2. The new agent is created in the old agent runner group and the --runnergroup is ignored

Expected behavior
The agent should have the same runner group as passed in --runner-group option

Runner Version and Platform

Version of your runner?
Current runner version: '2.317.0'

OS of the machine running the runner? OSX/Windows/Linux/... Linux (Ubuntu 22.04)

What's not working?

Agent is assigned the wrong runergroup

@srcinemo srcinemo added the bug Something isn't working label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant