Closed Bug 996732 Opened 8 years ago Closed 8 years ago
tons of unauthorized slaves on panda masters
Probably fallout from me making adjustments to the slave lists. So far I've found: panda-0074/twistd.log:2013-08-12 13:49:03-0700 [Broker,client] unauthorized login; check slave name and password panda-0884/twistd.log:2014-04-15 10:47:34-0700 [Broker,client] unauthorized login; check slave name and password
also affected: panda-0033 These all seem to be in a different state: panda-0033 is in the production slave list in buildbot-configs, in the "tests-panda" pool in slavealloc, but is marked as disabled. panda-0074 is in the production slave list in buildbot-configs, but is a dev slave in slavealloc and also disabled panda-0884 is NOT in the production slave list in buildbot-configs, but is in the "tests-panda" pool in slavealloc and enabled.
OK, 0033 and 0074 were red herrings. But 0884 (as well as 0883 and 0882) are all marked as staging in buildbot but production in slavealloc. I've adjusted slavealloc to make these pandas staging again, after consulting with kmoir and callek. Leaving this open to confirm this fixes the issue.
0882 through 0884 were the only ones causing issues.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.