df335525ab
Previously we were only checking that Apache can open TCP connections to determine if Gitea is up or down on a backend. This is insufficient because Gitea itself may be down while Apache is up. In this situation TCP connection to Apache will function, but if we make an HTTP request we should get back an error. To check if both Apache and Gitea are working properly we switch to using http checks instead. Then if Gitea is down Apache can return a 500 and the Gitea backend will be removed from the pool. Similarly if Apache is non functional the check will fail to connect via TCP. Note we don't verify ssl certs for simplicity as checking these in testing is not straightforward. We didn't have verification with the old tcp checks so this isn't a regression, but does represent something we could try and improve in the future. Change-Id: Id47a1f9028c7575e8fbbd10fabfc9730095cb541 |
||
|---|---|---|
| .. | ||
| group_vars | ||
| host_vars | ||
| gate-groups.yaml.j2 | ||