Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.

Fix traceback during a Manual Upgrade of an HA system from 11.2 to 11.3

Description

I was doing a manal update of a TrueNAS HA system from TrueNAS-11.2-INTERNAL-4 to TrueNAS-11.3-MASTER-201911200917
The first controller updated and prompted me to failover

I failed over and did a manual update

expected str, bytes or os.PathLike object, not NoneType

Error: Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/middlewared/job.py", line 349, in run
await self.future
File "/usr/local/lib/python3.7/site-packages/middlewared/job.py", line 388, in __run_body
rv = await self.middleware.run_in_thread(self.method, *([self] + args))
File "/usr/local/lib/python3.7/site-packages/middlewared/utils/run_in_thread.py", line 10, in run_in_thread
return await self.loop.run_in_executor(self.run_in_thread_executor, functools.partial(method, *args, * kwargs))
File " /usr /local /lib /python3 .7 /site -packages /middlewared /utils /io_thread_pool_executor .py ", line 25, in run
result = self .fn( self.args, * self .kwargs)
File " /usr /local /lib /python3 .7 /site -packages /middlewared /schema .py ", line 953, in nf
return f( args, **kwargs)
File "/usr/local/lib/middlewared_truenas/plugins/failover.py", line 767, in upgrade
remote.sendfile(token, os.path.join(local_path, f), os.path.join(remote_path, f))
File "/usr/local/lib/python3.7/posixpath.py", line 80, in join
a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType

I was updating to TrueNAS-11.3-MASTER-201911200917-manual-update-unsigned

Jeff also had the same problem with another TrueNAS HA system

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Activity

Show:

Bug Clerk November 22, 2019 at 5:58 PM

Bonnie Follweiler November 21, 2019 at 5:22 PM
Edited

The work around for this issue is, after upgrading the first controller and doing a failover, Go to Advanced and activate Legacy mode. Log into Legacy mode and finish the update from there.

 

It would be helpful if either
the system could detect it is going from 11.2 to 11.3 and it would automatically active the Legacy mode before failover and it was in Legacy mode for the upgrade after failover

or

There was a popup window after the first controller is updated with instructions on how to activate the Legacy mode and informing the user they will need to upgrade in Legacy mode

Complete
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Parent

More fields

Katalon Platform

Created November 21, 2019 at 3:15 PM
Updated July 1, 2022 at 4:47 PM
Resolved November 22, 2019 at 5:58 PM
Configure