brash-monitor-41966
08/23/2022, 2:30 PMcareful-optician-75900
08/23/2022, 2:32 PM2022/08/22 15:41:55 [ERROR] Error during subscribe write tcp 192.68.101.82:80->192.68.101.253:48714: write: broken pipe
3798840e408c4ea71783381ecd2e9af30baad65974 fetch origin 59bb6cc645129c1a89fc54a720a63c0971f5ede4 error: exit status 128, detail: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
fatal: the remote end hung up unexpectedly
, requeuing
2022/08/22 15:26:14 [ERROR] error syncing 'rancher-partner-charts': handler helm-clusterrepo-ensure: git -C /var/lib/rancher-data/local-catalogs/v2/rancher-partner-charts/8f17acdce9bffd6e05a58a3798840e408c4ea71783381ecd2e9af30baad65974 fetch origin 59bb6cc645129c1a89fc54a720a63c0971f5ede4 error: exit status 128, detail: fatal: unable to access '<https://git.rancher.io/partner-charts/>': The requested URL returned error: 502
, requeuing
creamy-room-58344
08/23/2022, 2:52 PMmodern-vr-23407
08/23/2022, 4:57 PMcreamy-room-58344
08/23/2022, 5:08 PMboundless-daybreak-2545
08/23/2022, 5:09 PMlittle-ambulance-5584
08/23/2022, 6:58 PMacceptable-xylophone-16224
08/23/2022, 9:32 PMkubectl exec
using the Rancher generated Kubeconfig. The command results in a blank error message: Error from server:
. Upon further investigation, it seems that the exec
command is unable to post to the Rancher proxy for the API server, and it receives a 403 forbidden
response:
POST https://<rancher-url>/k8s/clusters/local/api/v1/namespaces/<namespace>/pods/<pod>/exec?command=sh&container=<container>&stdin=true&stdout=true&tty=true 403 Forbidden in 238 milliseconds
All of our requests are routed through nginx, and we've confirmed that the nginx ingress receives the same 403 error. However, turning on trace logs for the Rancher pods, it appears that the message was never processed in the pod. We've also verified that our RBAC rules are sufficient for executing an exec
command as all kubectl auth can-i
prompts return "yes." Please let me know if you have any ideas on troubleshooting this issue. Thank you!great-planet-76498
08/23/2022, 10:08 PMlimactl
being flagged as malware and deleted on macOS, making using any version of Rancher Desktop impossible. Would hate to have my team revert to Docker Desktop for Mac.creamy-pencil-82913
08/24/2022, 4:44 AMadventurous-addition-59971
08/24/2022, 6:23 AMfuture-account-50371
08/24/2022, 8:30 AMmost-sunset-36476
08/24/2022, 9:30 AMmost-sunset-36476
08/24/2022, 9:47 AMmost-sunset-36476
08/24/2022, 9:49 AMchilly-telephone-51989
08/24/2022, 10:48 AMtall-school-18125
08/24/2022, 11:21 AMmost-sunset-36476
08/24/2022, 11:34 AMclever-mechanic-71254
08/24/2022, 12:25 PMbrash-monitor-41966
08/24/2022, 3:58 PMbrash-monitor-41966
08/24/2022, 3:58 PMbrash-monitor-41966
08/24/2022, 3:58 PMdamp-toothbrush-26028
08/24/2022, 4:13 PMp11-kit: couldn't create file: /var/lib/ca-certificates/java-cacerts: Permission denied
p11-kit: couldn't make directory writable: /var/lib/ca-certificates/openssl: Operation not permitted
p11-kit: couldn't make directory writable: /var/lib/ca-certificates/pem: Operation not permitted
/usr/lib/ca-certificates/update.d/99certbundle.run: line 21: /var/lib/ca-certificates/ca-bundle.pem.new: Permission denied
I feel like that might be somehow filesystem related? I can't find any fields in the Helm chart values to change the RunAs user, nor does it look like I'm using any sort of persistent storage, so IDK why the containers would be getting permission denied like that.best-actor-8484
08/24/2022, 4:20 PMboundless-daybreak-2545
08/24/2022, 4:55 PMflaky-shampoo-86024
08/24/2022, 7:09 PMbored-laptop-94633
08/24/2022, 8:17 PMEvents:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 13m default-scheduler 0/1 nodes are available: 1 node(s) had untolerated taint {<http://node.cloudprovider.kubernetes.io/uninitialized|node.cloudprovider.kubernetes.io/uninitialized>: true}. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
Warning FailedScheduling 8m40s default-scheduler 0/1 nodes are available: 1 node(s) had untolerated taint {<http://node.cloudprovider.kubernetes.io/uninitialized|node.cloudprovider.kubernetes.io/uninitialized>: true}. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.
sparse-dog-48948
08/25/2022, 2:20 AMrough-pager-2467
08/25/2022, 4:36 AMacceptable-salesmen-97792
08/25/2022, 7:59 AM