Netbox worker unable to run custom scripts

[iamjpy]

I have a very simple custom script which has been imported via the UI.

from extras.scripts import Script

class Test(Script):
    def run(self, data, commit):
        
        self.log_info("Netbox Test")

When it runs, it returns an Errored result in the UI:

The logs show the job succeeded:

netbox-worker-7996964d7-95h5l netbox-worker 18:13:01 default: handle(commit=True, data={}, job=<Job: 9b08a3fc-5318-42e2-86e0-7d8cd5d84c56>, request=<utilities.request.NetBoxFakeRequest object at 0x7f0882900380>) (9b08a3fc-5318-42e2-86e0-7d8cd5d84c56)
netbox-68bf9dd964-jtnjf netbox 10.254.0.182 - - [28/Feb/2025:18:13:01 +0000] "POST /extras/scripts/6/ HTTP/1.1" 302 0 "https://netbox.mgmt-dev.itential.io/extras/scripts/6/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:135.0) Gecko/20100101 Firefox/135.0"
netbox-worker-7996964d7-95h5l netbox-worker 18:13:01 Successfully completed handle(commit=True, data={}, job=<Job: 9b08a3fc-5318-42e2-86e0-7d8cd5d84c56>, request=<utilities.request.NetBoxFakeRequest object at 0x7f0882900380>) job in 0:00:00.058231s on worker 953529f739904ec7a05ffcca98966c08
netbox-worker-7996964d7-95h5l netbox-worker 18:13:01 default: Job OK (9b08a3fc-5318-42e2-86e0-7d8cd5d84c56)
netbox-worker-7996964d7-95h5l netbox-worker 18:13:01 Result is kept for 500 seconds

Using the CLI, I'm able to run the custom script with successful results on the netbox pod,

$ python /opt/netbox/netbox/manage.py runscript netbox_test.Test
🧬 loaded config '/etc/netbox/config/configuration.py'
🧬 loaded config '/etc/netbox/config/extra.py'
🧬 loaded config '/etc/netbox/config/logging.py'
🧬 loaded config '/etc/netbox/config/plugins.py'
[2025-02-28 18:15:17,868][INFO] - Running script (commit=False)
[2025-02-28 18:15:17,869][INFO] - Netbox Test
[2025-02-28 18:15:17,869][INFO] - Database changes have been reverted automatically.
[2025-02-28 18:15:17,876][INFO] - Script completed in 0 minutes, 0.01 seconds

But I'm unable to execute the script on the CLI of the netbox-worker pod nor am I able to access the /opt/netbox/netbox/scripts/ directory in the netbox-worker container

$ python /opt/netbox/netbox/manage.py runscript netbox_test.Test
🧬 loaded config '/etc/netbox/config/configuration.py'
🧬 loaded config '/etc/netbox/config/extra.py'
🧬 loaded config '/etc/netbox/config/logging.py'
🧬 loaded config '/etc/netbox/config/plugins.py'
Traceback (most recent call last):
  File "/opt/netbox/netbox/manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
    utility.execute()
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/__init__.py", line 436, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 413, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 459, in execute
    output = self.handle(*args, **options)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/netbox/extras/management/commands/runscript.py", line 59, in handle
    logger = logging.getLogger(f"netbox.scripts.{script.full_name}")
                                                 ^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'full_name'
$ cd /opt/netbox/netbox/scripts
sh: 15: cd: can't cd to /opt/netbox/netbox/scripts

I have a netbox deployment installed using the netbox-chart helm chart. The netbox and netbox-worker pods are running on the same node with scriptsPersistence enabled. I verified the netbox-scripts volume is mounted to both pods with RWO access. Both pods security contexts are configured with the same user and group UID

It seems that when both the netbox and netbox-worker pods are running at the same time, one of them loses access to the scripts directory, usually the netbox-worker which I believe results in the the Errored result upon executing the script via the UI. When I restart the pods in a different order, the netbox-worker pod regains access to the scripts volume and then the netbox pod loses it which results in a permissions error when running the custom script in the UI.

Any help is appreciated