mJh78B
Dabbler
- Joined
- Apr 2, 2022
- Messages
- 20
I have two jails I created manually using the web GUI. They're currently sitting at 12.3-RELEASE. I just upgraded to the newest TrueNAS-13.0-U3.1 release from version 12, so I wanted to upgrade the jails as well. As far as I can tell, there are two main commands required to achieve this:
Regardless it appears to have downloaded something into
The only other reference I found to this "Upgrade failed, nothing to install after fetch!" error was in the FreeBSD bug tracker and this post, but they aren't getting the "usage: ..." part and that doesn't seem to be the root problem here. I'm not sure where to go from here since it seems like the
iocage fetch and iocage upgrade. When I try to run iocage fetch, it downloaded some archives the first time I ran it then decompresses what it downloaded, but then fails, apparently trying to run what I presume is freebsd-update (based on the usage printed) with incorrect arguments:Code:
root@truenas[~]# iocage fetch
[0] 12.3-RELEASE
[1] 12.4-RELEASE
[2] 13.0-RELEASE
[3] 13.1-RELEASE
Type the number of the desired RELEASE
Press [Enter] to fetch the default selection: (13.1-RELEASE)
Type EXIT to quit:
Fetching: 13.1-RELEASE
Extracting: base.txz...
Extracting: lib32.txz...
Extracting: src.txz...
* Updating 13.1-RELEASE to the latest patch level...
usage: tmpi_ru6kbm [options] command ... [path]
Options:
-b basedir -- Operate on a system mounted at basedir
(default: /)
-d workdir -- Store working files in workdir
(default: /var/db/freebsd-update/)
-f conffile -- Read configuration options from conffile
(default: /etc/freebsd-update.conf)
-F -- Force a fetch operation to proceed in the
case of an unfinished upgrade
-k KEY -- Trust an RSA key with SHA256 hash of KEY
-r release -- Target for upgrade (e.g., 11.1-RELEASE)
-s server -- Server from which to fetch updates
(default: update.FreeBSD.org)
-t address -- Mail output of cron command, if any, to address
(default: root)
--not-running-from-cron
-- Run without a tty, for use by automated tools
--currently-running release
-- Update as if currently running this release
Commands:
fetch -- Fetch updates from server
cron -- Sleep rand(3600) seconds, fetch updates, and send an
email if updates were found
upgrade -- Fetch upgrades to FreeBSD version specified via -r option
updatesready -- Check if there are fetched updates ready to install
install -- Install downloaded updates or upgrades
rollback -- Uninstall most recently installed updates
IDS -- Compare the system against an index of "known good" files
showconfig -- Show configuration
usage: tmpi_ru6kbm [options] command ... [path]
Options:
-b basedir -- Operate on a system mounted at basedir
(default: /)
-d workdir -- Store working files in workdir
(default: /var/db/freebsd-update/)
-f conffile -- Read configuration options from conffile
(default: /etc/freebsd-update.conf)
-F -- Force a fetch operation to proceed in the
case of an unfinished upgrade
-k KEY -- Trust an RSA key with SHA256 hash of KEY
-r release -- Target for upgrade (e.g., 11.1-RELEASE)
-s server -- Server from which to fetch updates
(default: update.FreeBSD.org)
-t address -- Mail output of cron command, if any, to address
(default: root)
--not-running-from-cron
-- Run without a tty, for use by automated tools
--currently-running release
-- Update as if currently running this release
Commands:
fetch -- Fetch updates from server
cron -- Sleep rand(3600) seconds, fetch updates, and send an
email if updates were found
upgrade -- Fetch upgrades to FreeBSD version specified via -r option
updatesready -- Check if there are fetched updates ready to install
install -- Install downloaded updates or upgrades
rollback -- Uninstall most recently installed updates
IDS -- Compare the system against an index of "known good" files
showconfig -- Show configuration
Regardless it appears to have downloaded something into
iocage/download and iocage/releases. If I try to upgrade my jails, it again appears to try to run freebsd-update with invalid syntax and fails. The jail is changed to "up" state but otherwise nothing changes.Code:
root@truenas[~]# iocage upgrade -r 13.1-RELEASE OpenVPN
usage: tmpl9bndxps [options] command ...
Options:
-b basedir -- Operate on a system mounted at basedir
(default: /)
-d workdir -- Store working files in workdir
(default: /var/db/freebsd-update/)
-f conffile -- Read configuration options from conffile
(default: /etc/freebsd-update.conf)
-F -- Force a fetch operation to proceed in the
case of an unfinished upgrade
-j jail -- Operate on the given jail specified by jid or name
-k KEY -- Trust an RSA key with SHA256 hash of KEY
-r release -- Target for upgrade (e.g., 11.1-RELEASE)
-s server -- Server from which to fetch updates
(default: update.FreeBSD.org)
-t address -- Mail output of cron command, if any, to address
(default: root)
--not-running-from-cron
-- Run without a tty, for use by automated tools
--currently-running release
-- Update as if currently running this release
Commands:
fetch -- Fetch updates from server
cron -- Sleep rand(3600) seconds, fetch updates, and send an
email if updates were found
upgrade -- Fetch upgrades to FreeBSD version specified via -r option
updatesready -- Check if there are fetched updates ready to install
install -- Install downloaded updates or upgrades
rollback -- Uninstall most recently installed updates
IDS -- Compare the system against an index of "known good" files
showconfig -- Show configuration
Upgrade failed, nothing to install after fetch!
The only other reference I found to this "Upgrade failed, nothing to install after fetch!" error was in the FreeBSD bug tracker and this post, but they aren't getting the "usage: ..." part and that doesn't seem to be the root problem here. I'm not sure where to go from here since it seems like the
iocage command itself is broken due to a change in freebsd-update, even though iocage is the latest released version (1.2).
