Closed Bug 1369164 Opened 7 years ago Closed 7 years ago

if reconfig fails, next reconfig will not run if no changes have been deployed

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P1)

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: kmoir, Unassigned)

Details

from this morning

2017-05-31 07:00:01 - INFO  - Checking whether we need to reconfig...
2017-05-31 07:00:03 - INFO  - buildbotcustom: production-0.8 tag is unchanged - rev: 8f2305bb6a3d59fc12d288a09371a1ad970ff2c4
2017-05-31 07:00:05 - INFO  - buildbot-configs: production tag has moved - old rev: 2fc76c8d744ce26adc91d7d03ede75fdff4ae074; new rev: 11615246242db50ff111011b6eaf63e6d267ee4c
3 files updated, 0 files merged, 0 files removed, 0 files unresolved
2017-05-31 07:00:08 - INFO  - tools: default tag is unchanged - rev: bd89aaf901f5b991cd1c4730d04fa3b27d4104b6
2017-05-31 07:00:08 - INFO  - --------------------------------------------------------------
2017-05-31 07:00:08 - INFO  -  Begin updating master_config.json
writing new master_config.json file to /builds/buildbot/tests1-windows/master/master_config.json
2017-05-31 07:00:08 - INFO  - Starting reconfig. - 1496239201
cd master && /builds/buildbot/tests1-windows/bin/buildbot checkconfig
Traceback (most recent call last):
  File "/builds/buildbot/tests1-windows/lib/python2.7/site-packages/buildbot-0.8.2_hg_8b87b4974e3c_production_0.8-py2.7.egg/buildbot/scripts/runner.py", line 1042, in doCheckConfig
    ConfigLoader(configFileName=configFileName)
  File "/builds/buildbot/tests1-windows/lib/python2.7/site-packages/buildbot-0.8.2_hg_8b87b4974e3c_production_0.8-py2.7.egg/buildbot/scripts/checkconfig.py", line 31, in __init__
    self.loadConfig(configFile, check_synchronously_only=True)
  File "/builds/buildbot/tests1-windows/lib/python2.7/site-packages/buildbot-0.8.2_hg_8b87b4974e3c_production_0.8-py2.7.egg/buildbot/master.py", line 652, in loadConfig
    exec f in localDict
  File "/builds/buildbot/tests1-windows/master/master.cfg", line 109, in <module>
    c['slaves'].append(BuildSlave(name, SlavePasswords[slave_platform], max_builds=1,
KeyError: 'win10_64_devedition'
make: *** [checkconfig] Error 1
2017-05-31 07:00:12 - ERROR - Checkconfig failed.
2017-05-31 07:00:12 - ERROR - Reconfig failed. - 1496239201
2017-05-31 07:00:12 - INFO  - Elapsed: 0h 0m 11s
2017-05-31 07:00:12 - INFO  - ==================================================
2017-05-31 08:00:01 - INFO  - Checking whether we need to reconfig...
2017-05-31 08:00:03 - INFO  - buildbotcustom: production-0.8 tag is unchanged - rev: 8f2305bb6a3d59fc12d288a09371a1ad970ff2c4
2017-05-31 08:00:05 - INFO  - buildbot-configs: production tag is unchanged - rev: 11615246242db50ff111011b6eaf63e6d267ee4c
2017-05-31 08:00:07 - INFO  - tools: default tag is unchanged - rev: bd89aaf901f5b991cd1c4730d04fa3b27d4104b6
2017-05-31 08:00:07 - INFO  - No reconfig required.
2017-05-31 08:00:07 - INFO  - Elapsed: 0h 0m 6s

Workaround was to force a reconfig
This sounds like something we should look into to fix. If not, we should downgrade to P5.
Priority: -- → P1
@aselagea: I wonder if we can close this bug as WONTFIX? We've had plenty of reconfigs ever since + devedition is now fully integrated within our automation. What say you?
Flags: needinfo?(aselagea)
Yeah, I don't expect this to be an issue in the remaining time buildbot is around, so let's mark it as WONTFIX.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(aselagea)
Resolution: --- → WONTFIX
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.