Patrik Lundin
4b8b8887f6
In order to handle upgrades of the fleetlock server when running only one server we need to handle connection errors like connection refused or timed out errors gracefully. Because there are several different ways the connection can fail and it is hard to keep track of them all, just catch everything. We then also need special handling of our own timeout execption so we are not accidentally stuck retrying forever. Also fix so we actually use the request_timeout arg for individual HTTP requests instead of the global timeout. While here run isort to keep imports tidy. |
||
|---|---|---|
| default | ||
| docs | ||
| fabfile | ||
| global | ||
| scripts | ||
| .gitignore | ||
| addhost | ||
| apt | ||
| bump-tag | ||
| cosmos-rules.yaml | ||
| cosmos.conf | ||
| edit-secrets | ||
| host-puppet-conf-test | ||
| iaas-enable-root.sh | ||
| iaas-setup.sh | ||
| Makefile | ||
| prepare-iaas-debian | ||
| prepare-iaas-ubuntu | ||
| README | ||
The system documentation is in the docs directory of the multiverse repository.