In T149012, we saw that deploying to wtp2017.codfw.wmnet failed ,
20:29:29 ['/usr/bin/scap', 'deploy-local', '-v', '--repo', 'parsoid/deploy', '-g', 'default4', 'promote', '--refresh-config'] on wtp2017.codfw.wmnet returned [1]:
Looking at the logs on deployment.eqiad.wmnet in /srv/deployment/parsoid/deploy/scap/log,
./scap-sync-2016-10-24-0001.log:{"name": "target.wtp2017.codfw.wmnet.checks", "created": 1477340969.825173, "args": [], "msecs": 825.1729011535645, "filename": "checks.py", "levelno": 30, "msg": "Check 'repool' failed: Pooling wtp2017.codfw.wmnet from service=parsoid...\nERROR:conftool:Error when trying to set/pooled=yes on service=parsoid,name=wtp2017.codfw.wmnet\nERROR:conftool:Failure writing to the kvstore: Backend error: Raft Internal Error : etcdserver: request timed out\n", "host": "wtp2017.codfw.wmnet", "lineno": 70, "exc_text": null, "funcName": "handle_failure", "relativeCreated": 35622.64394760132}
Not sure what to make of that. Is it transient? What should I do if I encounter something like that again? In this case, I just removed that target and redeployed, which doesn't seem great.
Can I try scap deploy -l wtp2017.codfw.wmnet now? (Assuming that does what I think it does.)
Sorry for the naiveté.