It is reported that Cirrus-CI cannot provision 11.3-RELEASE instance on GCE.
From the boot log of 11.3-RELEASE on GCE provided by kibab@:
pkg_resources.DistributionNotFound: The 'boto' distribution was not found and is required by google-compute-engine
Shows that Python module boto is not installed and cause GCE agent can not execute correctly.
From sbz@ (and edited by me):
After looking at the ports source, ports commit r501581 removed py-boto from RUN_DEPENDS and added back in r502800.
But tags/RELEASE_11_3_0 only contains r501581:
I suggest we build a new 11.3-RELEASE image with correct dependency and upload to GCE. It would be best to keep the same name of `freebsd-11-3-release-amd64` for not increasing the complexity of the configuration of the downstream users.
Thanks for kibab@ and sbz@ test and analyze the problem.
Unfortunatley, we cannot just "go and re-roll a new 11.3-RELEASE for GCE", as there are third-party validations that need to be run, and changing the version of the port on the image changes reproducibility.
As the validation for the GCE marketplace did succeed (otherwise it would not be in the marketplace), it is adviced to either upgrade to 12.0 or use the 11.3-STABLE snapshots.
Reopening, because the issue is not solved. The current image does not work so even if we can't re-spin it we need to address it in some way.
The failure can be reproduced via the GCP web UI. Create a new FreeBSD 11.3 instance, then click the connect by SSH button.
> Transferring SSH keys to the VM.
for quite some time, three retries, and eventually it times out.
Downstream bug that's a result of the broken image: https://github.com/cirruslabs/cirrus-ci-docs/issues/359
A commit references this bug:
Date: Fri Dec 6 21:20:32 UTC 2019
New revision: 355463
Document the 11.3-RELEASE images in GCE do not work, and provide
information regarding alternative solutions.
PR: 242303 (related)
Sponsored by: Rubicon Communications, LLC (netgate.com)
Are there so many changes between 11.3-RELEASE and whatever the first 11-stable snapshot that works? Maybe we are solving the problem that can be workarounded by using 11-stable? To date, we know about Cirrus-CI problem, and that is it. Most users will be probably happier with 12-RELEASE anyway.
My suggestion will be:
1) Delete 11.3-RELEASE from GCP entirely;
2) Direct Cirrus to use 11-stable for their setup;
3) Acknowledge that 11.3-RELEASE is not available on GCP. An errata notice (already committed) should be enough.
11.3 is EoL'd.