Bootstrap v24.1 failing on Azure FreeBSD 13.2 VM

[ggriff]

I have tried multiple times to bootstrap an Azure FreeBSD v13.2 VM with no success. I have done this with v23.7 so am not a NOOB but have no clue why this is failing.

Code: [Select]

sudo sh ./opnsense-bootstrap.sh.in -r 24.1This utility will attempt to turn this installation into the latest
OPNsense 24.1 release.  All packages will be deleted, the base
system and kernel will be replaced, and if all went well the system
will automatically reboot.

Proceed with this action? [y/N]: y
fetch: https://github.com/opnsense/core/archive/stable/24.1.tar.gz: size of remote file is not known
/tmp/opnsense-bootstrap/core.tar.gz                   7650 kB 9543 kBps    01s
pkg: 17 packages installed
bash-5.2.15: already unlocked

previously it stopped at:
azure-agent-2.8.0.11: already unlocked
so I uninstalled the package but now it stops at the bash package so seems to just be going down the list.

Anyone have an idea why this is not working?

[Patrick M. Hausen]

FreeBSD 13.2 is EOL - you probably (I have not yet tried) need to start with 13.3 to be able to install packages?

[ggriff]

@Patrick thanks for the fast response but I'm still getting the same behaviour with FreeBSD 13.3

Code: [Select]

sudo sh ./opnsense-bootstrap.sh.in -r 23.7
sudo sh ./opnsense-bootstrap.sh.in -r 24.1
both result in:
Proceed with this action? [y/N]: y
fetch: https://github.com/opnsense/core/archive/stable/24.1.tar.gz: size of remote file is not known
/tmp/opnsense-bootstrap/core.tar.gz                   7650 kB 9600 kBps    01s
pkg: 18 packages installed
azure-agent-2.8.0.11: already unlocked
$

[Patrick M. Hausen]

Sorry, I cannot reproduce any problem, even with FreeBSD 13.2.

I do not use Azure but my own Vagrant based environment. [1] I have no idea what might be different in Microsoft's cloud.

Kind regards,
Patrick

[1] https://github.com/punktDe/vagrant-opnsense

[ggriff]

Hi Patrick,

Thanks for your response, I got the same issue on a local FreeBSD v13.3 image so ended up using the OPNSense ISO as I was tired of struggling with the bootstrap method.

[franco]

Actually this is caused by a regression in pkg-unlock tool, for details and workaround see https://github.com/opnsense/update/issues/93#issuecomment-2242714677


Cheers,
Franco