3a0540dff0
The `api.sh` test currently always defaults to "<REGION>-a" zone when creating instance using the built image. The resources in a zone may get exhausted and the solution is to use a different zone. Currently even a CI job retry won't help with mitigation of such error during a CI run. Modify `api.sh` to pick random GCP zone for a given region when creating a compute instance. Use only GCP zones which are "UP". The `cloud-cleaner` relied on the behavior of `api.sh` to always choose the "<REGION>-a" zone. Guessing the chosen zone in `cloud-cleaner` is not viable, but thankfully the instance name is by default unique for the whole GCP project. Modify `cloud-cleaner` to iterate over all available zones in the used region and try to delete the specific instance in each of them. Make `ComputeZonesInRegion` method from the `internal/cloud/gcp` package exported and use it in `cloud-cleaner` for getting the list of available zones in a region. Signed-off-by: Tomas Hozza <thozza@redhat.com> |
||
|---|---|---|
| .. | ||
| cloud-cleaner | ||
| osbuild-auth-tests | ||
| osbuild-composer | ||
| osbuild-composer-cli-tests | ||
| osbuild-dnf-json-tests | ||
| osbuild-image-tests | ||
| osbuild-koji | ||
| osbuild-koji-tests | ||
| osbuild-pipeline | ||
| osbuild-store-dump | ||
| osbuild-upload-aws | ||
| osbuild-upload-azure | ||
| osbuild-upload-gcp | ||
| osbuild-worker | ||