Skip to content
This repository has been archived by the owner on Apr 5, 2023. It is now read-only.

Bug in legacy agent termination #22

Open
drewinglis opened this issue Jan 31, 2020 · 0 comments
Open

Bug in legacy agent termination #22

drewinglis opened this issue Jan 31, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@drewinglis
Copy link
Contributor

Legacy agent termination doesn't seem to be working as intended. I didn't spend much time trying to debug why, so that remains TODO.

Retrieved on 2020/1/30:

aurora-cluster/gocd/test/build-agent-0
{:state :draining, :events [{:time #object[java.time.Instant 0x56840c6b "2020-01-09T20:24:29.024791Z"], :state :legacy, :message "Detected legacy agent in GoCD server"} {:time #object[java.time.Instant 0x2301ecba "2020-01-09T20:24:38.677649Z"], :state :draining, :message "Agent disabled in GoCD"}]}
state: draininglast-active:environment: ???resources:Event History2020-01-09T20:24:29.024791Z legacy Detected legacy agent in GoCD server2020-01-09T20:24:38.677649Z draining Agent disabled in GoCD

Screen Shot 2020-01-31 at 12 40 29 PM

@drewinglis drewinglis added the bug Something isn't working label Jan 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant