dazzling-processor-39269
02/23/2024, 3:21 PMdazzling-processor-39269
02/23/2024, 3:21 PMdazzling-processor-39269
02/23/2024, 3:22 PMdazzling-processor-39269
02/23/2024, 3:24 PMdazzling-processor-39269
02/23/2024, 3:24 PMdazzling-processor-39269
02/23/2024, 3:52 PMdazzling-processor-39269
02/23/2024, 3:52 PMdamjank@virt-work:~$ kubectl get pod -n longhorn-system -l app=longhorn-manager
NAME READY STATUS RESTARTS AGE
longhorn-manager-7t9n5 1/1 Running 0 20h
longhorn-manager-ld4qf 1/1 Running 1 (20h ago) 20h
longhorn-manager-s7528 1/1 Running 0 20h
damjank@virt-work:~$ kubectl get csinodes
NAME DRIVERS AGE
pk8s-agent-1 1 21h
pk8s-agent-2 1 21h
pk8s-agent-3 1 21h
pk8s-master-1 0 22h
pk8s-master-2 0 22h
pk8s-master-3 0 22h
pk8s-stor-1 1 20h
pk8s-stor-2 1 20h
pk8s-stor-3 1 20h
red-queen-31013
02/26/2024, 1:32 PMaccessMode
to StorageProfiles without patching? https://github.com/kubevirt/containerized-data-importer/issues/3005ripe-intern-96703
02/27/2024, 8:36 AMcool-architect-86201
02/27/2024, 12:44 PMdamp-football-74194
02/27/2024, 4:43 PMabundant-hair-58573
02/27/2024, 9:35 PMcool-architect-86201
02/28/2024, 10:16 AMbillowy-painting-56466
02/29/2024, 1:52 AMcool-architect-86201
03/02/2024, 6:49 AMkubectl describe pvc -n web3-helm near-mainnet-cziaw5wa0o28
Name: near-mainnet-cziaw5wa0o28
Namespace: web3-helm
StorageClass: longhorn-v2
Status: Bound
Volume: pvc-d585097c-79d7-4ff4-9836-0f72065b13cc
Labels: <http://app.kubernetes.io/instance=near-mainnet-cziaw5wa0o28|app.kubernetes.io/instance=near-mainnet-cziaw5wa0o28>
<http://app.kubernetes.io/managed-by=Helm|app.kubernetes.io/managed-by=Helm>
<http://app.kubernetes.io/name=near|app.kubernetes.io/name=near>
<http://helm.sh/chart=near-v1|helm.sh/chart=near-v1>
Annotations: <http://meta.helm.sh/release-name|meta.helm.sh/release-name>: near-mainnet-cziaw5wa0o28
<http://meta.helm.sh/release-namespace|meta.helm.sh/release-namespace>: web3-helm
<http://pv.kubernetes.io/bind-completed|pv.kubernetes.io/bind-completed>: yes
<http://pv.kubernetes.io/bound-by-controller|pv.kubernetes.io/bound-by-controller>: yes
<http://volume.beta.kubernetes.io/storage-provisioner|volume.beta.kubernetes.io/storage-provisioner>: <http://driver.longhorn.io|driver.longhorn.io>
<http://volume.kubernetes.io/storage-provisioner|volume.kubernetes.io/storage-provisioner>: <http://driver.longhorn.io|driver.longhorn.io>
Finalizers: [<http://kubernetes.io/pvc-protection|kubernetes.io/pvc-protection>]
Capacity: 1500Gi
Access Modes: RWO
VolumeMode: Filesystem
Used By: near-mainnet-cziaw5wa0o28-0
Conditions:
Type Status LastProbeTime LastTransitionTime Reason Message
---- ------ ----------------- ------------------ ------ -------
Resizing True Mon, 01 Jan 0001 00:00:00 +0000 Sat, 02 Mar 2024 06:36:01 +0000
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning VolumeResizeFailed 29m (x112 over 11h) external-resizer <http://driver.longhorn.io|driver.longhorn.io> resize volume "pvc-d585097c-79d7-4ff4-9836-0f72065b13cc" by resizer "<http://driver.longhorn.io|driver.longhorn.io>" failed: rpc error: code = Internal desc = Bad response statusCode [500]. Status [500 Internal Server Error]. Body: [message=unable to expand volume pvc-d585097c-79d7-4ff4-9836-0f72065b13cc: admission webhook "<http://validator.longhorn.io|validator.longhorn.io>" denied the request: changing volume size for volume pvc-d585097c-79d7-4ff4-9836-0f72065b13cc is not supported for data engine v2, code=Internal Server Error, detail=] from [<http://longhorn-backend:9500/v1/volumes/pvc-d585097c-79d7-4ff4-9836-0f72065b13cc?action=expand>]
Normal Resizing 3m56s (x428 over 11h) external-resizer <http://driver.longhorn.io|driver.longhorn.io> External resizer is resizing volume pvc-d585097c-79d7-4ff4-9836-0f72065b13cc
witty-air-27615
03/05/2024, 2:46 PMnarrow-electrician-19186
03/06/2024, 7:00 AMcurved-piano-98970
03/06/2024, 8:17 PMlonghorn_backup_state[10m] >= 4
will print out metrics that are not from the last 10 minutes or so? but will print out many others failed backups? I even tried to set it to 1 min but same results? How do you guys monitor your backups? or how should I do it?ripe-intern-96703
03/08/2024, 12:32 PMtall-cartoon-14232
03/09/2024, 1:07 AMWarning FailedAttachVolume 12s (x7 over 47s) attachdetach-controller AttachVolume.Attach failed for volume "pvc-5b1f286a-58a6-4ed7-b5d2-f39095822095" : rpc error: code = Aborted desc = volume pvc-5b1f286a-58a6-4ed7-b5d2-f39095822095 is not ready for workloads
sparse-ghost-91718
03/09/2024, 4:52 PMpolite-alarm-96476
03/12/2024, 3:57 PMabundant-hair-58573
03/12/2024, 8:58 PMcool-architect-86201
03/13/2024, 2:44 AMdamp-football-74194
03/13/2024, 9:03 AMdamp-football-74194
03/13/2024, 9:33 AMpowerful-table-93807
03/18/2024, 3:02 PMbright-fireman-42144
03/18/2024, 9:43 PMbland-article-62755
03/18/2024, 9:45 PMbright-fireman-42144
03/18/2024, 9:49 PM