Is 22.02 still coming out today?

[xenu]

After first upgrade (without problems) now I have a new upgrade:
TrueNAS-22.02.0 -> TrueNAS-22.02.RELEASE
Is it normal?

Best Regards,
Antonio

Same here. I assume just a version check issue.

But that aside everything appears to be working.
Rebooted from nightly to my RC boot environment and updated to release from there.
Thank you iXsystems.

 

[truecharts]

Please be aware that after a reboot it might take up to 30 minutes for the Kubernetes based Apps to start again.
Also, don't use docker-ps commands. It's not the right tool to query Kubernetes based apps. use:
k3s kubectl get pods -A

 

[gsrcrxsi]

so no option to fresh install yet? prefer to not install RC then upgrade. rather just do a fresh install of release from scratch.

 

[pabloalcantara]

For those who have problems with the APPs after the upgrade, just restore the backup you have done before, and the apps is restored.
Doesn´t need to roolback to RC2

 

[snave]

I upgraded from the last RC and have the TrueNAS-22.02.0 -> TrueNAS-22.02.RELEASE thing.

Also, system rebooted into the release with ssh disabled, which was odd.

Everything else good.

 

[nickspacemonkey]

Also, system rebooted into the release with ssh disabled, which was odd.

Same here! Upgraded from RC2 and everything was smooth. I had to reinstall my Fusion-io drivers, but I'm not really supposed to be installing drivers anyway, so all good.

 

[gsrcrxsi]

so no option to fresh install yet? prefer to not install RC then upgrade. rather just do a fresh install of release from scratch.

well even though they didnt update the download site, at least the site directories are browseable.

download the release here: http://download.truenas.com/TrueNAS-SCALE-Angelfish/22.02.0/

would be nice if they updated the website so folks don't have to go digging.

EDIT: the standard download site is now updated with the release. thanks!

 

[fmjyoolw]

For those who have problems with the APPs after the upgrade, just restore the backup you have done before, and the apps is restored.
Doesn´t need to roolback to RC2

Okay..I have no backup, that's so sad.

 

[pyrodex]

Upgrade went smooth but noticed a few issues after the system came up.

• Services that were set to start on boot didn't all start. Some examples were SSH, SMB, LLDP, TFTP, and UPS. I was able to click start and they started up fine but not on boot-up. Rebooted as a test afterwards and they came up fine.
• I had some ESX servers mounting the system via NFS and they would not connect after the first reboot. I tried everything and had to blow away the Datastore settings on the ESX side and recreate them for them to mount again. I've never had this issue across upgrades in the past and I've been running SCALE since 21.06-BETA.1

Other than that no other things to report.

BTW how do we clean up our older boot-pool snapshots across upgrades? I have a bunch of older ones and wanted to trim it back to maybe just RC2 and current version.

 

[morganL]

Ignore the "Updates are available for 22.02-RELEASE" message...... there is a bug in the updating software. More info to come.

 

[Ixian]

I updated my backup server and my test image (waiting to do my production server) - on both systems I get the updater error, which seems common, and on one I also had the issue where a number of services (SSH, UPS, etc.) didn't start on boot as configured but was able to manually start. For reasons I can't discern or suss out of the logs I didn't have the service auto-start problem on my test box. Both were 22.02-RC2 images that I upgraded from.

 

[truecharts]

Okay..I have no backup, that's so sad.

Apps are automatically backed up on update, our TrueCharts TrueTool CLI tool should also be able to restore those.
Though it's not tested very much.

 

[anodos]

Upgrade went smooth but noticed a few issues after the system came up.

• Services that were set to start on boot didn't all start. Some examples were SSH, SMB, LLDP, TFTP, and UPS. I was able to click start and they started up fine but not on boot-up. Rebooted as a test afterwards and they came up fine.
• I had some ESX servers mounting the system via NFS and they would not connect after the first reboot. I tried everything and had to blow away the Datastore settings on the ESX side and recreate them for them to mount again. I've never had this issue across upgrades in the past and I've been running SCALE since 21.06-BETA.1

NFS server was switched to kernel server. There may be some details of the NFS server configuration or exports that didn't transfer correctly in your situation. Hard to say off the cuff. If you're interested in investigating further, you can send me a PM and I can give instructions on getting the config from a previous boot environment so that I can see if there's a migration issue there. Glad you were able to work around the issue.

Depending on performance characteristics of server, you may need to increase the number of kernel threads for server. You can adjust via midclt call nfs.config (see number of servers) and midclt call nfs.update '{"servers": 16}' for example to increase to 16 threads.

 

[andysmile]

Edit: The problem is solved after I uncheck the advanced option under Network and Services of the app edit UI.


After I updated to 22.02, when I update several apps, they cannot be updated and have nodeport error. Would anyone know how to fix it?

Error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/middlewared/job.py", line 423, in run await self.future File "/usr/lib/python3/dist-packages/middlewared/job.py", line 459, in __run_body rv = await self.method(*([self] + args)) File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1261, in nf return await func(*args, **kwargs) File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1129, in nf res = await f(*args, **kwargs) File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/upgrade.py", line 116, in upgrade await self.upgrade_chart_release(job, release, options) File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/upgrade.py", line 266, in upgrade_chart_release config, context = await self.middleware.call( File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1318, in call return await self._call( File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1275, in _call return await methodobj(*prepared_call.args) File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/chart_release.py", line 332, in normalise_and_validate_values dict_obj = await self.middleware.call( File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1318, in call return await self._call( File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1275, in _call return await methodobj(*prepared_call.args) File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/validation.py", line 58, in validate_values await self.validate_question( File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/validation.py", line 81, in validate_question await self.validate_question( File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/validation.py", line 81, in validate_question await self.validate_question( File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/validation.py", line 81, in validate_question await self.validate_question( [Previous line repeated 1 more time] File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/validation.py", line 112, in validate_question verrors, parent_value, parent_value[sub_question['variable']], sub_question, KeyError: 'nodePort'
Close

 

[noconnor]

Upgrade went smooth but noticed a few issues after the system came up.

• Services that were set to start on boot didn't all start. Some examples were SSH, SMB, LLDP, TFTP, and UPS. I was able to click start and they started up fine but not on boot-up. Rebooted as a test afterwards and they came up fine.
• I had some ESX servers mounting the system via NFS and they would not connect after the first reboot. I tried everything and had to blow away the Datastore settings on the ESX side and recreate them for them to mount again. I've never had this issue across upgrades in the past and I've been running SCALE since 21.06-BETA.1

Other than that no other things to report.

BTW how do we clean up our older boot-pool snapshots across upgrades? I have a bunch of older ones and wanted to trim it back to maybe just RC2 and current version.

Thanks for pointing this out. My NFS datastore would not mount but when I reverted to RC2 it worked just fine again. I was going through a lot of troubleshooting about a missing 'nobody' group and NFSv4 (which I don't use) but simply removing and readding the datastore on the ESX side worked fine.

Now just to go re-register all my VMs...

 

[fmjyoolw]

From TrueNAS-22.02-RC.2-1 -> TrueNAS-22.02.RELEASE
The apt and apt-key commands cannot be executed because these two files have no executable attributes, is this intentional?

 

[waqarahmed]

@andysmile can you please create a bug report at https://jira.ixsystems.com ? Also please make sure to attach a debug of your system and also kindly provide the output of "midclt call chart.release.query | jq" ( please feel free to mask/hide any data which you think is sensitive from the output ). Thanks!

 

[pabloalcantara]

Okay..I have no backup, that's so sad.

Return the boot to RC2, and save the backup when prompeted to do the upgrade

 

[jgreco]

From TrueNAS-22.02-RC.2-1 -> TrueNAS-22.02.RELEASE
The apt and apt-key commands cannot be executed because these two files have no executable attributes, is this intentional?

Yes, of course, because you aren't supposed to be using them. TrueNAS is an appliance, and you are not supposed to be making changes to the base system. For Linux, add containers or virtual machines and do your "hacking" in those. For FreeBSD, jails or VM's. Making changes to the base OS is unsupported; if you are sufficiently clever, you can get it to work, but for heaven's sake please don't ask for support or help here in the forums on a hacked-up TrueNAS install.

@anodos is working on a ticket that might make this more readily apparent to new users on the platform.

 

[Etorix]

Please be aware that after a reboot it might take up to 30 minutes for the Kubernetes based Apps to start again.

I initiated upgrade from SCALE-RC2 to RELEASE… from a TrueCommand TrueChart running on my tiny test plateform along PiHole, and watched the process from the HTML5 IPMI console ;)
The OS update went on smoothly and PiHole came back up rather quickly, however TrueCommand indeed took about half an hour to "deploy". The card showed "2.1_9.0.42 Up to date" but clicking on it showed an update was available. After a manual upgrade, TrueCommand is up and running again. Was the delay due to updating and parsing the whole TrueCharts catalog?