Switching back to CORE train has issues.

Description

I built a test VM with CORE, with the intention of seeing if a SCALE train change for testing was destructive.
I switched to SCALE, booted the system.
I then chose CORE from the boot environment option upon a reboot and this produces minor errors, which do seem concerning.
These are the errors in the UI / Alerts on CORE upon that reboot back.

 

rror: concurrent.futures.process._RemoteTraceback: """ Traceback (most recent call last): File "/usr/lib/python3.11/concurrent/futures/process.py", line 256, in _process_worker r = call_item.fn(*call_item.args, **call_item.kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/worker.py", line 112, in main_worker res = MIDDLEWARE._run(*call_args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/worker.py", line 46, in _run return self._call(name, serviceobj, methodobj, args, job=job) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/worker.py", line 34, in _call with Client(f'ws+unix://{MIDDLEWARE_RUN_DIR}/middlewared-internal.sock', py_exceptions=True) as c: File "/usr/lib/python3/dist-packages/middlewared/worker.py", line 40, in _call return methodobj(*params) ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 50, in nf res = f(*args, **kwargs) ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 181, in nf return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/plugins/zfs_/dataset.py", line 169, in do_update with libzfs.ZFS() as zfs: File "libzfs.pyx", line 529, in libzfs.ZFS.__exit__ File "/usr/lib/python3/dist-packages/middlewared/plugins/zfs_/dataset.py", line 178, in do_update self.update_zfs_object_props(properties, dataset) File "/usr/lib/python3/dist-packages/middlewared/plugins/zfs_/dataset.py", line 247, in update_zfs_object_props verrors.check() File "/usr/lib/python3/dist-packages/middlewared/service_exception.py", line 70, in check raise self middlewared.service_exception.ValidationErrors: [EINVAL] properties.org.freenas:quota_warning: Property does not exist and cannot be inherited [EINVAL] properties.org.freenas:quota_critical: Property does not exist and cannot be inherited [EINVAL] properties.org.freenas:refquota_warning: Property does not exist and cannot be inherited [EINVAL] properties.org.freenas:refquota_critical: Property does not exist and cannot be inherited """ The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/middlewared/main.py", line 201, in call_method result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1342, in _call return await methodobj(*prepared_call.args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/service/crud_service.py", line 180, in update return await self.middleware._call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1342, in _call return await methodobj(*prepared_call.args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/service/crud_service.py", line 197, in nf rv = await func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 44, in nf res = await f(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 177, in nf return await func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/plugins/pool_/dataset.py", line 894, in do_update await self.middleware.call('zfs.dataset.update', id, {'properties': props}) File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1399, in call return await self._call( ^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1342, in _call return await methodobj(*prepared_call.args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/service/crud_service.py", line 180, in update return await self.middleware._call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1350, in _call return await self._call_worker(name, *prepared_call.args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1356, in _call_worker return await self.run_in_proc(main_worker, name, args, job) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1267, in run_in_proc return await self.run_in_executor(self.__procpool, method, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1251, in run_in_executor return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ middlewared.service_exception.ValidationErrors: [EINVAL] properties.org.freenas:quota_warning: Property does not exist and cannot be inherited [EINVAL] properties.org.freenas:quota_critical: Property does not exist and cannot be inherited [EINVAL] properties.org.freenas:refquota_warning: Property does not exist and cannot be inherited [EINVAL] properties.org.freenas:refquota_critical: Property does not exist and cannot be inherited

This is discussed here:

https://www.truenas.com/community/threads/unable-to-go-from-core-to-scale.116977/

 

 

More concerning is that the “upgrade” section of TrueNAS is now ‘locked to’ SCALE? So to speak? Despite being on the 13 Stable train after selecting old CORE boot environment, the upgrade page is suggesting that I continue with the upgrade.

https://i.imgur.com/qD26SO5.png

Problem/Justification

None

Impact

None

Attachments

1
  • 04 Apr 2024, 01:47 AM

Activity

Show:

Bug Clerk April 5, 2024 at 4:25 PM

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

Alexandra Bain April 5, 2024 at 4:24 PM

As per the migration guide the migration from core to scale is a one way operation.
https://www.truenas.com/docs/scale/gettingstarted/migrate/migrateprep/

Daniel Pizappi April 4, 2024 at 2:30 PM

Thank you for this report . I have put it into our queue for our engineers to review.

disk diddler April 4, 2024 at 1:46 AM

Debug file is attached.
LET ME BE CLEAR, this is extremely easy to recreate and test this issue. Any of your support staff with a VM and experience could do this in 20 minutes or less, probably as little as 5 minutes.

 

Understand CORE is now “DOA” but please consider fixing this issue as convincing people to test SCALE is going to be more difficult if there’s risks like this going back.

disk diddler April 4, 2024 at 1:41 AM

Please note the URL auto generator is INCORRECT for some reason?
It’s not “CIFS SERVICE does not start after FreeNAS bootup “
It’s :
https://www.truenas.com/community/threads/unable-to-go-from-core-to-scale.116977/

Won't Do

Details

Assignee

Reporter

Labels

Impact

Low

Time remaining

0m

Components

Fix versions

Affects versions

Priority

Katalon Platform

Created April 4, 2024 at 1:39 AM
Updated May 8, 2024 at 5:56 PM
Resolved April 5, 2024 at 4:25 PM