search

truecharts / public

Community Helm Chart Repository
https://truecharts.org
GNU Affero General Public License v3.0
1.14k stars 619 forks source link

Cannot install unifi app #8126

Closed nautilus7 closed 1 year ago

nautilus7 commented 1 year ago

App Name

unifi

SCALE Version

22.12.2

App Version

14.0.7

Application Events

app not installed

Application Logs

app not installed

Application Configuration

default app setting - nothing changed at all

Describe the bug

Error: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 426, in run
    await self.future
  File "/usr/lib/python3/dist-packages/middlewared/job.py", line 461, in __run_body
    rv = await self.method(*([self] + args))
  File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1186, in nf
    res = await f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/middlewared/schema.py", line 1318, in nf
    return await func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/middlewared/plugins/chart_releases_linux/chart_release.py", line 486, in do_create
    await self.middleware.call(
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1386, in call
    return await self._call(
  File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1346, 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 1249, 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 install chart release: Error: INSTALLATION FAILED: create: failed to create: secrets "sh.helm.release.v1.unifi.v1" is forbidden: unable to create new content in namespace ix-unifi because it is being terminated

To Reproduce

  1. I had the unifi app installed. The old version. The app name was "unifi".
  2. I deleted the app, BUT did not check the "delete docker images used by the app".
  3. Tried to install the app again, the new version this time. Default settings, default everything, SAME name "unifi".
  4. The app will not install.
  5. Then tried to install it again, but this time with a different name "unifi2". The now installs successfully.

Expected Behavior

install

Screenshots

not applicable

Additional Context

not applicable

I've read and agree with the following

stavros-k commented 1 year ago

Wait couple of minutes and try again. Takes some time to cleanup sometimes (this is how kubernetes work)

nautilus7 commented 1 year ago

I restarted twice! Isn't this enough?

Is this why the command below (I am setting up metalLB, thus the command) shows the uinifi app there and still having an IP address?

k3s kubectl get svc -A

NAMESPACE             NAME                          TYPE           CLUSTER-IP       EXTERNAL-IP     PORT(S)                        AGE
default               kubernetes                    ClusterIP      172.17.0.1       <none>          443/TCP                        236d
kube-system           kube-dns                      ClusterIP      172.17.0.10      <none>          53/UDP,53/TCP,9153/TCP         236d
kube-system           kubelet                       ClusterIP      None             <none>          10250/TCP,10255/TCP,4194/TCP   160d
cert-manager          cert-manager                  ClusterIP      172.17.87.11     <none>          9402/TCP                       91d
cert-manager          cert-manager-webhook          ClusterIP      172.17.210.48    <none>          443/TCP                        91d
metallb-system        webhook-service               ClusterIP      172.17.87.10     <none>          443/TCP                        160d
prometheus-operator   prometheus-operator           ClusterIP      None             <none>          8080/TCP                       160d
ix-mosquitto          mosquitto-websockets          ClusterIP      172.17.47.167    <none>          9001/TCP                       86d
cnpg-system           cnpg-webhook-service          ClusterIP      172.17.79.181    <none>          443/TCP                        160d
ix-wordpress          wordpress-mariadb             ClusterIP      172.17.1.241     <none>          3306/TCP                       35d
ix-home-assistant     home-assistant-postgresql     ClusterIP      172.17.120.87    <none>          5432/TCP                       5d11h
ix-mosquitto          mosquitto                     LoadBalancer   172.17.15.165    192.168.10.10   1883:40970/TCP                 59d
ix-home-assistant     home-assistant-codeserver     LoadBalancer   172.17.106.161   192.168.10.13   36107:15610/TCP                5d11h
ix-home-assistant     home-assistant                LoadBalancer   172.17.238.47    192.168.10.13   8123:26084/TCP                 5d11h
ix-wordpress          wordpress                     LoadBalancer   172.17.41.105    192.168.10.14   10591:11441/TCP                35d
ix-adguard-home       adguard-home-dns-crypt        LoadBalancer   172.17.150.50    192.168.10.15   5443/TCP                       131m
ix-adguard-home       adguard-home-dns-crypt-udp    LoadBalancer   172.17.91.84     192.168.10.15   5443/UDP                       131m
ix-adguard-home       adguard-home-dns-https        LoadBalancer   172.17.172.82    192.168.10.15   10234/TCP                      131m
ix-adguard-home       adguard-home-dns-https-udp    LoadBalancer   172.17.198.214   192.168.10.15   10234/UDP                      131m
ix-adguard-home       adguard-home-dns-quic-udp-1   LoadBalancer   172.17.231.22    192.168.10.15   784/UDP,853/UDP,8853/UDP       131m
ix-adguard-home       adguard-home-dns-tcp          LoadBalancer   172.17.251.186   192.168.10.15   53/TCP                         131m
ix-adguard-home       adguard-home-dns-udp          LoadBalancer   172.17.222.135   192.168.10.15   53/UDP                         131m
ix-unifi              unifi-comm                    LoadBalancer   172.17.103.68    192.168.10.11   8080:21565/TCP                 3h3m
ix-unifi              unifi-guestportal             LoadBalancer   172.17.252.238   192.168.10.11   8880:38157/TCP,8843:9105/TCP   3h3m
ix-unifi              unifi                         LoadBalancer   172.17.165.131   192.168.10.11   8443:37178/TCP                 3h3m
ix-unifi              unifi-speedtest               LoadBalancer   172.17.72.106    192.168.10.11   6789:41548/TCP                 3h3m
ix-unifi              unifi-stun                    LoadBalancer   172.17.182.57    192.168.10.11   3478:16728/UDP                 3h3m
ix-adguard-home       adguard-home                  LoadBalancer   172.17.160.143   192.168.10.11   10232/TCP                      131m
ix-frigate            frigate                       LoadBalancer   172.17.197.96    192.168.40.40   10500:45030/TCP                11d
ix-frigate            frigate-rtmp                  LoadBalancer   172.17.50.230    192.168.40.40   1935:46840/TCP                 11d
ix-unifi2             unifi2-comm                   LoadBalancer   172.17.39.132    192.168.10.12   8080/TCP                       39s
ix-unifi2             unifi2-guestportal            LoadBalancer   172.17.76.53     192.168.10.12   8880/TCP,8843/TCP              39s
ix-unifi2             unifi2                        LoadBalancer   172.17.128.56    192.168.10.12   8443/TCP                       39s
ix-unifi2             unifi2-speedtest              LoadBalancer   172.17.35.195    192.168.10.12   6789/TCP                       39s
ix-unifi2             unifi2-stun                   LoadBalancer   172.17.153.17    192.168.10.12   3478/UDP                       39s
nautilus7 commented 1 year ago

Several hours later... no change, still cannot install unifi using "unifi" as app name.

PrivatePuffin commented 1 year ago

This should’ve been closed right away. We’re not related to iXsystems and have zero influence over how they design(ed) their kubernetes stack.

this is 100% unrelated to the chart, as wd have zero control over how namespace deletion is handled.

Feel free to file a ticket on the iX Jora instead though.

PrivatePuffin commented 1 year ago

*jira