Matthew Booth
Matthew Booth
> Moving it to cloudbuild is not an issue as it mainly relies on the Makefile and Docker to run. It's just less community friendly as one can easily browse...
For reference, here's the logs of one of our nightly image builds: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/cluster-api-provider-openstack-push-images-nightly/1635189053307490304 Incidentally, that job seems pointless. We should probably kill it.
Example of automatic uploading of artifacts from a cloudbuild job: https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/b2b2a3ec4565c146b57ce1c9634469ddfd9a078c/Makefile#L405-L406
Could it just be timeouts? It's probably fine to run them sequentially as separate cloudbuild steps, I guess.
Thanks. Does it succeed eventually when it retries?
We're definitely leaking floating IPs every time this fails, and in a way which looks like it might prevent the cluster ever coming up. I think that's the most serious...
> could a step below this be to maybe build out the Makefile's needed to make this happen so users can easily build things out.. and _then_ this could be...
We need to robustify this entire method against incremental failures. Unfortunately I don't have time to work on this myself right now, but if you are able to work on...
/remove-lifecycle stale
Is there any chance this was fixed by https://github.com/kubernetes-sigs/cluster-api-provider-openstack/pull/1829?