https://bugzilla.wikimedia.org/show_bug.cgi?id=70597
Bryan Davis <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Bryan Davis <[email protected]> --- This happens once in a while. It's some sort of deadlock in Jenkins itself. Here's how I generally try to resolve it: * Take deployment-bastion offline in Jenkins <https://integration.wikimedia.org/ci/computer/deployment-bastion.eqiad/markOffline> * Kill any jenkins jobs running on deployment-bastion via Jenkins UI * Kill all pending jobs in the Jenkins queue that are "waiting on executors" * Disconnect deployment-bastion <https://integration.wikimedia.org/ci/computer/deployment-bastion.eqiad/disconnect> * Bring deployment-bastion back online (button labeled "Bring this node back online") * Launch slave agent (there's a button that says this) * Check agent log to see that it connected <https://integration.wikimedia.org/ci/computer/deployment-bastion.eqiad/log> Sometimes you have to do this whole dance twice before Jenkins realizes that the there are a bunch of executors that it can use. This deadlock seems to happen more often than not following or during a database update that is taking a while to complete. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
