iocage cannot not update jail past current version and cannot upgrade past 12.0

[itskando]

Posted at github iocage forum also:

iocage update/upgrade fail to reach latest versions · Issue #1227 · iocage/iocage

TrueNAS 12.0. iocage version 1.2 Background: There are 2 preexisting jails and 1 new test jail (syncthing — not yet setup). Issue: The preexisting jails were unable to iocage update <jail> past the...

github.com

TrueNAS 12.0.
iocage version 1.2

Background:
There are 2 preexisting jails and 1 new test jail (syncthing — not yet setup).

Issue:
The preexisting jails were unable to iocage update <jail> past their current version.
When they were 11.3-RELEASE, they only updated to 11.3-RELEASE.

The preexisting jails updated via iocage upgrade <jail> -r 12.0-RELEASE to 12.0.
They are now 12.0-RELEASE, but they only update to 12.0-RELEASE.

The preexisting jails are unable to iocage upgrade <jail> -r [12.0|12.1|12.2]-RELEASE past 12.0.
iocage upgrade <jail> -r 12.2-RELEASE, for example, updates to 12.0 (not 12.2).

New jails are able to be made in 12.2 without issue.

Expectation:
I was expecting to be able to update or manual upgrade to the 12.2 release.

Commands and Outputs:

Code:

root@Deetz:~ # iocage list
+-----+-----------+-------+--------------+---------------+
| JID |   NAME    | STATE |   RELEASE    |      IP4      |
+=====+===========+=======+==============+===============+
| 1   | media     | up    | 12.0-RELEASE | 192.168.86.10 |
+-----+-----------+-------+--------------+---------------+
| 2   | openVPN   | up    | 12.0-RELEASE | 192.168.86.8  |
+-----+-----------+-------+--------------+---------------+
| 3   | syncthing | up    | 12.2-RELEASE | DHCP          |
+-----+-----------+-------+--------------+---------------+



.



root@Deetz:~ # iocage update media
Snapshot: Lydia/iocage/jails/media@ioc_update_12.0-RELEASE-p13_2020-11-20_18-34-04 created.
Updating jail...

* Updating media to the latest patch level...
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 12.0-RELEASE from update4.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 12.0-RELEASE-p13.

WARNING: FreeBSD 12.0-RELEASE HAS PASSED ITS END-OF-LIFE DATE.
Any security issues discovered after Fri Feb 28 19:00:00 EST 2020
will not have been corrected.
No updates are available to install.
Run '/tmp/tmpq477w54n fetch' first.

release: 12.0-RELEASE-p13 -> 12.0-RELEASE-p13



.



root@Deetz:~ # iocage upgrade media -r 12.2-RELEASE
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 12.0-RELEASE from update4.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.

The following components of FreeBSD seem to be installed:
src/src world/base world/doc world/lib32

The following components of FreeBSD do not seem to be installed:
world/base-dbg world/lib32-dbg

Does this look reasonable (y/n)? n
Command: /tmp/tmpgtqfw_3e -b /mnt/Lydia/iocage/jails/media/root -d /mnt/Lydia/iocage/jails/media/root/var/db/freebsd-update/ -f /mnt/Lydia/iocage/jails/media/root/etc/freebsd-update.conf --not-running-from-cron --currently-running 12.0-RELEASE -r 12.2-RELEASE upgrade failed!
root@Deetz:~ #

 

[itskando]

Reformatted summary : j

 

[Jailer]

I fail to see what the issue is here. The iocage update command updates the patch level of the jail. If there is no newer patch level available then it doesn't update. Iocage upgrade upgrades the release. You stopped the upgrade by answering "n" and it stopped. Looks like to me it funstioned exactly as it should have.

https://iocage.readthedocs.io/en/latest/advanced-use.html#updating-jails

 

[itskando]

iocage list proves that 12.2 is available.
iocage upgrade only goes to 12.0.
iocage update -r 12.2 only goes to 12.0.

I stopped the later process because it immediately states 12.0 rather than 12.2. it's already won't and there is therefore no need to go further

 

[itskando]

In other words, if I can make a new jail in 12.2 and I can iocage fetch -U to 12.2, why can I not rev an existing jail to 12.2

 

[Alecmascot]

In other words, if I can make a new jail in 12.2 and I can iocage fetch -U to 12.2, why can I not rev an existing jail to 12.2

You stopped the upgrade process too soon.
You made an assumption that "Fetching metadata signature for 12.0-RELEASE " referred to the target version, whereas it relates to the version to be upgraded from.
The process works fine.

 

[itskando]

Oh.

Thank you.

(Before closing the issue; why doesn't update function? That one does go from 12.0 to 12.0..)

 

[Jailer]

No updates needed to update system to 12.0-RELEASE-p13.

It states why in the output you posted that I quoted above and stated in my previous post.

The iocage update command updates the patch level of the jail. If there is no newer patch level available then it doesn't update.

 

[itskando]

I just don't understand why if 12.2 is released,
that no newer patch level is available according to upgrade.
upgrade states this even after I performed a manual fetch of 12.2.

 

[intergalactic]

Greetings,

I am having very similar issue with the difference that various invocations of iocage make no difference. I have tried update/upgrade with and without -r flag and all in vain. Here is an output from the host:

Code:

root@nas[~]# freebsd-version
12.2-RELEASE-p3

root@nas[~]# iocage upgrade syncthing -r 12.2-RELEASE-p3
Snapshotting syncthing...
Snapshot already exists
Updating plugin INDEX...
Running upgrade...
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 5 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
        ca_root_nss: 3.61
        nginx: 1.18.0_47,2
        pcre: 8.44
        pkg: 1.16.3
        syncthing: 1.13.1

Number of packages to be removed: 5

The operation will free 90 MiB.
[syncthing] [1/5] Deinstalling nginx-1.18.0_47,2...
[syncthing] [1/5] Deinstalling nginx-1.18.0_47,2...
pkg: Failed to execute lua script: [string "-- args: etc/nginx/fastcgi_params-dist etc/ng..."]:12: attempt to call a nil value (field 'filecmp')
[syncthing] [1/5] Deinstalling nginx-1.18.0_47,2...
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
[syncthing] [1/5] Deleting files for nginx-1.18.0_47,2: .......... done
pkg: lua script failed
[syncthing] [2/5] Deinstalling ca_root_nss-3.61...
pkg: lua script failed
[syncthing] [2/5] Deinstalling ca_root_nss-3.61...
pkg: Failed to execute lua script: [string "-- args: etc/ssl/cert.pem.sample..."]:12: attempt to call a nil value (field 'filecmp')
pkg: lua script failed
pkg: lua script failed
[syncthing] [2/5] Deleting files for ca_root_nss-3.61: ....... done
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
[syncthing] [3/5] Deinstalling pcre-8.44...
[syncthing] [3/5] Deleting files for pcre-8.44: .......... done
pkg: lua script failed
[syncthing] [4/5] Deinstalling pkg-1.16.3...
pkg: lua script failed
[syncthing] [4/5] Deinstalling pkg-1.16.3...
pkg: Failed to execute lua script: [string "-- args: etc/pkg.conf.sample..."]:12: attempt to call a nil value (field 'filecmp')
[syncthing] [4/5] Deinstalling pkg-1.16.3...
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
[syncthing] [4/5] Deleting files for pkg-1.16.3: .......... done
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
pkg: lua script failed
[syncthing] [5/5] Deinstalling syncthing-1.13.1...
[syncthing] [5/5] Deleting files for syncthing-1.13.1: .......... done
pkg: lua script failed
==> You should manually remove the "syncthing" user.
pkg: lua script failed
==> You should manually remove the "syncthing" group
pkg: lua script failed
Snapshotting syncthing...
Updating plugin INDEX...
Updating plugin artifact...
Cloning git repository

Branch 12.2-RELEASE does not exist at https://github.com/freenas/iocage-plugin-syncthing.git!
Using "master" branch for plugin, this may not work with your RELEASE
Installing new pkgs...
Repo: iocage-plugins already exists, skipping!

Testing Host DNS response to pkg.FreeBSD.org
Testing syncthing's SRV response to pkg.FreeBSD.org
Testing syncthing's DNSSEC response to pkg.FreeBSD.org

Installing plugin packages:
  - syncthing...
  - ca_root_nss...
  - nginx...
Cloning git repository

Branch 12.2-RELEASE does not exist at https://github.com/freenas/iocage-plugin-syncthing.git!
Using "master" branch for plugin, this may not work with your RELEASE

syncthing successfully upgraded!

root@nas[~]# iocage list
+------+-----------+-------+--------------+------------+
| JID  |   NAME    | STATE |   RELEASE    |    IP4     |
+======+===========+=======+==============+============+
| None | syncthing | down  | 12.1-RELEASE | 172.16.0.2 |
+------+-----------+-------+--------------+------------+

Would appreciate an advice how to update said jail without re-creating everything from scratch.

Thank you.

 

[Inxsible]

I have the same issue. No matter which iocage update / upgrade command I use, I cannot get the jails to upgrade to 12.2. They keep staying on 12.1-RELEASE-pXX

For a long time they were on 12.1-RELEASE-p12 --- but today I upgraded and they upgraded to 12.1-RELEASE-p13 --- but no matter what they don't upgrade to 12.2-RELEASE-p3 even though my freebsd-version shows that version number.

 

[styno]

Maybe I am stating the obvious, but what is the output of the following command?

Code:

iocage list --release

If you don't have 12.2-RELEASE listed in there you have to fetch it first with

Code:

iocage fetch

 

[Inxsible]

Maybe I am stating the obvious, but what is the output of the following command?

Code:

iocage list --release

If you don't have 12.2-RELEASE listed in there you have to fetch it first with

Code:

iocage fetch

iocage upgrade should fetch the latest release if it's not available which was not happening for me. I tried it again today, and the

Code:

iocage upgrade emby

dowloaded the 12.2-RELEASE and updated it. However I tried upgrading my other transmission jail and it doesn't upgrade at all. I have used

Code:

iocage upgrade transmission

Code:

iocage upgrade -r 12.2-RELEASE transmission

But iocage list keeps showing me:

Code:

root@freenas:/mnt/tank/home/inxsible # iocage list
+-----+--------------+-------+--------------+-------------+
| JID |     NAME     | STATE |   RELEASE    |     IP4     |
+=====+==============+=======+==============+=============+
| 19  | emby         | up    | 12.2-RELEASE | 192.168.1.30 |
+-----+--------------+-------+--------------+-------------+
| 28  | transmission | up    | 12.1-RELEASE | 192.168.1.29 |
+-----+--------------+-------+--------------+-------------+
root@freenas:/mnt/tank/home/inxsible #

 

[Morris]

I'm having the same issue with Plex. About to move the server to a Windows VM

 

[talz13]

Same here. I just upgraded my 4 manually created jails:

• One from 11.3-RELEASE to 12.2-RELEASE
• Three from 12.1-RELEASE to 12.2-RELEASE

But my plexpass plugin jail will not update. I performed the same sequence, stopped the jail, ran the iocage upgrade plex-freenas -r 12.2-RELEASE, but still shows 12.1 after completion.

 

[ddaenen1]

Same here. I just upgraded my 4 manually created jails:

• One from 11.3-RELEASE to 12.2-RELEASE
• Three from 12.1-RELEASE to 12.2-RELEASE

But my plexpass plugin jail will not update. I performed the same sequence, stopped the jail, ran the iocage upgrade plex-freenas -r 12.2-RELEASE, but still shows 12.1 after completion.

Same here. Quite frustrating...

 

[emk2203]

I tried to update a transmission jail from 12.1 to 12.2 and failed as well. Watching the error messages, it looks like the release is not included for the plugin. The messages went to fast during the GUI upgrade, I could just make out something like "release not found on github'.