Bug 291354 - GCE has an out-of-date-image for image_family: freebsd-15-0
Summary: GCE has an out-of-date-image for image_family: freebsd-15-0
Status: In Progress
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 15.0-STABLE
Hardware: Any Any
: --- Affects Many People
Assignee: Xin LI
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-02 15:29 UTC by Alan Somers
Modified: 2025-12-02 17:44 UTC (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Somers freebsd_committer freebsd_triage 2025-12-02 15:29:06 UTC 
The newly release freebsd-15-0-release-amd64-ufs GCE image works great.  However the freebsd-15-0 image_family isn't using it.  Instead, it's using an out-of-date freebsd-15-0-beta5-amd64-ufs .  And that image fails with Cirrus CI.  Can we please update the image_family?

> gcloud compute images describe-from-family freebsd-15-0 --project freebsd-org-cloud-dev
archiveSizeBytes: '1268910656'
creationTimestamp: '2025-11-07T07:52:57.801-08:00'
diskSizeGb: '22'
enableConfidentialCompute: false
family: freebsd-15-0
guestOsFeatures:
- type: GVNIC
- type: UEFI_COMPATIBLE
id: '5641347432213359414'
kind: compute#image
labelFingerprint: 42WmSpB8rSM=
licenseCodes:
- '5463491087573782631'
licenses:
- https://www.googleapis.com/compute/v1/projects/freebsd-org-cloud-dev/global/licenses/freebsd
name: freebsd-15-0-beta5-amd64-ufs
rawDisk:
  containerType: TAR
  source: ''
selfLink: https://www.googleapis.com/compute/v1/projects/freebsd-org-cloud-dev/global/images/freebsd-15-0-beta5-amd64-ufs
sourceType: RAW
status: READY
storageLocations:
- us
Comment 1 Colin Percival freebsd_committer freebsd_triage 2025-12-02 16:35:00 UTC 
Starting with (I think) RC1 we have the architecture and filesystem as part of the image family, e.g. freebsd-15-0-amd64-ufs.  Google pointed out that having the "latest" image randomly change architecture and filesystem depending on which upload won the race wasn't the best user experience.

The image family "freebsd-15-0" should not be used any more.
Comment 2 Alan Somers freebsd_committer freebsd_triage 2025-12-02 16:36:55 UTC 
(In reply to Colin Percival from comment #1)
Is there any way to list all registered image families in the project?
Comment 3 Colin Percival freebsd_committer freebsd_triage 2025-12-02 16:42:48 UTC 
Good question.  I have no idea; I don't use GCE myself.
Comment 4 Xin LI freebsd_committer freebsd_triage 2025-12-02 17:13:00 UTC 
(In reply to Alan Somers from comment #2)
I think that would be something like:

```
gcloud compute images list --project freebsd-org-cloud-dev --no-standard-images  --format="value(family)" | sort -u
```

but I'm not sure if there is a better way (e.g. querying families only).
Comment 5 Alexander Ziaee freebsd_committer freebsd_triage 2025-12-02 17:25:00 UTC 
We should mark the one we aren't using anymore accordingly.
Comment 6 Xin LI freebsd_committer freebsd_triage 2025-12-02 17:27:18 UTC 
(In reply to Alexander Ziaee from comment #5)
Yeah, I'm working on this now...
Comment 7 Alan Somers freebsd_committer freebsd_triage 2025-12-02 17:38:01 UTC 
Ok, I think the bottom line is that:
* We should specify an exact image if we want a release
* We should use image_family if we want a snapshot of the main branch or a stable branch
* If we want a single specification that will gracefully upgrade itself from 15.0 to 15.1 to 15.2, etc, then we are SOL.