Truenas scale nextcloud pod not start

Hi comunity

I have
OS Version:TrueNAS-SCALE-22.12.1
Product:VMware Virtual Platform
Model:Intel(R) Xeon(R) CPU E5-2450 v2 @ 2.50GHz
Memory:8 GiB

I install app ugrade from nextcloud 280.0.24 to 29.0.1 but the pot not start

I have this error on save the configuration of app

Error
EFAULT Failed to update chart release: Error: UPGRADE FAILED: cannot patch "nextcloud-prod-postgres" with kind Deployment: Deployment.apps "nextcloud-prod-postgres" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/instance":"nextcloud-prod-postgres", "app.kubernetes.io/name":"nextcloud-postgres", "pod.name":"postgres"}, MatchExpressions:v1.LabelSelectorRequirement(nil)}: field is immutable
More info…

Error: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 427, in run
    await self.future
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 465, in __run_body
    rv = await self.method(*(self + args))
  File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1247, in nf
    res = await f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1379, in nf
    return await func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/chart_release.py", line 553, in do_update
    await self.middleware.call('chart.release.helm_action', chart_release, chart_path, config, 'update')
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1368, in call
    return await self._call(
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1328, in _call
    return await self.run_in_executor(prepared_call.executor, methodobj, *prepared_call.args)
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1231, in run_in_executor
    return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
  File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/helm.py", line 44, in helm_action
    raise CallError(f'Failed to {tn_action} chart release: {stderr.decode()}')
middlewared.service_exception.CallError: EFAULT Failed to update chart release: Error: UPGRADE FAILED: cannot patch "nextcloud-prod-postgres" with kind Deployment: Deployment.apps "nextcloud-prod-postgres" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{"app.kubernetes.io/instance":"nextcloud-prod-postgres", "app.kubernetes.io/name":"nextcloud-postgres", "pod.name":"postgres"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable

I try to solve rollback the upgrade but cant start
cant stop the app and can start the web portal

when i try to start the log i se these:

Docker

WARNING: Your user does not have sudo privileges so /usr/local/bin/k3s command will run
on your behalf. This might cause permission issues.


error: unable to upgrade connection: container not found (“nextcloud”)

–Application Name:nextcloud-prodPod Name:nextcloud-prod-postgres-59459bd95-zdp9gContainer Name:nextcloud-prod

2024-05-09 16:22:00.687568-06:002024-05-09T16:22:00.687568361-06:00

2024-05-09 16:22:00.687619-06:00PostgreSQL Database directory appears to contain a database; Skipping initialization

2024-05-09 16:22:00.687641-06:002024-05-09T16:22:00.687641783-06:00

2024-05-09 16:22:01.164237-06:002024-05-09 22:22:01.164 UTC LOG: starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit

2024-05-09 16:22:01.165208-06:002024-05-09 22:22:01.165 UTC LOG: listening on IPv4 address "0.0.0.0", port 5432

2024-05-09 16:22:01.165265-06:002024-05-09 22:22:01.165 UTC LOG: listening on IPv6 address "::", port 5432

2024-05-09 16:22:01.166974-06:002024-05-09 22:22:01.166 UTC LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"

2024-05-09 16:22:01.199338-06:002024-05-09 22:22:01.199 UTC LOG: database system was shut down at 2024-05-09 22:13:10 UTC

2024-05-09 16:22:01.240708-06:002024-05-09 22:22:01.237 UTC LOG: database system is ready to accept connections

– Application Name:nextcloud-prodPod Name:nextcloud-prod-redis-777f9f468f-ldpmdContainer Name:nextcloud-prod

2024-05-09 16:22:00.317879-06:00 [38;5;6mredis [38;5;5m22:22:00.31 [0m

2024-05-09 16:22:00.324024-06:00 [38;5;6mredis [38;5;5m22:22:00.31 [0m[1mWelcome to the Bitnami redis container[0m

2024-05-09 16:22:00.324061-06:00[38;5;6mredis [38;5;5m22:22:00.32 [0mSubscribe to project updates by watching 

2024-05-09 16:22:00.328411-06:00[38;5;6mredis [38;5;5m22:22:00.32 [0mSubmit issues and feature requests at [0m

2024-05-09 16:22:00.332492-06:00[38;5;6mredis [38;5;5m22:22:00.32 [0m

2024-05-09 16:22:00.339389-06:00[38;5;6mredis [38;5;5m22:22:00.33 [0m[38;5;2mINFO [0m ==> ** Starting Redis setup **

2024-05-09 16:22:00.431813-06:00[38;5;6mredis [38;5;5m22:22:00.42 [0m[38;5;2mINFO [0m ==> Initializing Redis
2024-05-09 16:22:00.479309-06:00[38;5;6mredis [38;5;5m22:22:00.47 [0m[38;5;2mINFO [0m ==> Setting Redis config file

2024-05-09 16:22:00.682064-06:00[38;5;6mredis [38;5;5m22:22:00.67 [0m[38;5;2mINFO[0m ==> ** Redis setup finished! **

2024-05-09 16:22:00.682086-06:002024-05-09T16:22:00.682086331-06:00

2024-05-09 16:22:00.703040-06:00[38;5;6mredis [38;5;5m22:22:00.70 [0m[38;5;2mINFO [0m ==> ** Starting Redis **

2024-05-09 16:22:00.951741-06:001:C 09 May 2024 22:22:00.951 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

2024-05-09 16:22:00.951791-06:001:C 09 May 2024 22:22:00.951 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started

2024-05-09 16:22:00.951835-06:001:C 09 May 2024 22:22:00.951 # Configuration loaded

2024-05-09 16:22:00.952337-06:001:M 09 May 2024 22:22:00.952 * monotonic clock: POSIX clock_gettime

2024-05-09 16:22:00.955718-06:001:M 09 May 2024 22:22:00.955 * Running mode=standalone, port=6379.

2024-05-09 16:22:00.955747-06:001:M 09 May 2024 22:22:00.955 # Server initialized

2024-05-09 16:22:00.963511-06:001:M 09 May 2024 22:22:00.963 * Creating AOF base file appendonly.aof.1.base.rdb on server start

2024-05-09 16:22:00.964717-06:001:M 09 May 2024 22:22:00.964 * Creating AOF incr file appendonly.aof.1.incr.aof on server start

2024-05-09 16:22:00.964746-06:001:M 09 May 2024 22:22:00.964 * Ready to accept connections

Are you any idea how to repare or backup the nextcloud pot to mount in other instance