[QUESTION] Unable to attach a volume to a pod in k3s installation

Question
I have a new deployment of Longhorn and whenever I try to start a pod, it can't attach to the volume. I have created the volume beforehand with no issue, but when I launch the deployment, it tries to attach to the volume, but fails.
In the Longhorn UI, the volume shows as attaching, but if I run kubectl describe pod then I get this error message:
Type     Reason              Age                From                     Message
  ----     ------              ----               ----                     -------
  Normal   Scheduled           3m19s              default-scheduler        Successfully assigned leobigfoot/radarr-deployment-69cf4c4f58-hvxvq to k8srv03
  Warning  FailedAttachVolume  79s                attachdetach-controller  AttachVolume.Attach failed for volume "pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912" : Attach timeout for volume pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912
  Warning  FailedMount         76s                kubelet                  Unable to attach or mount volumes: unmounted volumes=[radarr-config], unattached volumes=[radarr-config radarr-downloads radarr-movies kube-api-access-s6zh8]: timed out waiting for the condition
  Warning  FailedAttachVolume  12s (x7 over 78s)  attachdetach-controller  AttachVolume.Attach failed for volume "pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912" : rpc error: code = DeadlineExceeded desc = Failed to attach volume pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912 to node k8srv03

Environment:

Longhorn version: v1.1.1 (but in the UI, under Setting, it says v1.2.0m but when I run longhorn -v, it says v1.1.1)
Kubernetes version: v1.21.5+k3s1
Node config

OS type and version: Ubuntu 20.04.3 LTS
CPU per node: 4 cores
Memory per node: 8GB
Disk type: USB3 connected SSD
Network bandwidth and latency between the nodes: 1Gb/s

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): baremetal on Raspberry Pi 4

Additional context
Below is an extract of the logs from the longhorn-manager pod:
time="2021-10-02T16:07:08Z" level=info msg="Engine got new owner k8srv03" controller=longhorn-engine engine=pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-e-5537a1d5 node=k8srv03
time="2021-10-02T16:07:08Z" level=debug msg="Instance handler updated instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-e-5537a1d5 state, old state , new state stopped"
time="2021-10-02T16:07:08Z" level=debug msg="Replica controller picked up" controller=longhorn-replica controllerID=k8srv03 dataPath= node=k8srv03 nodeID= ownerID= replica=pvc-5daba64c-bec3-47ae-
9d01-32acfd0ab912-r-b3ba7a36
time="2021-10-02T16:07:08Z" level=debug msg="Instance handler updated instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 state, old state , new state stopped"
time="2021-10-02T16:07:08Z" level=debug msg="Requeue longhorn-system/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 due to conflict" controller=longhorn-replica dataPath= error="Operation ca
nnot be fulfilled on replicas.longhorn.io \"pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36\": the object has been modified; please apply your changes to the latest version and try again" nod
e=k8srv03 nodeID= ownerID= replica=pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36
time="2021-10-02T16:07:08Z" level=debug msg="Instance handler updated instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 state, old state , new state stopped"
<IP_ADDRESS> - - [02/Oct/2021:16:07:35 +0000] "GET /v1/backingimages HTTP/1.1" 200 118 "https://openstack01/k8s/clusters/c-fnshj/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend
:80/proxy/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36"
<IP_ADDRESS> - - [02/Oct/2021:16:07:38 +0000] "GET /v1/backingimages HTTP/1.1" 200 118 "https://openstack01/k8s/clusters/c-fnshj/api/v1/namespaces/longhorn-system/services/http:longhorn-frontend
:80/proxy/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36"
time="2021-10-02T16:07:53Z" level=debug msg="Volume got new owner k8srv03" accessMode=rwo controller=longhorn-volume frontend=blockdev migratable=false node=k8srv03 owner=k8srv01 state=detached v
olume=pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912
time="2021-10-02T16:07:54Z" level=debug msg="Prepare to create instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36"
time="2021-10-02T16:07:54Z" level=info msg="Event(v1.ObjectReference{Kind:\"Replica\", Namespace:\"longhorn-system\", Name:\"pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36\", UID:\"4eee857d-
7d9b-4d77-bb06-1de7b2c6d596\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"417225\", FieldPath:\"\"}): type: 'Normal' reason: 'Start' Starts pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b
3ba7a36"
time="2021-10-02T16:07:54Z" level=debug msg="Instance process pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 had been created, need to wait for instance manager update"
time="2021-10-02T16:07:54Z" level=warning msg="Instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/rancher-m
irrored-longhornio-longhorn-engine-v1.1.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/rancher-mirrored-longhornio-longhorn-engine-v1.1.1/longhorn: no such file or directory"
time="2021-10-02T16:07:54Z" level=debug msg="Instance handler updated instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 state, old state stopped, new state error"
time="2021-10-02T16:07:54Z" level=warning msg="Instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 crashed on Instance Manager instance-manager-r-9687b1aa at k8srv03, try to get log"
time="2021-10-02T16:07:54Z" level=warning msg="Error syncing Longhorn volume longhorn-system/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912" controller=longhorn-volume error="fail to sync longhorn-syst
em/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: fail to reconcile volume state for pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: no healthy or scheduled replica for starting" node=k8srv03
time="2021-10-02T16:07:54Z" level=warning msg="Error syncing Longhorn volume longhorn-system/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912" controller=longhorn-volume error="fail to sync longhorn-syst
em/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: fail to reconcile volume state for pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: no healthy or scheduled replica for starting" node=k8srv03
E1002 16:07:54.659345       1 volume_controller.go:202] fail to sync longhorn-system/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: fail to reconcile volume state for pvc-5daba64c-bec3-47ae-9d01-32acf
d0ab912: no healthy or scheduled replica for starting
time="2021-10-02T16:07:54Z" level=warning msg="Dropping Longhorn volume longhorn-system/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912 out of the queue" controller=longhorn-volume error="fail to sync l
onghorn-system/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: fail to reconcile volume state for pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: no healthy or scheduled replica for starting" node=k8srv03
time="2021-10-02T16:07:54Z" level=warning msg="Instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/rancher-m
irrored-longhornio-longhorn-engine-v1.1.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/rancher-mirrored-longhornio-longhorn-engine-v1.1.1/longhorn: no such file or directory"
time="2021-10-02T16:07:54Z" level=warning msg="Instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 crashed on Instance Manager instance-manager-r-9687b1aa at k8srv03, try to get log"
time="2021-10-02T16:08:21Z" level=warning msg="Instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/rancher-m
irrored-longhornio-longhorn-engine-v1.1.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/rancher-mirrored-longhornio-longhorn-engine-v1.1.1/longhorn: no such file or directory"
time="2021-10-02T16:08:21Z" level=warning msg="Instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 crashed on Instance Manager instance-manager-r-9687b1aa at k8srv03, try to get log"
time="2021-10-02T16:08:21Z" level=warning msg="Instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/rancher-m
irrored-longhornio-longhorn-engine-v1.1.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/rancher-mirrored-longhornio-longhorn-engine-v1.1.1/longhorn: no such file or directory"
time="2021-10-02T16:08:21Z" level=warning msg="Instance pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912-r-b3ba7a36 crashed on Instance Manager instance-manager-r-9687b1aa at k8srv03, try to get log"
time="2021-10-02T16:08:21Z" level=warning msg="Error syncing Longhorn volume longhorn-system/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912" controller=longhorn-volume error="fail to sync longhorn-syst
em/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: fail to reconcile volume state for pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: no healthy or scheduled replica for starting" node=k8srv03
E1002 16:08:21.131165       1 volume_controller.go:202] fail to sync longhorn-system/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: fail to reconcile volume state for pvc-5daba64c-bec3-47ae-9d01-32acf
d0ab912: no healthy or scheduled replica for starting
time="2021-10-02T16:08:21Z" level=warning msg="Dropping Longhorn volume longhorn-system/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912 out of the queue" controller=longhorn-volume error="fail to sync l
onghorn-system/pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: fail to reconcile volume state for pvc-5daba64c-bec3-47ae-9d01-32acfd0ab912: no healthy or scheduled replica for starting" node=k8srv03

When I set up longhorn, I set the # of replicas to 2 and I have 4 nodes in my cluster, so there should be enough nodes for the 2 replicas. I have also set the soft anti-affinity to true just to make sure this isn't the issue.
Any idea why it is not attaching?
Thanks a lot in advance,
B.

Alright, so I have made a few changes.
First of all, my /var/lib/longhorn was initially a link to /srv/var/lib/longhorn, but docker can't mount links, so I instead have been using the /srv/var/lib/longhorn directory directly, so I uninstalled longhorn completely.
I then reinstalled it using the kubectl command. Here is the part I changed in my longhorn.yaml file to point to the /srv/var/lib/longhorn directory:
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: longhorn-default-setting
  namespace: longhorn-system
data:
  default-setting.yaml: |-
    backup-target:
    backup-target-credential-secret:
    allow-recurring-job-while-volume-detached:
    create-default-disk-labeled-nodes:
    default-data-path: /srv/var/lib/longhorn
    replica-soft-anti-affinity: true
    replica-auto-balance:
    storage-over-provisioning-percentage:
    storage-minimal-available-percentage:
    upgrade-checker:
    default-replica-count: 2
    default-data-locality:
    default-longhorn-static-storage-class:
    backupstore-poll-interval:
    taint-toleration:
    system-managed-components-node-selector:
    priority-class:
    auto-salvage:
    auto-delete-pod-when-volume-detached-unexpectedly:
    disable-scheduling-on-cordoned-node:
    replica-zone-soft-anti-affinity:
    node-down-pod-deletion-policy:
    allow-node-drain-with-last-healthy-replica:
    mkfs-ext4-parameters:
    disable-replica-rebuild:
    replica-replenishment-wait-interval:
    concurrent-replica-rebuild-per-node-limit:
    disable-revision-counter:
    system-managed-pods-image-pull-policy:
    allow-volume-creation-with-degraded-availability:
    auto-cleanup-system-generated-snapshot:
    concurrent-automatic-engine-upgrade-per-node-limit:
    backing-image-cleanup-wait-interval:
    backing-image-recovery-wait-interval:
    guaranteed-engine-manager-cpu:
    guaranteed-replica-manager-cpu:
---
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  labels:
    app: longhorn-manager
  name: longhorn-manager
  namespace: longhorn-system
spec:
  selector:
    matchLabels:
      app: longhorn-manager
  template:
    metadata:
      labels:
        app: longhorn-manager
    spec:
      containers:
      - name: longhorn-manager
        image: longhornio/longhorn-manager:v1.2.1
        imagePullPolicy: IfNotPresent
        securityContext:
          privileged: true
        command:
        - longhorn-manager
        - -d
        - daemon
        - --engine-image
        - longhornio/longhorn-engine:v1.2.1
        - --instance-manager-image
        - longhornio/longhorn-instance-manager:v1_20210731
        - --share-manager-image
        - longhornio/longhorn-share-manager:v1_20210914
        - --backing-image-manager-image
        - longhornio/backing-image-manager:v2_20210820
        - --manager-image
        - longhornio/longhorn-manager:v1.2.1
        - --service-account
        - longhorn-service-account
        ports:
        - containerPort: 9500
          name: manager
        readinessProbe:
          tcpSocket:
            port: 9500
        volumeMounts:
        - name: dev
          mountPath: /host/dev/
        - name: proc
          mountPath: /host/proc/
        - name: longhorn
          mountPath: /srv/var/lib/longhorn/
          mountPropagation: Bidirectional
        - name: longhorn-default-setting
          mountPath: /srv/var/lib/longhorn-setting/
        env:
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: POD_IP
          valueFrom:
            fieldRef:
              fieldPath: status.podIP
        - name: NODE_NAME
          valueFrom:
            fieldRef:
              fieldPath: spec.nodeName
        # Should be: mount path of the volume longhorn-default-setting + the key of the configmap data in 04-default-setting.yaml
        - name: DEFAULT_SETTING_PATH
          value: /srv/var/lib/longhorn-setting/default-setting.yaml
      volumes:
      - name: dev
        hostPath:
          path: /dev/
      - name: proc
        hostPath:
          path: /proc/
      - name: longhorn
        hostPath:
          path: /srv/var/lib/longhorn/
      - name: longhorn-default-setting
        configMap:
          name: longhorn-default-setting
#      imagePullSecrets:
#      - name: ""
#      priorityClassName:
#      tolerations:
#      - key: "key"
#        operator: "Equal"
#        value: "value"
#        effect: "NoSchedule"
#      nodeSelector:
#        label-key1: "label-value1"
#        label-key2: "label-value2"
      serviceAccountName: longhorn-service-account
  updateStrategy:
    rollingUpdate:
      maxUnavailable: "100%"

These were the only area that were pointing to the default /var/lib/longhorn. I then proceeded to deploy longhorn using kubectl apply -f ./longhorn.yaml -n longhorn-system and everything deployed fine.
Then I created a PVC through Rancher and it created fine, but when I deployed a pod that attached to that PVC, it errored out. Looking at the logs of the longhorn manager for the node that had own of the replicas for the PVC, this is what I got:
2021/10/07 20:26:09 proto: duplicate proto type registered: VersionResponse
time="2021-10-07T20:26:09Z" level=info msg="Start overwriting built-in settings with customized values"
W1007 20:26:09.942894       1 client_config.go:552] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2021-10-07T20:26:09Z" level=info msg="cannot list the content of the src directory /var/lib/rancher/longhorn/engine-binaries for the copy, will do nothing: Failed to execute: nsenter [--mount=/host/proc/1/ns/mnt --net=/host/proc/1/ns/net bash -c ls /var/lib/rancher/longhorn/engine-binaries/*], output , stderr, ls: cannot access '/var/lib/rancher/longhorn/engine-binaries/*': No such file or directory\n, error exit status 2"
I1007 20:26:09.985739       1 leaderelection.go:242] attempting to acquire leader lease  longhorn-system/longhorn-manager-upgrade-lock...
time="2021-10-07T20:26:10Z" level=info msg="New upgrade leader elected: k8srv04"
I1007 20:26:16.428745       1 leaderelection.go:252] successfully acquired lease longhorn-system/longhorn-manager-upgrade-lock
time="2021-10-07T20:26:16Z" level=info msg="Start upgrading"
time="2021-10-07T20:26:16Z" level=info msg="No API version upgrade is needed"
time="2021-10-07T20:26:18Z" level=info msg="upgrade from v1.1.0 to v1.2.0: Starting storageClass recurring job translation" namespace=longhorn-system translate=storage-class-recurring-jobs
time="2021-10-07T20:26:18Z" level=info msg="upgrade from v1.1.0 to v1.2.0: Finished storageClass recurring job translation" namespace=longhorn-system translate=storage-class-recurring-jobs
time="2021-10-07T20:26:18Z" level=info msg="upgrade from v1.1.0 to v1.2.0: Starting volume recurring job translation" namespace=longhorn-system translate=volume-recurring-jobs
time="2021-10-07T20:26:18Z" level=debug msg="upgrade from v1.1.0 to v1.2.0: Found 0 recurring job" action=create-recurringJob-CRs namespace=longhorn-system translate=volume-recurring-jobs
time="2021-10-07T20:26:18Z" level=info msg="upgrade from v1.1.0 to v1.2.0: Finished volume recurring job translation" namespace=longhorn-system translate=volume-recurring-jobs
time="2021-10-07T20:26:18Z" level=info msg="upgrade from v1.1.0 to v1.2.0: Starting volume cron job cleanup" action=cleanup-applied-volume-cron-jobs namespace=longhorn-system
time="2021-10-07T20:26:18Z" level=info msg="upgrade from v1.1.0 to v1.2.0: Finished volume cron job cleanup" action=cleanup-applied-volume-cron-jobs namespace=longhorn-system
time="2021-10-07T20:26:24Z" level=info msg="Finish upgrading"
time="2021-10-07T20:26:24Z" level=info msg="Upgrade leader lost: k8srv02"
W1007 20:26:24.216685       1 client_config.go:552] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I1007 20:26:24.232198       1 shared_informer.go:223] Waiting for caches to sync for longhorn datastore
E1007 20:26:24.347927       1 kubernetes_node_controller.go:232] couldn't get kubernetes node k8srv02: node "k8srv02" not found
I1007 20:26:26.733541       1 shared_informer.go:230] Caches are synced for longhorn datastore
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn replica controller" controller=longhorn-replica node=k8srv02
I1007 20:26:26.733767       1 shared_informer.go:223] Waiting for caches to sync for longhorn replicas
I1007 20:26:26.733792       1 shared_informer.go:230] Caches are synced for longhorn replicas
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn volume controller" controller=longhorn-volume node=k8srv02
I1007 20:26:26.733856       1 shared_informer.go:223] Waiting for caches to sync for longhorn engines
I1007 20:26:26.733876       1 shared_informer.go:230] Caches are synced for longhorn engines
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn Backup controller" controller=longhorn-backup node=k8srv02
I1007 20:26:26.733912       1 shared_informer.go:223] Waiting for caches to sync for longhorn-backup
W1007 20:26:26.733919       1 client_config.go:552] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn Engine Image controller"
I1007 20:26:26.733972       1 shared_informer.go:223] Waiting for caches to sync for longhorn engine images
I1007 20:26:26.733992       1 shared_informer.go:230] Caches are synced for longhorn engine images
time="2021-10-07T20:26:26Z" level=info msg="Starting Longhorn backing image data source controller"
I1007 20:26:26.734017       1 shared_informer.go:223] Waiting for caches to sync for longhorn backing image data source
I1007 20:26:26.734035       1 shared_informer.go:230] Caches are synced for longhorn backing image data source
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn Backup Target controller" controller=longhorn-backup-target node=k8srv02
I1007 20:26:26.734134       1 shared_informer.go:223] Waiting for caches to sync for longhorn-backup-target
I1007 20:26:26.734151       1 shared_informer.go:230] Caches are synced for longhorn-backup-target
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn Backup Volume controller" controller=longhorn-backup-volume node=k8srv02
I1007 20:26:26.734503       1 shared_informer.go:223] Waiting for caches to sync for longhorn-backup-volume
time="2021-10-07T20:26:26Z" level=info msg="Starting Longhorn instance manager controller"
I1007 20:26:26.734549       1 shared_informer.go:230] Caches are synced for longhorn-backup-volume
time="2021-10-07T20:26:26Z" level=debug msg="CheckEngineImageReadiness: nodes [k8srv02] don't have the engine image longhornio/longhorn-engine:v1.2.1"
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn engine controller" controller=longhorn-engine node=k8srv02
I1007 20:26:26.734665       1 shared_informer.go:223] Waiting for caches to sync for longhorn engines
I1007 20:26:26.734685       1 shared_informer.go:230] Caches are synced for longhorn engines
time="2021-10-07T20:26:26Z" level=info msg="Starting Longhorn backing image manager controller"
I1007 20:26:26.734773       1 shared_informer.go:223] Waiting for caches to sync for longhorn backing image manager
I1007 20:26:26.734792       1 shared_informer.go:230] Caches are synced for longhorn backing image manager
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn node controller"
I1007 20:26:26.734562       1 shared_informer.go:223] Waiting for caches to sync for longhorn instance manager
I1007 20:26:26.734898       1 shared_informer.go:223] Waiting for caches to sync for longhorn node
I1007 20:26:26.734905       1 shared_informer.go:230] Caches are synced for longhorn instance manager
I1007 20:26:26.734915       1 shared_informer.go:230] Caches are synced for longhorn node
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn share manager controller" controller=longhorn-share-manager node=k8srv02
I1007 20:26:26.735333       1 shared_informer.go:223] Waiting for caches to sync for longhorn-share-manager-controller
I1007 20:26:26.735360       1 shared_informer.go:230] Caches are synced for longhorn-share-manager-controller
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn Setting controller" controller=longhorn-setting node=k8srv02
I1007 20:26:26.735605       1 shared_informer.go:223] Waiting for caches to sync for longhorn settings
I1007 20:26:26.735627       1 shared_informer.go:230] Caches are synced for longhorn settings
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn Backing Image controller"
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn websocket controller" controller=longhorn-websocket node=k8srv02
I1007 20:26:26.736295       1 shared_informer.go:223] Waiting for caches to sync for longhorn websocket
I1007 20:26:26.736332       1 shared_informer.go:230] Caches are synced for longhorn websocket
time="2021-10-07T20:26:26Z" level=info msg="Starting Longhorn Recurring Job controller"
I1007 20:26:26.736370       1 shared_informer.go:223] Waiting for caches to sync for longhorn recurring jobs
I1007 20:26:26.736386       1 shared_informer.go:230] Caches are synced for longhorn recurring jobs
I1007 20:26:26.736394       1 shared_informer.go:223] Waiting for caches to sync for longhorn backing images
I1007 20:26:26.736413       1 shared_informer.go:230] Caches are synced for longhorn backing images
time="2021-10-07T20:26:26Z" level=info msg="Start kubernetes controller"
I1007 20:26:26.736514       1 shared_informer.go:223] Waiting for caches to sync for kubernetes
I1007 20:26:26.736533       1 shared_informer.go:230] Caches are synced for kubernetes
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn Kubernetes secret controller" controller=longhorn-kubernetes-secret-controller node=k8srv02
I1007 20:26:26.736651       1 shared_informer.go:223] Waiting for caches to sync for longhorn-kubernetes-secret-controller
I1007 20:26:26.736671       1 shared_informer.go:230] Caches are synced for longhorn-kubernetes-secret-controller
I1007 20:26:26.733929       1 shared_informer.go:230] Caches are synced for longhorn-backup
time="2021-10-07T20:26:26Z" level=info msg=Start controller=longhorn-kubernetes-configmap-controller node=k8srv02
I1007 20:26:26.737040       1 shared_informer.go:223] Waiting for caches to sync for longhorn-kubernetes-configmap-controller
I1007 20:26:26.737061       1 shared_informer.go:230] Caches are synced for longhorn-kubernetes-configmap-controller
time="2021-10-07T20:26:26Z" level=info msg="Start longhorn-kubernetes-pod-controller" controller=longhorn-kubernetes-pod node=k8srv02
I1007 20:26:26.737098       1 shared_informer.go:223] Waiting for caches to sync for longhorn-kubernetes-pod-controller
I1007 20:26:26.737117       1 shared_informer.go:230] Caches are synced for longhorn-kubernetes-pod-controller
time="2021-10-07T20:26:26Z" level=info msg="Start Longhorn Kubernetes node controller"
I1007 20:26:26.737222       1 shared_informer.go:223] Waiting for caches to sync for longhorn kubernetes node
I1007 20:26:26.737241       1 shared_informer.go:230] Caches are synced for longhorn kubernetes node
time="2021-10-07T20:26:27Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"k8srv02\", UID:\"bb6c801a-2bed-4d21-83be-d8ee83ae726f\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"6232082\", FieldPath:\"\"}): type: 'Warning' reason: 'Ready' Node k8srv02 is down: the manager pod longhorn-manager-twmsm is not running"
time="2021-10-07T20:26:27Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"k8srv02\", UID:\"bb6c801a-2bed-4d21-83be-d8ee83ae726f\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"6232082\", FieldPath:\"\"}): type: 'Normal' reason: 'Schedulable' "
time="2021-10-07T20:26:27Z" level=info msg="Listening on <IP_ADDRESS>:9500" node=k8srv02
time="2021-10-07T20:26:27Z" level=info msg="Debug Server listening on <IP_ADDRESS>:6060" node=k8srv02
time="2021-10-07T20:26:27Z" level=debug msg="Prepare to create default instance manager instance-manager-e-937932be, node: k8srv02, default instance manager image: longhornio/longhorn-instance-manager:v1_20210731, type: engine"
time="2021-10-07T20:26:27Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"k8srv02\", UID:\"bb6c801a-2bed-4d21-83be-d8ee83ae726f\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"6232082\", FieldPath:\"\"}): type: 'Normal' reason: 'Ready' Disk default-disk-8fd9a35382fe84e7(/srv/var/lib/longhorn) on node k8srv02 is ready"
time="2021-10-07T20:26:27Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"k8srv02\", UID:\"bb6c801a-2bed-4d21-83be-d8ee83ae726f\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"6232082\", FieldPath:\"\"}): type: 'Normal' reason: 'Schedulable' Disk default-disk-8fd9a35382fe84e7(/srv/var/lib/longhorn) on node k8srv02 is schedulable"
time="2021-10-07T20:26:27Z" level=debug msg="Prepare to create default instance manager instance-manager-r-25faebbe, node: k8srv02, default instance manager image: longhornio/longhorn-instance-manager:v1_20210731, type: replica"
time="2021-10-07T20:26:27Z" level=debug msg="Instance Manager Controller k8srv02 picked up instance-manager-e-937932be" controller=longhorn-instance-manager instanceManager=instance-manager-e-937932be node=k8srv02 nodeID=k8srv02
time="2021-10-07T20:26:27Z" level=info msg="Created instance manager pod instance-manager-e-937932be for instance manager instance-manager-e-937932be"
time="2021-10-07T20:26:28Z" level=debug msg="Instance Manager Controller k8srv02 picked up instance-manager-r-25faebbe" controller=longhorn-instance-manager instanceManager=instance-manager-r-25faebbe node=k8srv02 nodeID=k8srv02
time="2021-10-07T20:26:28Z" level=info msg="Created instance manager pod instance-manager-r-25faebbe for instance manager instance-manager-r-25faebbe"
time="2021-10-07T20:26:28Z" level=debug msg="Requeue longhorn-system/k8srv02 due to conflict: Operation cannot be fulfilled on nodes.longhorn.io \"k8srv02\": the object has been modified; please apply your changes to the latest version and try again"
time="2021-10-07T20:26:28Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"k8srv02\", UID:\"bb6c801a-2bed-4d21-83be-d8ee83ae726f\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"6232106\", FieldPath:\"\"}): type: 'Normal' reason: 'Ready' Disk default-disk-8fd9a35382fe84e7(/srv/var/lib/longhorn) on node k8srv02 is ready"
time="2021-10-07T20:26:28Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"k8srv02\", UID:\"bb6c801a-2bed-4d21-83be-d8ee83ae726f\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"6232106\", FieldPath:\"\"}): type: 'Normal' reason: 'Schedulable' Disk default-disk-8fd9a35382fe84e7(/srv/var/lib/longhorn) on node k8srv02 is schedulable"
time="2021-10-07T20:26:28Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"k8srv04\", UID:\"8d527dfc-5e37-4062-a772-113266ed991b\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"6231995\", FieldPath:\"\"}): type: 'Normal' reason: 'Ready' Node k8srv04 is ready"
time="2021-10-07T20:26:29Z" level=debug msg="Requeue longhorn-system/k8srv04 due to conflict: Operation cannot be fulfilled on nodes.longhorn.io \"k8srv04\": the object has been modified; please apply your changes to the latest version and try again"
time="2021-10-07T20:26:34Z" level=debug msg="Start monitoring instance manager instance-manager-e-937932be" controller=longhorn-instance-manager instance manager=instance-manager-e-937932be node=k8srv02
time="2021-10-07T20:26:36Z" level=debug msg="Start monitoring instance manager instance-manager-r-25faebbe" controller=longhorn-instance-manager instance manager=instance-manager-r-25faebbe node=k8srv02
time="2021-10-07T20:28:21Z" level=info msg="Engine got new owner k8srv02" controller=longhorn-engine engine=pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-e-ea18044b node=k8srv02
time="2021-10-07T20:28:21Z" level=debug msg="Instance handler updated instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-e-ea18044b state, old state , new state stopped"
time="2021-10-07T20:28:21Z" level=debug msg="Replica controller picked up" controller=longhorn-replica controllerID=k8srv02 dataPath= node=k8srv02 nodeID= ownerID= replica=pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-61609137
time="2021-10-07T20:28:21Z" level=debug msg="Instance handler updated instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-61609137 state, old state , new state stopped"
time="2021-10-07T20:28:22Z" level=debug msg="Replica controller picked up" controller=longhorn-replica controllerID=k8srv02 dataPath= node=k8srv02 nodeID=k8srv02 ownerID=k8srv01 replica=pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40
time="2021-10-07T20:32:40Z" level=debug msg="Prepare to create instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
time="2021-10-07T20:32:40Z" level=info msg="Event(v1.ObjectReference{Kind:\"Replica\", Namespace:\"longhorn-system\", Name:\"pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40\", UID:\"2bcfed7d-dc8f-41bc-8d11-abe084e248de\", APIVersion:\"longhorn.io/v1beta1\", ResourceVersion:\"6237284\", FieldPath:\"\"}): type: 'Normal' reason: 'Start' Starts pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
time="2021-10-07T20:32:40Z" level=debug msg="Instance process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 had been created, need to wait for instance manager update"
time="2021-10-07T20:32:40Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
time="2021-10-07T20:32:40Z" level=debug msg="Instance handler updated instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 state, old state stopped, new state error"
time="2021-10-07T20:32:40Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 crashed on Instance Manager instance-manager-r-25faebbe at k8srv02, try to get log"
time="2021-10-07T20:32:40Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
time="2021-10-07T20:32:40Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 crashed on Instance Manager instance-manager-r-25faebbe at k8srv02, try to get log"
time="2021-10-07T20:32:54Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
time="2021-10-07T20:32:54Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 crashed on Instance Manager instance-manager-r-25faebbe at k8srv02, try to get log"
time="2021-10-07T20:32:54Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
time="2021-10-07T20:32:54Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 crashed on Instance Manager instance-manager-r-25faebbe at k8srv02, try to get log"
time="2021-10-07T20:33:24Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
time="2021-10-07T20:33:24Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 crashed on Instance Manager instance-manager-r-25faebbe at k8srv02, try to get log"
time="2021-10-07T20:33:24Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
time="2021-10-07T20:33:24Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 crashed on Instance Manager instance-manager-r-25faebbe at k8srv02, try to get log"
time="2021-10-07T20:33:54Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
time="2021-10-07T20:33:54Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 crashed on Instance Manager instance-manager-r-25faebbe at k8srv02, try to get log"
time="2021-10-07T20:33:54Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
time="2021-10-07T20:33:54Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 crashed on Instance Manager instance-manager-r-25faebbe at k8srv02, try to get log"
time="2021-10-07T20:34:24Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
time="2021-10-07T20:34:24Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 crashed on Instance Manager instance-manager-r-25faebbe at k8srv02, try to get log"
time="2021-10-07T20:34:24Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 is state error, error message: exec: \"/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn\": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
time="2021-10-07T20:34:24Z" level=warning msg="Instance pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 crashed on Instance Manager instance-manager-r-25faebbe at k8srv02, try to get log"
``` and this is the log from the `instance-manager-r` on the same node:

time="2021-10-07T20:26:33Z" level=info msg="Storing process logs at path: /var/log/instances"
[longhorn-instance-manager] time="2021-10-07T20:26:33Z" level=info msg="Instance Manager listening to <IP_ADDRESS>:8500"
[longhorn-instance-manager] time="2021-10-07T20:26:36Z" level=debug msg="started new process manager update watch"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=info msg="Process Manager: prepare to create process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=error msg="Process Manager: failed to init new process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40 error exec: "/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=debug msg="Process update: pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40: state error: Error: exec: "/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=debug msg="Process update: pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40: state error: Error: exec: "/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=debug msg="Process update: pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40: state error: Error: exec: "/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=debug msg="Process update: pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40: state error: Error: exec: "/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=debug msg="Process update: pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40: state error: Error: exec: "/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:32:40Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:32:54Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:32:54Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:32:54Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:32:54Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:33:24Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:33:24Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:33:24Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:33:24Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:33:40Z" level=debug msg="Process update: pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40: state error: Error: exec: "/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
[longhorn-instance-manager] time="2021-10-07T20:33:54Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:33:54Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:33:54Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:33:54Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:34:24Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:34:24Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:34:24Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:34:24Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:34:40Z" level=debug msg="Process update: pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40: state error: Error: exec: "/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
[longhorn-instance-manager] time="2021-10-07T20:34:54Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:34:54Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:34:54Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:34:54Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:35:24Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:35:24Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:35:24Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:35:24Z" level=debug msg="Process Manager: got logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:35:40Z" level=debug msg="Process Manager: prepare to delete process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:35:40Z" level=debug msg="Process update: pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40: state error: Error: exec: "/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
[longhorn-instance-manager] time="2021-10-07T20:35:40Z" level=debug msg="Process Manager: deleted process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:35:40Z" level=info msg="Process Manager: successfully unregistered process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
[longhorn-instance-manager] time="2021-10-07T20:35:40Z" level=debug msg="Process update: pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40: state error: Error: exec: "/host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn": stat /host/var/lib/longhorn/engine-binaries/longhornio-longhorn-engine-v1.2.1/longhorn: no such file or directory"
[longhorn-instance-manager] time="2021-10-07T20:35:40Z" level=debug msg="Process Manager: start getting logs for process pvc-e5a65bc2-a00e-4845-86cc-3a83fe334e56-r-0b191f40"
Why is it still referencing `/var/lib/longhorn` when it is clear that in the yaml file used to deploy it, I set the `default-data-path` to `/srv/var/lib/longhorn`?

As an aside, I initially deployed longhorn using the helm chart thinking it will be easier, but ran into the same issue, hence why I decided to go the `kubectl` route as it gave me greater granularity in terms of setting change.

I have uninstalled and reinstalled Longhorn with the mount point being in /var/lib/longhorn and everything is working fine. I still think that not being able to change the default-data-path is an issue and should be remedied.


Vite + Vue app throws error trying to access service-worker on fresh install

Describe the bug

When initializing a fresh Vue app with Vite, I keep getting an error when running the dev server. This seems to be a 2.3.0 regression as it doesn't happen with 2.2.4.
[vite] Internal server error: The request url "/service-worker.js" is outside of vite dev server root "/Users/mcbridem/src".
      For security concerns, accessing files outside of workspace root is restricted since Vite v2.3.x.
      Refer to docs https://vitejs.dev/config/#server-fsserveroot for configurations and more details.

Reproduction

Initialize a brand new project with npm init @vitejs/app
Choose Vue as the framework
cd into the directory and run npm install
run npm run dev
See the error above

System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 605.43 MB / 16.00 GB
    Shell: 3.2.2 - /usr/local/bin/fish
  Binaries:
    Node: 14.16.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.10.0 - /usr/local/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 90.0.4430.85
    Edge: 89.0.774.76
    Firefox: 88.0
    Firefox Developer Edition: 84.0
    Safari: 14.1
  npmPackages:
    @vitejs/plugin-vue: ^1.2.2 => 1.2.2
    vite: ^2.3.0 => 2.3.0

Used package manager:  yarn
Logs

[vite] Internal server error: The request url "/service-worker.js" is outside of vite dev server root "/Users/mcbridem/src".
      For security concerns, accessing files outside of workspace root is restricted since Vite v2.3.x.
      Refer to docs https://vitejs.dev/config/#server-fsserveroot for configurations and more details.

Before submitting the issue, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Provide a description in this issue that describes the bug.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

Can the docs help you here? https://vitejs.dev/config/#server-fsserve-root

Yeah I tried changing the root but I still got the error. For now I downgraded to 2.2.4 and it's working again.

@mikemcbride in v2.3.2, fsServe.root has been marked as experimental and disabled by default. You should be able to upgrade to it.

That worked, thanks!


raftstore: not always update pending_cross_snap

What have you changed? (mandatory)
pending_cross_snap is updated when a new message is received or a snapshot is received. However, need_gc_merge assumes an updated field indicates a snapshot is received. This can lead to wrong decision which may ruin merge process that one peer destroy itself, but the other peer want to merge it.
This PR fixes it by checking the range is covered by exist regions to decide whether updating pending_cross_snap when a new message is received. If that, means that the region may generated by some kinds of split and merge by catching logs. So it is no need to accept snapshot, namely, do not need to update pending_cross_snap.
What are the type of the changes? (mandatory)

Bug fix (non-breaking change which fixes an issue)

How has this PR been tested? (mandatory)
unit-test
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
No
Does this PR affect tidb-ansible update? (mandatory)
No

PTAL @BusyJay

PTAL @BusyJay @overvenus @siddontang

PTAL

PTAL @overvenus @siddontang @zhangjinpeng1987


Documentation: How to setup?

Vscode extension newbie here. I've added the extension's exposed fields to my settings.json:
{
    "workbench.colorTheme": "Solarized Light",
    "git.autofetch": true,
    "extensions.ignoreRecommendations": true,
     ...
    "autoDarkMode.lightTheme": "Solarized Light",
    "autoDarkMode.darkTheme": "Solarized Dark"
}

What am I missing?
Suggestion: include a sentence about where these fields can be set
Suggestion: include a sentence about possible values for these fields

As indicated in the readme, this is supported natively in VS Code now and I would recommend using that instead:
https://code.visualstudio.com/updates/v1_42#_auto-switch-theme-based-on-os-color-scheme

My bad, cheers!


CB-3791 Revert to passing full db usernames to CM

One change in the prior commit for CB-3791 was having Cloudbreak
configure Cloudera Manager with only the bare usernames for database
connections, instead of the "full" username@short-hostname format needed
for connections to Azure-managed databases. This change undoes that
work, so that once again the entire username is configured in Cloudera
Manager.
This still does not allow Cloudera Manager to support clusters backed
by Azure databases, because of OPSAPS-53099. However, once that CM work
is done, Hive metastore table creation should succeed, and perhaps
overall cluster creation will as well.
Other previous changes in CB-3791 to username handling are preserved.
This change only affects how Cloudera Manager is configured.

Follow-up to #6479.


Fixed a few typos on Get-ADKeyCredential doc

Command is Get-ADKeyCredential but examples still use Get-KeyCredential.

Hi @cdanger , thanks! I agree that it is against the best practices to use aliases in production PS scripts.


Allow taskqueue instantiation with any boto3 client keywords

Translate legacy keyrword 'region' to 'region_name'

I needed this for local testing using a dockerized sqs queue, where the endpoint_url to boto3.client is required and credentials are not necessary.
https://hub.docker.com/r/roribio16/alpine-sqs/

This is great! Can you add some documentation about how to use the new feature?

Added to the README.
I also cleaned it up, so the AWS specific stuff is not part of the higher-level taskqueue interface.

Test failures are related to parallel FileQueue inserts and do not affect the contents of this PR.


Added ability fo fully bootstrap Code manager

This adds the ability to properly bootstrap code manager by making the following major changes:

Added the ability to specify a private key

Added the functionality to sync this private key to the masters if it's local so that they are fully ready to deploy code

In order to get this working we needed to improve a few things, mostly around how pe.conf is generated:

Move pe.conf  from templates to fully dynamic config files
Added $pe_conf_data to allow users to specify any pe.conf settings without requiring template changes
$pe_conf_data also allows the hardcoded settings like puppet_enterprise::profile::puppetdb::database_host to be overridden if required for some reason

@dylanratcliffe I refactored these commits a little to:

Make it clearer what was being changed in each commit, so that individual proposals were easier to separate and evaluate
Minor implementation cleanup
Suggested simplification of the r10k_private_key portion

Please take a look and let me know what you think of the adjustments. Happy to chat real-time if you want! Just ping me on Slack. :)

@dylanratcliffe updated with the changes we discussed. Have not tested this code yet but logically it should be complete. Thoughts?


Resolution Verifier (Protocol Client)

Resolution Verifier (used by VDR) should be provided 'versioned' Protocol Client instead of creating one.
TODO: Review logic

No need to provide implementation of 'versioned' protocol client at this point, the code already supports setting version ids(implementation has to be support provided versions) . In case that client needs different handling they can create their own resolution verifier.


Add an Example using Julia's Genie.jl framework

I've created a demo using Julia lang's Genie.jl framework to build a webapp using Docker spaces! I would love to add this to the list of examples, as it is quite finicky to figure out how ports need to be exposed and how the default CMD is leveraged. I think this would be useful for those looking to grow the Julia ecosystem and support on the Huggingface platform :)

Yes definitely! Where should I put this specific write up?

maybe in spaces-docker-julia-genie.md file? (we can always rename later if needed)

in the meantime, i'm deploying this PR :) Thanks a lot!

see also #585 for a similar approach! (documenting a new SDK for Spaces)

Amazing! Thanks for the reference :)


Locale request: fa-IR

Which locale do you wish to add?
fa-IR
Maintainer
Sanity will bootstrap and keep the locale updated using AI. We would like human contributors to help maintain the locales by improving them and/or reviewing pull requests from the AI and from other contributors as they come in. Check the box below if you want to be added as a maintainer of this locale. As a maintainer you will be automatically added as reviewer to future PRs that improve it.
If you are not the author of this issue, but would still like to be added as a maintainer, please add a comment to the thread.

[ ] I want to be added as maintainer

I can help in RTL styling.


cleaned up integration-cli/docker_api_images_test.go

As part of "Proposal: use of checkers on Integration test #16756"

@ZJaffee As stated by the build you need to format the modified files, with gofmt -s -w

/ping @ZJaffee

I'm very sorry but I'm going to close this PR until the errors are resolved. Please, feel free to send it again after testing that every test still works and the code is valid. make test and make validate are your friends.
As a rule of thumb, before opening all your PRs again, it will be easier to get them merged if you focus in one at a time, that way reviewers don't need to point the same errors over several changes.


SparkRestClient.scala fetchData() throws java.lang.IllegalArgumentException for yarn-client Spark jobs

Spark jobs run under yarn-client have no attemptId (see https://issues.apache.org/jira/browse/SPARK-15923). The missing attemptId causes the following error to occur in SparkRestClient.scala fetchData:
12-19-2016 10:50:35 ERROR [dr-el-executor-thread-0] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Failed fetching data for
java.lang.IllegalArgumentException: Spark REST API has no attempt information
at com.linkedin.drelephant.spark.fetchers.SparkRestClient$stateMachine$4$1.apply(SparkRestClient.scala:91)
at com.linkedin.drelephant.spark.fetchers.SparkRestClient$stateMachine$4$1.apply$mcV$sp(SparkRestClient.scala:76)
at com.linkedin.drelephant.spark.fetchers.SparkRestClient$stateMachine$4$1.apply(SparkRestClient.scala:76)
at com.linkedin.drelephant.spark.fetchers.SparkRestClient$stateMachine$4$1.apply(SparkRestClient.scala:76)
at scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
at scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
at scala.concurrent.impl.ExecutionContextImpl$$anon$3.exec(ExecutionContextImpl.scala:107)
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

I met the same problem,even after i fix the declaration of ApplicationAttemptInfo to
class ApplicationAttemptInfo(   val attemptId: Option[String] = Some("Hello"),   val startTime: Date,   val endTime: Date,   val lastUpdated: Date,   val duration: Int,   val startTimeEpoch: Long,   val endTimeEpoch: Long,   val lastUpdatedEpoch: Long,   val sparkUser: String,   val completed: Boolean = false)
hadoop 2.7.3  spark 2.0.2 yarn-client mode
but the function of fetchData code is like
val lastAttemptId = applicationInfo.attempts.maxBy { _.startTime }.attemptId
      lastAttemptId match {
        case Some(attemptId) => {
          val attemptTarget = appTarget.path(attemptId)
          val futureJobDatas = async { getJobDatas(attemptTarget) }
          val futureStageDatas = async { getStageDatas(attemptTarget) }
          val futureExecutorSummaries = async { getExecutorSummaries(attemptTarget) }
          SparkRestDerivedData(
            applicationInfo,
            await(futureJobDatas),
            await(futureStageDatas),
            await(futureExecutorSummaries)
          )
        }
        case None => throw new IllegalArgumentException("Spark REST API has no attempt information")
      }

Worked around it by ignoring yarn-client jobs as follows:
Modified SparkRestClient.scala to read:
```

val applicationInfo = getApplicationInfo(appTarget)
// Limit scope of async.
async {
val lastAttemptId = applicationInfo.attempts.maxBy {
_.startTime
}.attemptId
lastAttemptId match {
case Some(attemptId) => {
val attemptTarget = appTarget.path(attemptId)
val futureJobDatas = async {
getJobDatas(attemptTarget)
}
val futureStageDatas = async {
getStageDatas(attemptTarget)
}
val futureExecutorSummaries = async {
getExecutorSummaries(attemptTarget)
}
SparkRestDerivedData(
applicationInfo,
await(futureJobDatas),
await(futureStageDatas),
await(futureExecutorSummaries)
)
}
case None => {
throw new NoYarnClientAttemptInfoExistsException(s"${appId} was initiated from yarn-client, so no attempt information exists. Skipping job.")
}
}
}

with a custom exception NoYarnClientAttemptInfoExistsException that avoids writing the stack dump into the log file for brevity purposes:

public class NoYarnClientAttemptInfoExistsException extends Exception {
    @Override
    public Throwable fillInStackTrace() {
        return null;
    }
    public NoYarnClientAttemptInfoExistsException(String message) {
            super(message);
        }
}

@bretlowery and @leechedan: I have submitted a PR (https://github.com/linkedin/dr-elephant/pull/193) to fix this problem. Maybe you can test this patch. Both cluster and client mode applications should work with this patch.

Patch committed: e93d431
Thanks @shkhrgpt


OSError: [Errno 2] No such file or directory

Recent version from github produces the following error. Don't know why?
sudo ./bin/ycsb load cassandra-cql -p hosts="<IP_ADDRESS>" -s -P workloads/workloada
[WARN]  Running against a source checkout. In order to get our runtime dependencies we'll have to invoke Maven. Depending on the state of your system, this may take ~30-45 seconds
[DEBUG]  Running 'mvn -pl site.ycsb:cassandra-binding -am package -DskipTests dependency:build-classpath -DincludeScope=compile -Dmdep.outputFilterFile=true'
Traceback (most recent call last):
File "./bin/ycsb", line 325, in
sys.exit(main())
File "./bin/ycsb", line 298, in main
maven_says = get_classpath_from_maven(project)
File "./bin/ycsb", line 218, in get_classpath_from_maven
"-Dmdep.outputFilterFile=true"])
File "./bin/ycsb", line 167, in check_output
process = subprocess.Popen(stdout=subprocess.PIPE, *popenargs, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 711, in init
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

you should install openjdk at first

probably you are also missing a maven install. you should run from our latest release artifacts instead of building if you can.
you also should not run ycsb as root, but I do not think that is causing your current problem.

Did using the binaries from the latest ycsb release work for you?


Add Fetch/Create workspace APIs

Changes:

Add Workspace Table to dynamo DB (entity definition here)

To be verified: Dynamo DB LocalSecondaryIndexes has been used to index diseaseId in WorkspaceTable and workspaceId in ProgramTable

Create program API, Now require workspaceId field

Add create Workspace API :

API: POST /workspaces
    "workspace": {
        "name": "My test workspace",
        "description": "This workpace is used to test",
        "disease": {
            "name": "string",
            "abbreviation": "string",
            "omimId": "string",
            "causalGene": "string",
            "mutationImpact": "string",
            "proteinSize": 20
        }
    }
}

Fetch all user's Workspaces API :

API: GET /workspaces

To Test:

API endpoint: https://w1929x5und.execute-api.us-west-2.amazonaws.com/development/workspaces
GET Workspaces API:

curl 'https://w1929x5und.execute-api.us-west-2.amazonaws.com/development/workspaces' \
--header 'Authorization <COGNITO_TOKEN_HER>'

Create Workspaces API:

curl -XPOST 'https://w1929x5und.execute-api.us-west-2.amazonaws.com/development/workspaces' \
--header 'Authorization: <COGNITO_TOKEN_HER>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "workspace": {
       "name": "My test workspace",
        "description": "This workpace is used to test",
        "disease": {
            "name": "string",
            "abbreviation": "string",
            "omimId": "string",
            "causalGene": "string",
            "mutationImpact": "string",
            "proteinSize": 20
        }
    }
}'

Checklist

[x] Tests have been added and are passing
[x] Documentation has been updated

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Error trying to install

Error and traceback:
Downloading/unpacking rockstar
  Downloading rockstar-0.3-py2-none-any.whl
Downloading/unpacking gitpython==1.0.1 (from rockstar)
  Running setup.py (path:c:\users\adrin~1\appdata\local\temp\pip_build_Adrißn\gitpython\setup.py) egg_info for package gitpython
    W:\DEV\Python2X\lib\distutils\dist.py:267: UserWarning: Unknown distribution option: 'test_requirements'
      warnings.warn(msg)

    warning: no files found matching 'README'
Cleaning up...
Exception:
Traceback (most recent call last):
  File "W:\DEV\Python2X\lib\site-packages\pip\basecommand.py", line 122, in main
    status = self.run(options, args)
  File "W:\DEV\Python2X\lib\site-packages\pip\commands\install.py", line 278, in run
    requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, bundle=self.bundle)
  File "W:\DEV\Python2X\lib\site-packages\pip\req.py", line 1234, in prepare_files
    req_to_install.assert_source_matches_version()
  File "W:\DEV\Python2X\lib\site-packages\pip\req.py", line 464, in assert_source_matches_version
    % (display_path(self.source_dir), version, self))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe1 in position 60: ordinal not in range(128)

Traceback (most recent call last):
  File "W:\DEV\Python2X\lib\runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "W:\DEV\Python2X\lib\runpy.py", line 72, in _run_code
    exec code in run_globals
  File "W:\DEV\Python2X\Scripts\pip.exe\__main__.py", line 9, in <module>
  File "W:\DEV\Python2X\lib\site-packages\pip\__init__.py", line 185, in main
    return command.main(cmd_args)
  File "W:\DEV\Python2X\lib\site-packages\pip\basecommand.py", line 161, in main
    text = '\n'.join(complete_log)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe1 in position 75: ordinal not in range(128)

Running Python 2.7.9

Hey it's Python 3 only.


Support pathname-based routing

I believe that this library could also support pathname-based routing, which would, in turn, allow for its use on server-side rendering (for isomorphic/universal applications).

Closing this as I just saw in the guide:
This library facilitates hash-based routing. If you're looking to do pushstate routing with the history object, then you are in the wrong place.

@arthur-xavier Did you end up settling for hash-based routing or did you find an alternative?


deprecate ControllerLoader, suggest to use ControllerManager instead

see https://github.com/zendframework/zf2/pull/4962

rebased

I've updated PR title

based on @weierophinney comment on https://github.com/zendframework/zend-authentication/pull/2#issuecomment-110043990 , I will update it as fully remove ControllerLoader, and it will be a PR for 3.0

PR title and commits force updated so we use it for 3.0

@Ocramius it can be marked as 3.0.0 milestone again ;)

With the previous approach this could be merged right now.


Software Implementation

-Quality of source code reviews
-Correct implementation of design patterns
-Respect of code conventions
-Design quality as measured by number of classes/packages, module size, coupling, cohesion
-Quality of source code documentation
-Refactoring activity documented in commit messages
-Quality detail of commit messages
-Use of feature branches
-Use of atomic commits
-linking of commits to issues (user stories)

Not sure if all of those goes in the document or not. I also need to wait until the coding for sprint 2 is over to document the "real" values of the metrics, number of classes, cohesion, etc. I emailed the teacher about what goes in the doc and what doesn't. Might take a few more days depending how fast the teacher replies which will might result in a bit of delay. Already started to make a "template" for my part.

There isn't much to document for software implementation so this issue is basically done


Fix the filter in the UI to allow filtering for only legal clusters on a device.

Fix the filter in the UI to allow filtering for only legal clusters on a device.

Dear @tecimovic how can we indicate which cluster is legal?

All of the legal clusters are children of the  in  tags.
    <deviceType>         <name>MA-rootdevice</name>         <domain>CHIP</domain>         <typeName>Matter Root Node</typeName>         <profileId editable="false">0x0103</profileId>         <deviceId editable="false">0x0016</deviceId>         <clusters lockOthers="true">             <include cluster="Basic" client="false" server="true" clientLocked="true" serverLocked="true">                 <requireAttribute>INTERACTION_MODEL_VERSION</requireAttribute>                 <requireAttribute>VENDOR_NAME</requireAttribute>                 <requireAttribute>VENDOR_ID</requireAttribute>                 <requireAttribute>PRODUCT_NAME</requireAttribute>                 <requireAttribute>PRODUCT_ID</requireAttribute>                 <requireAttribute>NODE_LABEL</requireAttribute>                 <requireAttribute>LOCATION</requireAttribute>                 <requireAttribute>HARDWARE_VERSION</requireAttribute>                 <requireAttribute>HARDWARE_VERSION_STRING</requireAttribute>                 <requireAttribute>SOFTWARE_VERSION</requireAttribute>                 <requireAttribute>SOFTWARE_VERSION_STRING</requireAttribute>             </include>             <include cluster="Descriptor" client="false" server="true" clientLocked="true" serverLocked="true">                 <requireAttribute>DEVICE_TYPE_LIST</requireAttribute>                 <requireAttribute>SERVER_LIST</requireAttribute>                 <requireAttribute>CLIENT_LIST</requireAttribute>                 <requireAttribute>PARTS_LIST</requireAttribute>             </include>             <include cluster="ACL" client="false" server="true" clientLocked="true" serverLocked="true"></include>             <include cluster="Power Source Configuration" client="false" server="false" clientLocked="true" serverLocked="false"></include>             <include cluster="Time Synchronization" client="false" server="false" clientLocked="true" serverLocked="false"></include>             <include cluster="Group Key Management" client="false" server="true" clientLocked="true" serverLocked="true"></include>             <include cluster="General Commissioning" client="false" server="true" clientLocked="true" serverLocked="true"></include>             <include cluster="Network Commissioning" client="false" server="true" clientLocked="true" serverLocked="true"></include>             <include cluster="AdministratorCommissioning" client="false" server="true" clientLocked="true" serverLocked="true"></include>             <include cluster="Operational Credentials" client="false" server="true" clientLocked="true" serverLocked="true"></include>             <include cluster="Localization Configuration" client="false" server="false" clientLocked="true" serverLocked="false"></include>             <include cluster="Localization Time Format" client="false" server="false" clientLocked="true" serverLocked="false"></include>             <include cluster="Localization Unit" client="false" server="false" clientLocked="true" serverLocked="false"></include>             <include cluster="General Diagnostics" client="false" server="true" clientLocked="true" serverLocked="true"></include>             <include cluster="Diagnostic Logs" client="false" server="false" clientLocked="true" serverLocked="false"></include>             <include cluster="Software Diagnostics" client="false" server="false" clientLocked="true" serverLocked="false"></include>             <include cluster="Ethernet Network Diagnostics" client="false" server="false" clientLocked="true" serverLocked="false"></include>             <include cluster="Wifi Network Diagnostics" client="false" server="false" clientLocked="true" serverLocked="false"></include>             <include cluster="Thread Network Diagnostics" client="false" server="false" clientLocked="true" serverLocked="false"></include>         </clusters>

How to indicate? A new filter option -- LEGAL.

You won't see the optional attributes on controller zap, you need to first change the controller zap to server and then enable the attribute, then change it back to client.
This is a known issue, not recent regression.

I'm trying to validate this. I don't see any new options in the filter menu, was there one added?

I have cloned the consultatnt branch https://github.com/Mehradml/zap.git and I still don't see this change in the filter dropdown.

I don't understand what the concept of a "LEGAL" cluster is? @jonsmirl , can you point to this concept in the spec, either Matter or Zigbee? I'm assuming you are using this term to identify any cluster listed under a device, but "LEGAL" implies that other clusters are "ILLEGAL" which I don't think we want to indicate. Please clarify. Thanks

When the device type has been picked as a Matter device, by default only display the clusters specified for that device in the Matter specification.  Yes you can have any cluster in the device, but if you pick them they likely won't work because no one is supporting them in the controllers. So by default, if you pick a Matter device you can only see the clusters the Matter spec allows.
If you want some hidden advanced mode that lets you turn on Zigbee HA clusters on a Matter device, that is fine too. But it should be hidden by default.
The point of this is to prevent some customer starting out with Matter from adding in Zigbee HA clusters and then spending a month figuring out why their device isn't using the Zigbee HA features.

Ok so it's not LEGAL as much as it is "Matter supported", but Legal is a good short description.


ability to asynchronously wait until all buffere data has been written

This is essential for preventing write-buffer bloating. Now, I'm required to use protected method
await request._writer.drain()
Do not sure this helps. Will experiment. Probably you should remove access to request.transport and reveal access to requiest.writer and request.reader

response.drain() is the answer. Sorry that I bother you and eat cool #666 number

But anyway, you should document that response is subclass of StreamWrier in documentation. request is StreamReader ?


Support for cache headers

adding test cases

@RajeshHegde the pull request seems missing some of the changes you made earlier, probably this is due to the previous merge that I did and then reverted it back for the lack of tests.
Please create a new pull request (I will close this one) containing all the changes with the tests passing, so I can merge it.
Thanks again for your contribution.

I will send new pull request tomorrow.


View Profile, Add header and footers

First, copy the header and footer from Atif and then add them to the dashboard, later work on the profile.

finished with profile, header, footer and profile. with css


Position of the titles is flipped, should be text first then picture.

On the blog section, it is necessarily to change text position from below to above the picture.

Fixe on issue #21.


Pipeline Operator but for Generic Types

Search Terms
pipeline operator
generic types
Suggestion
A pipeline operator but for generic types
Use Cases
This would be less ugly and more readable
Examples
The following
Promise<Signed<Message<String>>>

would become
Promise of Signed of Message of String

On an interface
interface Duck {
    quack(): Promise of String;
}

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

Near-duplicate of #34165

Similarly to #34165 I find the readability claim debatable.
Also what happens with generics with multiple type parameters ? would you use G of T1 and T2 ? How would you disambiguate something like G1 of G2 and T1 and T2 is that G1<G2<T1, T2>> or G1<G2<T1>, T2>.  While the angle brackets are not the prettiest bit of syntax they do make it clear where one type ends and the other continues.

Promise of String
Promise of (String and number)

Parentheses are too close to angle brackets for my taste; no human being uses parentheses or angle brackets to communicate.  Instead of punctuation we should use a keyword to signify where a generic parameter list ends.  Since reusing existing keywords is preferable to coining new ones (and helps the environment), a good one to use for this would be finally, which does a good job of signaling the end of something.   And instead of and, a new keyword, we could re-use with, which is just sitting around gathering dust anyway.  Anyway, that means we can turn the completely incomprehensible
Pick<Map<string, Promise<number>>, "get">

into the human-friendly
Pick of Map of string with Promise of number finally finally "get" finally

:trollface:

@jcalz 😬
We're extremely conservative around adding syntax to the type space; new syntax needs to have very concrete upsides


Deploy Script Error in AutoUpdates [BUG]

Line 275 of deploy.sh says:
sed -i 's#//Unattended-Upgrade::Automatic-Reboot-Time "02:00";Unattended-Upgrade::Automatic-Reboot-Time "02:00";#g' /etc/apt/apt.conf.d/50unattended-upgrades
I think this should be:
sed -i 's#//Unattended-Upgrade::Automatic-Reboot-Time "02:00";#Unattended-Upgrade::Automatic-Reboot-Time "02:00";#g' /etc/apt/apt.conf.d/50unattended-upgrades

Hi @nickjossy, Thanks for this, I have just tested this and you are correct.

Fixed in https://github.com/ukncsc/lme/commit/88264ddaaae27e1df7b08b7b00a62a55adda8f75
Thanks.


merge from konsum-frontend-svelte,template-arlac77-github,template-svelte-app

package.json

chore(deps): add ^10.15.6 remove ^10.15.5 (devDependencies.npm-pkgbuild)

:tada: This PR is included in version 1.34.11 :tada:
The release is available on:

npm package (@latest dist-tag)
v1.34.11
GitHub release

Your semantic-release bot :package::rocket:


CreateTun error if TunConfig.Ipv6 != ""

I run kubevpn proxy command kubevpn proxy deploymeny/xx,
PS D:\kubevpn\bin> kubevpn proxy deployment/test-deploy --headers name=jack
connectting to cluster
start to connect
got cidr from cache
get cidr successfully
update ref count successfully
traffic manager already exist, reuse it
port forward ready
add ipv6 addr to tun err:Element not found.
create tun device error: Element not found.
create tun listener error: Element not found.
parse route error: Element not found.
start local tun service failed: Element not found.
do connect error: Element not found.
prepare to exit, cleaning up
update ref count successfully
clean up successfully
Error: rpc error: code = Unknown desc = Element not found.

error occurs in tun_windows.go:createTun func:  ifName.AddIPAddress(prefix)
func createTun(cfg Config) (conn net.Conn, itf *net.Interface, err error) {
	if cfg.Addr == "" && cfg.Addr6 == "" {
		err = fmt.Errorf("ipv4 address and ipv6 address can not be empty at same time")
		return
	}

	interfaceName := "kubevpn"
	if len(cfg.Name) != 0 {
		interfaceName = cfg.Name
	}
	tunDevice, err := wireguardtun.CreateTUN(interfaceName, cfg.MTU)
	if err != nil {
		err = fmt.Errorf("failed to create TUN device: %w", err)
		return
	}

	ifName := winipcfg.LUID(tunDevice.(*wireguardtun.NativeTun).LUID())

	var ipv4, ipv6 net.IP
	if cfg.Addr != "" {
		if ipv4, _, err = net.ParseCIDR(cfg.Addr); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			return
		}
	}

	if cfg.Addr6 != "" {
		if ipv6, _, err = net.ParseCIDR(cfg.Addr6); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr6); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			log.Infof("add ipv6 addr to tun err:%v", err)
			return
		}
	}

i used nocalhost's proxy mode before, and nocalhost does not support ipv6, but it works for me.
if i remove the setting env code:
func (c *ConnectOptions) startLocalTunServe(ctx context.Context, forwardAddress string, lite bool) (err error) {
	// todo figure it out why
	if util.IsWindows() {
		c.localTunIPv4.Mask = net.CIDRMask(0, 32)
	}
	var list = sets.New[string]()
	if !lite {
		list.Insert(config.CIDR.String())
	}
	for _, ipNet := range c.cidrs {
		list.Insert(ipNet.String())
	}
	// add extra-cidr
	for _, s := range c.ExtraCIDR {
		_, _, err = net.ParseCIDR(s)
		if err != nil {
			return fmt.Errorf("invalid extra-cidr %s, err: %v", s, err)
		}
		list.Insert(s)
	}
	// if err = os.Setenv(config.EnvInboundPodTunIPv6, c.localTunIPv6.String()); err != nil {
	//	return err
	// }

createTun will work successfully.
does anyone know how to solve this problem?

Hello, sorry for you meet this issue. Can you privode which Windows version you are using?

`D:>kubevpn proxy deployment/authors --headers a=1
connectting to cluster
start to connect
got cidr from cache
get cidr successfully
update ref count successfully
traffic manager already exist, reuse it
port forward ready
tunnel connected
adding route...
dns service ok
start to create remote inbound pod for deployment/authors
patch workload default/deployment/authors with sidecar
rollout status for deployment/authors
Waiting for deployment spec update to be observed...
Waiting for deployment spec update to be observed...
Waiting for deployment "authors" rollout to finish: 0 out of 1 new replicas have been updated...
Waiting for deployment "authors" rollout to finish: 1 old replicas are pending termination...
 Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

My os is:
版本	Windows 10 专业版
版本号	21H1
安装日期	2023/5/30
操作系统内部版本	19043.1645
体验	Windows Feature Experience Pack 120.2212.4170.0

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

My os is: 版本 Windows 10 专业版 版本号 21H1 安装日期 2023/5/30 操作系统内部版本 19043.1645 体验 Windows Feature Experience Pack 120.2212.4170.0

Ok, got it, can you please check the bellow link to make sure registry table is setting correctly
https://forums.he.net/index.php?topic=653.0 https://forums.he.net/index.php?topic=1492.0

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

My os is: 版本 Windows 10 专业版 版本号 21H1 安装日期 2023/5/30 操作系统内部版本 19043.1645 体验 Windows Feature Experience Pack 120.2212.4170.0

Ok, got it, can you please check the bellow link to make sure registry table is setting correctly https://forums.he.net/index.php?topic=653.0 https://forums.he.net/index.php?topic=1492.0

OK, i'll give it a try.

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

My os is: 版本 Windows 10 专业版 版本号 21H1 安装日期 2023/5/30 操作系统内部版本 19043.1645 体验 Windows Feature Experience Pack 120.2212.4170.0

Ok, got it, can you please check the bellow link to make sure registry table is setting correctly https://forums.he.net/index.php?topic=653.0 https://forums.he.net/index.php?topic=1492.0

It works! Thanks a lot!

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

My os is: 版本 Windows 10 专业版 版本号 21H1 安装日期 2023/5/30 操作系统内部版本 19043.1645 体验 Windows Feature Experience Pack 120.2212.4170.0

Ok, got it, can you please check the bellow link to make sure registry table is setting correctly https://forums.he.net/index.php?topic=653.0 https://forums.he.net/index.php?topic=1492.0

It works! Thanks a lot!

Wow, congratulations ~~. Maybe you can introduce kubevpn to your colleagues or friends, welcome pr and star ~

Yes, i will.

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

sorry to bother, but i wonder what is the meaning of adding ipv6 address to tun device in pkg/tun/tun_windows.go:CreateTun()
	if cfg.Addr6 != "" {
		if ipv6, _, err = net.ParseCIDR(cfg.Addr6); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr6); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			return
		}
	}

it seems works fine when tun device has no ipv6 address

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

sorry to bother, but i wonder what is the meaning of adding ipv6 address to tun device in pkg/tun/tun_windows.go:CreateTun()
	if cfg.Addr6 != "" {
		if ipv6, _, err = net.ParseCIDR(cfg.Addr6); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr6); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			return
		}
	}

it seems works fine when tun device has no ipv6 address

It will generate a IPv6 addr by default. so our computer needs to enable IPv6 feature

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

sorry to bother, but i wonder what is the meaning of adding ipv6 address to tun device in pkg/tun/tun_windows.go:CreateTun()
	if cfg.Addr6 != "" {
		if ipv6, _, err = net.ParseCIDR(cfg.Addr6); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr6); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			return
		}
	}

it seems works fine when tun device has no ipv6 address

It will generate a IPv6 addr by default. so our computer needs to enable IPv6 feature

ok, got it.

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

sorry to bother, but i wonder what is the meaning of adding ipv6 address to tun device in pkg/tun/tun_windows.go:CreateTun()
	if cfg.Addr6 != "" {
		if ipv6, _, err = net.ParseCIDR(cfg.Addr6); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr6); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			return
		}
	}

it seems works fine when tun device has no ipv6 address

It will generate a IPv6 addr by default. so our computer needs to enable IPv6 feature

ok, got it.

Microsoft docs:
https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6
https://learn.microsoft.com/zh-cn/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

sorry to bother, but i wonder what is the meaning of adding ipv6 address to tun device in pkg/tun/tun_windows.go:CreateTun()
	if cfg.Addr6 != "" {
		if ipv6, _, err = net.ParseCIDR(cfg.Addr6); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr6); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			return
		}
	}

it seems works fine when tun device has no ipv6 address

It will generate a IPv6 addr by default. so our computer needs to enable IPv6 feature

ok, got it.

Microsoft docs: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6 https://learn.microsoft.com/zh-cn/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6

Is that possible that i do not need ipv6 capability, and tun device has no need to add an ipv6 address.
I have this issue because somehow me and my friend both encoutered the "element not found" error, we two must configure  the ipv6 registry key. But actually we seem don't want ipv6 feature so much. So could the ipv6 capability be an user option when use kubevpn proxy?

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

sorry to bother, but i wonder what is the meaning of adding ipv6 address to tun device in pkg/tun/tun_windows.go:CreateTun()
	if cfg.Addr6 != "" {
		if ipv6, _, err = net.ParseCIDR(cfg.Addr6); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr6); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			return
		}
	}

it seems works fine when tun device has no ipv6 address

It will generate a IPv6 addr by default. so our computer needs to enable IPv6 feature

ok, got it.

Microsoft docs: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6 https://learn.microsoft.com/zh-cn/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6

Is that possible that i do not need ipv6 capability, and tun device has no need to add an ipv6 address. I have this issue because somehow me and my friend both encoutered the "element not found" error, we two must configure the ipv6 registry key. But actually we seem don't want ipv6 feature so much. So could the ipv6 capability be an user option when use kubevpn proxy?

Maybe i can check if PC not enable IPv6, not to set IPv6 address ? 🤔

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

sorry to bother, but i wonder what is the meaning of adding ipv6 address to tun device in pkg/tun/tun_windows.go:CreateTun()
	if cfg.Addr6 != "" {
		if ipv6, _, err = net.ParseCIDR(cfg.Addr6); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr6); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			return
		}
	}

it seems works fine when tun device has no ipv6 address

It will generate a IPv6 addr by default. so our computer needs to enable IPv6 feature

ok, got it.

Microsoft docs: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6 https://learn.microsoft.com/zh-cn/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6

Is that possible that i do not need ipv6 capability, and tun device has no need to add an ipv6 address. I have this issue because somehow me and my friend both encoutered the "element not found" error, we two must configure the ipv6 registry key. But actually we seem don't want ipv6 feature so much. So could the ipv6 capability be an user option when use kubevpn proxy?

Maybe i can check if PC not enable IPv6, not to set IPv6 address ? 🤔

i have tried this case before, it seems to work well.

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

sorry to bother, but i wonder what is the meaning of adding ipv6 address to tun device in pkg/tun/tun_windows.go:CreateTun()
	if cfg.Addr6 != "" {
		if ipv6, _, err = net.ParseCIDR(cfg.Addr6); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr6); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			return
		}
	}

it seems works fine when tun device has no ipv6 address

It will generate a IPv6 addr by default. so our computer needs to enable IPv6 feature

ok, got it.

Microsoft docs: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6 https://learn.microsoft.com/zh-cn/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6

Is that possible that i do not need ipv6 capability, and tun device has no need to add an ipv6 address. I have this issue because somehow me and my friend both encoutered the "element not found" error, we two must configure the ipv6 registry key. But actually we seem don't want ipv6 feature so much. So could the ipv6 capability be an user option when use kubevpn proxy?

Maybe i can check if PC not enable IPv6, not to set IPv6 address ? 🤔

i have tried this case before, it seems to work well.

Ok. I got it. I will fix it as soon as possible.

Hello, sorry for you meet this issue. Can you privode which Windows version you are using? and i searched Element not found issue on Google, It shows that please make sure HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\DisabledComponents  this key should not exist. ref ref2

sorry to bother, but i wonder what is the meaning of adding ipv6 address to tun device in pkg/tun/tun_windows.go:CreateTun()
	if cfg.Addr6 != "" {
		if ipv6, _, err = net.ParseCIDR(cfg.Addr6); err != nil {
			return
		}
		var prefix netip.Prefix
		if prefix, err = netip.ParsePrefix(cfg.Addr6); err != nil {
			return
		}
		if err = ifName.AddIPAddress(prefix); err != nil {
			return
		}
	}

it seems works fine when tun device has no ipv6 address

It will generate a IPv6 addr by default. so our computer needs to enable IPv6 feature

ok, got it.

Microsoft docs: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6 https://learn.microsoft.com/zh-cn/troubleshoot/windows-server/networking/configure-ipv6-in-windows#use-registry-key-to-configure-ipv6

Is that possible that i do not need ipv6 capability, and tun device has no need to add an ipv6 address. I have this issue because somehow me and my friend both encoutered the "element not found" error, we two must configure the ipv6 registry key. But actually we seem don't want ipv6 feature so much. So could the ipv6 capability be an user option when use kubevpn proxy?

Maybe i can check if PC not enable IPv6, not to set IPv6 address ? 🤔

i have tried this case before, it seems to work well.

Ok. I got it. I will fix it as soon as possible.

fixed this issue in commit: f7957c2a25f52a0af68c3af9154c3514a2a538ad

@kyr1eeee. Hello. i redo released v2.2.1 and fixed this issue. You can download latest version and try it again. Or us e command kubevpn upgrade   to upgrade

Yes, it works even if my pc doesn't enable tcpip6


Fix grammar in README.md & Changed headings

Changes:

Changes All RIghts are Reserved to All Rights are Reserved
All h1 headings to h2 except the first one

Resolves #56

Thanks

Thanks

@Zaid-maker np (•◡•)


Icon request: Tor

I'd love to link my hidden service version of my website on my omg.lol page, but attempting to use font-awesome onion ({onion}) just results in showing the default font awesome flag, and {tor} doesn't work either.
Given the unique structure of onion addresses, automatically picking the correct icon when the domain part of a url ends in .onion seems like it would be pretty doable. Time permitting, I might try to fulfill this issue myself -- but opening in case anyone else can quickly get to it before me :)
Until then, I'll just use {user} for my regular website and {user-secret} for my hidden service version of my website :)

Should be good to go now! URLs ending in .onion will get the icon automatically, and the {tor} tag will also apply it.

You may need to refresh a couple of times for the custom icon font to reload. Let me know if you run into any issues!

Awesome, thanks for such a quick turnaround time!