From nobody Tue Aug 12 17:58:36 2025 X-Original-To: virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4c1fPm6H8nz65C29 for ; Tue, 12 Aug 2025 17:58:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4c1fPm4T4jz41ld for ; Tue, 12 Aug 2025 17:58:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1755021516; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=mlmbj3Wlf/Xhv33DZSH5Og5HKK/ER+QXm6TSwORZFT4=; b=EvQ2RQWauvvh3lu13td7LkggEgxZ0EMMlqx53cSQcWAyA5JKyb/JeAL9+MZbdmyxFmoH0b vKMApWhVFmmpgGiEv6rrDQY5C7U/fOBkS9YJ6XEVQWuRkczm2I0j8n2OTOPHnArk/FL9LL ztk6eBg2LtsERIs8AXQNrZZ18HAutJKatUZ+7zIWinzEp0k8IC+IK4+18s5GZT/zxlTzMI FVUFF+THZmQwcwx/RyN/9BKCQnYxNZriA0cr0Cp37dCBGRjssoi2Cc3wSKF473vvai0Mnj 3OZ3OC48ipWFOU6EIGkk0hmEXFfzfWhONnVRsoD4d1XwePRkq1EhLBkFYlo/dw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1755021516; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=mlmbj3Wlf/Xhv33DZSH5Og5HKK/ER+QXm6TSwORZFT4=; b=OTOBYaCpgSv505eZm+tHJwxLIUxmkGXiyHodFs61j+lpaT9s36fTK3W/bsOuQkVPAdcRFU gIhafZV8qmaS/eek5vkfgOVIWRMnX10Pm8ArvLn1Fw782un1vDiIOTiOjtyImIi01floWi goylPBtU4JXpuX145odxzz58/OdsDLg3nKPEmVR8rTLLvQzfNkHVzxSdn/zOHfzh4AYLsB E5UBywdCP4pINTioqqEdcbNIB7+WR6ktt6+eUZWT6KURBeDm9/O+42C0QNmvyJTXgqEG20 G74qm6ChucctZE0g81KeRXjD6O1xz7lX5Fi/5b8gHF66Scx0dcumJ5ZFD8lzXA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1755021516; a=rsa-sha256; cv=none; b=Nhd8fexGvTSWcnyTtlW+xkeiNVbeU7zYB7hoWHFFLZeU6zDJFMZ17F/FDoipPMeb43Z0Tc d/lr9iCh5359dpoY3wMonA5jfqrYCdH75UhRaK610V2Mf/dpT1qJpPPbmQ4JNzcMVjiqnh p3gBYSkLBcl45vYTla2PGi84bWBllyT5O43V2XxO9eF+B6v1Lt8b/x1foT3mNiVMV3y3i1 UJjQoweRvO3iBMlE62oAihCE1jYS4Flh1zaHqEiWfoCsecAL++JeR69mZ4/I1u3lXSxSof 6WyPbIfXHccZ1y6PRuzDI2u1ye9wTXwU65sZhklRSPBUK/fTza/kyGWMQFMtQw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4c1fPm37xczpWc for ; Tue, 12 Aug 2025 17:58:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 57CHwauf008934 for ; Tue, 12 Aug 2025 17:58:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 57CHwawG008933 for virtualization@FreeBSD.org; Tue, 12 Aug 2025 17:58:36 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 288817] Recent FreeBSD 15.0-CURRENT images in GCP are broken with Cirrus CI Date: Tue, 12 Aug 2025 17:58:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 15.0-CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D288817 Mark Millard changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #1 from Mark Millard --- For main-* (beefy18, beefy17, ampere2), I expect that the timing of: libutil.so.9 =3D> not found (0) /lib/libutil.so.10 vs. also having (later): libssl.so.30 =3D> not found (0) libcrypto.so.30 =3D> not found (0) /lib/libcrypto.so.35 /usr/lib/libssl.so.35 at issue. Some port-package builders are running poudriere jail worlds with /lib/libutil.so.10 now and have even completed builds with such if I remember right. But none are yet running such worlds with: /lib/libcrypto.so.35 or /usr/lib/libssl.so.35 Notes about the timing of availability as stands: The main-* port-package build servers are: main-amd64: beefy18 main-i386: beefy17 (Unsure when i386 will having main built!) main-arm64: ampere2 main-armv7: ampere2 (yes: again) (I do not have details for distribution stage or servers.) These notes based on recent times with pkg 2.2.1 or pkg 2.2.2 in use on the builders in question. There is also the timing of the ports-tree snapshot involved. Some combinations will not match the staging for the above well. What is needed for main-* follow. Notes were originally typed early on 2025-Aug-12 UTC but are only intended to give ball park figures. The poudriere Jails need to have a 2025-Aug-12+ (UTC) or so Jail OSVERSION that is 1500059 (or later) The poudriere Jails needs to be using a ports tree from 2025-Aug-12+ (UTC) or so No existing build activity is that recent. main-amd64 on beefy18: 2025-Aug-26 or so Details . . . Jail OSVERSION is currently at: 1500056 It takes 250 Hrs to 270 Hrs or so to build an update in recent times. So about 10 to 11 Days. The existing build has about 100 Hrs to go (about 4 days). Then the jail osversion and ports tree can be updated. So 4 days + 10 days + ? days is: 14 days+ main-i386 on beefy17: 2025-Aug-26 or so Details . . . Jail OSVERSION is currently at: 1500056 It takes 245 Hrs to 260 Hrs or so to build an update in recent times. So also about 10 to 11 Days. The existing build has about 90 Hrs to go (about 4 days). Then the jail osversion and ports tree can be updated. So 4 days + 10 days + ? days is: 14 days+ ampere 2 cycles between building main-aarch64 and main-armv7 . So things are more complicated and sequential. main-arm64 on ampere2: 2025-Sep-07 or so main-armv7 on ampere2: 2025-Sep-23 or so Details . . . Jail OSVERSION is currently at: 1500052 main-armv7 is building currently. main-armv7 takes 390 Hrs to 420 Hrs to build. So about 16 days to 18 days. The existing build has about 230 Hrs to go (about 10 days). Then the jail osversion and ports tree can be updated. main-arm64 takes 390 Hrs to 420 Hrs to build. So about 16 days to 18 days. So 10 days + 16 days + ? days is: 26 days+ main-armv7 takes 390 Hrs to 420 Hrs to build. So about 16 days to 18 days. So 26 days + 16 days + ? days is: 42 days+ --=20 You are receiving this mail because: You are the assignee for the bug.=