text:
Rancher?

What steps did you take and what happened:
Installed this in rancher, but I am not getting any volumes provisioned.
What did you expect to happen:
Volumes to be provisioned
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other Pastebin is fine.)

`kubectl logs -f openebs-lvm-controller-0 -n kube-system -c openebs-lvm-plugin
kubectl logs -f openebs-lvm-node-[xxxx] -n kube-system -c openebs-lvm-plugin
kubectl get pods -n kube-system
kubectl get lvmvol -A -o yaml

gist with those
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

LVM Driver version
Kubernetes version (use kubectl version)

kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.2", GitCommit:"f5743093fd1c663cb0cbc89748f730662345d44d", GitTreeState:"clean", BuildDate:"2020-09-16T13:41:02Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.8", GitCommit:"5575935422cc1cf5169dfc8847cb587aa47bac5a", GitTreeState:"clean", BuildDate:"2021-06-16T12:53:07Z", GoVersion:"go1.15.13", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes installer & version:
rancher
Cloud provider or hardware configuration:
KVM on linux
OS (e.g. from /etc/os-release):

cat /etc/os-release
NAME="RancherOS"
VERSION=v1.5.8
ID=rancheros
ID_LIKE=
VERSION_ID=v1.5.8
PRETTY_NAME="RancherOS v1.5.8"
HOME_URL="http://rancher.com/rancher-os/"
SUPPORT_URL="https://forums.rancher.com/c/rancher-os"
BUG_REPORT_URL="https://github.com/rancher/os/issues"
BUILD_ID=

[rancher@orm01-vault2 ~]$ sudo pvscan
  PV /dev/vda1   VG lvmvg           lvm2 [<33.30 GiB / <33.30 GiB free]
  Total: 1 [<33.30 GiB] / in use: 1 [<33.30 GiB] / in no VG: 0 [0   ]
[rancher@orm01-vault2 ~]$ sudo vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group "lvmvg" using metadata type lvm2

$ cat openebs-lvm-sc.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: openebs-lvmpv
parameters:
  storage: "lvm"
  volgroup: "lvmvg"
provisioner: local.csi.openebs.io

$ k get sc
NAME                        PROVISIONER                                                RECLAIMPOLICY   VOLUMEBINDINGMODE      ALLOWVOLUMEEXPANSION   AGE
openebs-device              openebs.io/local                                           Delete          WaitForFirstConsumer   false                  5h38m
openebs-hostpath            openebs.io/local                                           Delete          WaitForFirstConsumer   false                  5h38m
openebs-jiva-default        openebs.io/provisioner-iscsi                               Delete          Immediate              false                  5h38m
openebs-lvmpv (default)     local.csi.openebs.io                                       Delete          Immediate              false                  114m
openebs-snapshot-promoter   volumesnapshot.external-storage.k8s.io/snapshot-promoter   Delete          Immediate              false                  5h38m

$ k get pvc
NAME                                       STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS    AGE
data-whc01elastic-opendistro-es-data-0     Pending                                      openebs-lvmpv   105m
data-whc01elastic-opendistro-es-master-0   Pending                                      openebs-lvmpv   105m

$ k describe pvc data-whc01elastic-opendistro-es-data-0
Name:          data-whc01elastic-opendistro-es-data-0
Namespace:     default
StorageClass:  openebs-lvmpv
Status:        Pending
Volume:
Labels:        app=whc01elastic-opendistro-es
               heritage=Helm
               release=whc01elastic
               role=data
Annotations:   volume.beta.kubernetes.io/storage-provisioner: local.csi.openebs.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Mounted By:    whc01elastic-opendistro-es-data-0
Events:
  Type    Reason                Age                     From                                                                                Message
  ----    ------                ----                    ----                                                                                -------
  Normal  ExternalProvisioning  4m39s (x401 over 104m)  persistentvolume-controller                                                         waiting for a volume to be created, either by external provisioner "local.csi.openebs.io" or manually created by system administrator
  Normal  Provisioning          91s (x29 over 105m)     local.csi.openebs.io_openebs-lvm-controller-0_33139b9f-e336-4a2b-a90a-33b6bb4a91c3  External provisioner is provisioning volume for claim "default/data-whc01elastic-opendistro-es-data-0"

@joshuacox can you share the o/p $ kubectl get csidrivers local.csi.openebs.io -oyaml? Also can you shared the o/p of kunectl describe pvc?

$ kubectl get csidrivers local.csi.openebs.io -oyaml
apiVersion: storage.k8s.io/v1
kind: CSIDriver
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"storage.k8s.io/v1","kind":"CSIDriver","metadata":{"annotations":{},"name":"local.csi.openebs.io"},"spec":{"attachRequired":false,"podInfoOnMount":true}}
  creationTimestamp: "2021-06-25T01:30:51Z"
  managedFields:
  - apiVersion: storage.k8s.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:kubectl.kubernetes.io/last-applied-configuration: {}
      f:spec:
        f:attachRequired: {}
        f:fsGroupPolicy: {}
        f:podInfoOnMount: {}
        f:volumeLifecycleModes:
          .: {}
          v:"Persistent": {}
    manager: kubectl-client-side-apply
    operation: Update
    time: "2021-06-25T01:30:51Z"
  name: local.csi.openebs.io
  resourceVersion: "122338"
  uid: 0f340ecb-1e1f-4f6d-8483-06097d1ef929
spec:
  attachRequired: false
  fsGroupPolicy: ReadWriteOnceWithFSType
  podInfoOnMount: true
  volumeLifecycleModes:
  - Persistent

apiVersion: storage.k8s.io/v1
kind: CSIDriver
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"storage.k8s.io/v1","kind":"CSIDriver","metadata":{"annotations":{},"name":"local.csi.openebs.io"},"spec":{"attachRequired":false,"podInfoOnMount":true}}
  creationTimestamp: "2021-06-25T01:30:51Z"
  managedFields:
  - apiVersion: storage.k8s.io/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:kubectl.kubernetes.io/last-applied-configuration: {}
      f:spec:
        f:attachRequired: {}
        f:fsGroupPolicy: {}
        f:podInfoOnMount: {}
        f:volumeLifecycleModes:
          .: {}
          v:"Persistent": {}
    manager: kubectl-client-side-apply
    operation: Update
    time: "2021-06-25T01:30:51Z"
  name: local.csi.openebs.io
  resourceVersion: "122338"
  uid: 0f340ecb-1e1f-4f6d-8483-06097d1ef929
spec:
  attachRequired: false
  fsGroupPolicy: ReadWriteOnceWithFSType
  podInfoOnMount: true
  volumeLifecycleModes:
  - Persistent

Name:          data-whc01elastic-opendistro-es-data-0
Namespace:     default
StorageClass:  openebs-lvmpv
Status:        Pending
Volume:
Labels:        app=whc01elastic-opendistro-es
               heritage=Helm
               release=whc01elastic
               role=data
Annotations:   volume.beta.kubernetes.io/storage-provisioner: local.csi.openebs.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Mounted By:    whc01elastic-opendistro-es-data-0
Events:
  Type     Reason                Age                      From                                                                                Message
  ----     ------                ----                     ----                                                                                -------
  Warning  ProvisioningFailed    48m (x73 over 6h12m)     local.csi.openebs.io_openebs-lvm-controller-0_02d19800-b17d-4543-bacc-b1468ad17f46  failed to provision volume with StorageClass "openebs-lvmpv": error generating accessibility requirements: no available topology found
  Normal   Provisioning          3m44s (x82 over 6h12m)   local.csi.openebs.io_openebs-lvm-controller-0_02d19800-b17d-4543-bacc-b1468ad17f46  External provisioner is provisioning volume for claim "default/data-whc01elastic-opendistro-es-data-0"
  Normal   ExternalProvisioning  117s (x1482 over 6h11m)  persistentvolume-controller                                                         waiting for a volume to be created, either by external provisioner "local.csi.openebs.io" or manually created by system administrator

Name:          data-whc01elastic-opendistro-es-master-0
Namespace:     default
StorageClass:  openebs-lvmpv
Status:        Pending
Volume:
Labels:        app=whc01elastic-opendistro-es
               heritage=Helm
               release=whc01elastic
               role=master
Annotations:   volume.beta.kubernetes.io/storage-provisioner: local.csi.openebs.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Mounted By:    whc01elastic-opendistro-es-master-0
Events:
  Type     Reason                Age                       From                                                                                Message
  ----     ------                ----                      ----                                                                                -------
  Warning  ProvisioningFailed    59m (x71 over 6h13m)      local.csi.openebs.io_openebs-lvm-controller-0_02d19800-b17d-4543-bacc-b1468ad17f46  failed to provision volume with StorageClass "openebs-lvmpv": error generating accessibility requirements: no available topology found
  Normal   Provisioning          4m30s (x82 over 6h13m)    local.csi.openebs.io_openebs-lvm-controller-0_02d19800-b17d-4543-bacc-b1468ad17f46  External provisioner is provisioning volume for claim "default/data-whc01elastic-opendistro-es-master-0"
  Normal   ExternalProvisioning  2m43s (x1481 over 6h12m)  persistentvolume-controller                                                         waiting for a volume to be created, either by external provisioner "local.csi.openebs.io" or manually created by system administrator

@pawanpraka1 of note this is RancherOS, so it might be missing some lvm utility that openebs is expecting.

@joshuacox I see that the error is "no available topology found". Can you get me below o/p?
kubectl get csinodes -oyaml

Also, I need to check the openebs-lvm-plugin container log in the openebs-lvm-controller-0 pod.

of note this is RancherOS, so it might be missing some lvm utility that openebs is expecting.
that might be the case but control has not reached to that stage. It is failing before that.

Can you also share  openebs-lvm-plugin container log in the openebs-lvm-node-xxxx pod also? Also, what is the k8s version you are using?

k8s = 1.20.8
k get nodes -o wide
NAME                STATUS   ROLES                      AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE           KERNEL-VERSION     CONTAINER-RUNTIME
orm01-ctl-vault2    Ready    controlplane               22h   v1.20.8   10.0.23.87    <none>        RancherOS v1.5.8   4.14.138-rancher   docker://19.3.15
orm01-etcd-vault2   Ready    etcd                       22h   v1.20.8   10.0.23.197   <none>        RancherOS v1.5.8   4.14.138-rancher   docker://19.3.15
orm01-vault1        Ready    controlplane,etcd,worker   23h   v1.20.8   10.0.23.115   <none>        RancherOS v1.5.8   4.14.138-rancher   docker://19.3.15
orm01-vault2        Ready    worker                     23h   v1.20.8   10.0.23.5     <none>        RancherOS v1.5.8   4.14.138-rancher   docker://19.3.15
orm01-vault4        Ready    controlplane,etcd,worker   23h   v1.20.8   10.0.23.137   <none>        RancherOS v1.5.8   4.14.138-rancher   docker://19.3.15

apiVersion: v1
items:
- apiVersion: storage.k8s.io/v1
  kind: CSINode
  metadata:
    creationTimestamp: "2021-06-24T17:22:51Z"
    managedFields:
    - apiVersion: storage.k8s.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:ownerReferences:
            .: {}
            k:{"uid":"d4ea7891-28fe-47e7-aa40-68e8cf6f26b7"}:
              .: {}
              f:apiVersion: {}
              f:kind: {}
              f:name: {}
              f:uid: {}
      manager: kubelet
      operation: Update
      time: "2021-06-24T17:22:51Z"
    name: orm01-ctl-vault2
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: orm01-ctl-vault2
      uid: d4ea7891-28fe-47e7-aa40-68e8cf6f26b7
    resourceVersion: "17731"
    uid: ee67401e-d93b-435a-ab03-7ca3c963bfdb
  spec:
    drivers: null
- apiVersion: storage.k8s.io/v1
  kind: CSINode
  metadata:
    creationTimestamp: "2021-06-24T17:32:16Z"
    managedFields:
    - apiVersion: storage.k8s.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:ownerReferences:
            .: {}
            k:{"uid":"d5078036-fbdf-4ddc-9605-8f5ee110c07a"}:
              .: {}
              f:apiVersion: {}
              f:kind: {}
              f:name: {}
              f:uid: {}
      manager: kubelet
      operation: Update
      time: "2021-06-24T17:32:16Z"
    name: orm01-etcd-vault2
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: orm01-etcd-vault2
      uid: d5078036-fbdf-4ddc-9605-8f5ee110c07a
    resourceVersion: "19568"
    uid: 14f82699-8865-410a-aac5-994176f03f16
  spec:
    drivers: null
- apiVersion: storage.k8s.io/v1
  kind: CSINode
  metadata:
    creationTimestamp: "2021-06-24T16:19:17Z"
    managedFields:
    - apiVersion: storage.k8s.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:ownerReferences:
            .: {}
            k:{"uid":"f74ca919-fe32-42cc-971d-e331b1f501a3"}:
              .: {}
              f:apiVersion: {}
              f:kind: {}
              f:name: {}
              f:uid: {}
      manager: kubelet
      operation: Update
      time: "2021-06-24T16:19:17Z"
    name: orm01-vault1
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: orm01-vault1
      uid: f74ca919-fe32-42cc-971d-e331b1f501a3
    resourceVersion: "5712"
    uid: 76d4cf11-d63a-4afe-b6dc-ae8e918a0a6d
  spec:
    drivers: null
- apiVersion: storage.k8s.io/v1
  kind: CSINode
  metadata:
    creationTimestamp: "2021-06-24T16:03:40Z"
    managedFields:
    - apiVersion: storage.k8s.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:ownerReferences:
            .: {}
            k:{"uid":"9aa0c223-bbee-4585-867d-9dffe6103077"}:
              .: {}
              f:apiVersion: {}
              f:kind: {}
              f:name: {}
              f:uid: {}
      manager: kubelet
      operation: Update
      time: "2021-06-24T16:03:40Z"
    name: orm01-vault2
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: orm01-vault2
      uid: 9aa0c223-bbee-4585-867d-9dffe6103077
    resourceVersion: "3112"
    uid: 2b7aaf50-4b72-41a8-a320-f50df2c19911
  spec:
    drivers: null
- apiVersion: storage.k8s.io/v1
  kind: CSINode
  metadata:
    creationTimestamp: "2021-06-24T16:34:49Z"
    managedFields:
    - apiVersion: storage.k8s.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:ownerReferences:
            .: {}
            k:{"uid":"2df2a2e7-f9d8-4a15-ab96-4d594db6dd1f"}:
              .: {}
              f:apiVersion: {}
              f:kind: {}
              f:name: {}
              f:uid: {}
      manager: kubelet
      operation: Update
      time: "2021-06-24T16:34:49Z"
    name: orm01-vault4
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: orm01-vault4
      uid: 2df2a2e7-f9d8-4a15-ab96-4d594db6dd1f
    resourceVersion: "8616"
    uid: 7ab7f5cf-6c67-4f86-8b90-f34c15bf5919
  spec:
    drivers: null
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Here are the logs with lines like Successfully synced 'openebs/orm01-vault2' pruned:
k logs -n kube-system openebs-lvm-node-bx2v5 openebs-lvm-plugin|grep -v Successfully
I0625 01:31:17.318625       1 main.go:122] LVM Driver Version :- 0.6.0 - commit :- aa439a1e26484f0ba00ccac1aca73f5c2de64e5d
I0625 01:31:17.318742       1 main.go:123] DriverName: local.csi.openebs.io Plugin: agent EndPoint: unix:///plugin/csi.sock NodeID: orm01-vault2 SetIOLimits: false ContainerRuntime: containerd RIopsPerGB: [] WIopsPerGB: [] RBpsPerGB: [] WBpsPerGB: []
I0625 01:31:17.318774       1 driver.go:48] enabling volume access mode: SINGLE_NODE_WRITER
I0625 01:31:17.319543       1 grpc.go:190] Listening for connections on address: &net.UnixAddr{Name:"//plugin/csi.sock", Net:"unix"}
I0625 01:31:17.324436       1 builder.go:107] Creating event broadcaster
I0625 01:31:17.331698       1 snapshot.go:165] Starting Snap controller
I0625 01:31:17.331743       1 snapshot.go:168] Waiting for informer caches to sync
I0625 01:31:17.331715       1 builder.go:107] Creating event broadcaster
I0625 01:31:17.331914       1 volume.go:265] Starting Vol controller
I0625 01:31:17.331927       1 volume.go:268] Waiting for informer caches to sync
I0625 01:31:17.384800       1 builder.go:116] Creating event broadcaster
I0625 01:31:17.385007       1 lvmnode.go:191] Starting Node controller
I0625 01:31:17.385025       1 lvmnode.go:194] Waiting for informer caches to sync
I0625 01:31:17.532046       1 snapshot.go:172] Starting Snap workers
I0625 01:31:17.532126       1 snapshot.go:179] Started Snap workers
I0625 01:31:17.621354       1 grpc.go:72] GRPC call: /csi.v1.Identity/GetPluginInfo requests {}
I0625 01:31:17.624229       1 grpc.go:81] GRPC response: {"name":"local.csi.openebs.io","vendor_version":"0.6.0"}
I0625 01:31:17.632789       1 volume.go:272] Starting Vol workers
I0625 01:31:17.632845       1 volume.go:279] Started Vol workers
I0625 01:31:17.785205       1 lvmnode.go:199] Starting Node workers
I0625 01:31:17.785286       1 lvmnode.go:206] Started Node workers
I0625 01:31:17.865993       1 lvmnode.go:80] lvm node controller: creating new node object for &{TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:orm01-vault2 GenerateName: Namespace:openebs SelfLink: UID: ResourceVersion: Generation:0 CreationTimestamp:0001-01-01 00:00:00 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[] Annotations:map[] OwnerReferences:[{APIVersion:v1 Kind:Node Name:orm01-vault2 UID:9aa0c223-bbee-4585-867d-9dffe6103077 Controller:0xc000131350 BlockOwnerDeletion:<nil>}] Finalizers:[] ClusterName: ManagedFields:[]} VolumeGroups:[]}
I0625 01:31:17.926965       1 lvmnode.go:127] Got add event for lvm node openebs/orm01-vault2
I0625 01:31:17.930365       1 lvmnode.go:84] lvm node controller: created node object openebs/orm01-vault2
I0625 01:37:17.895843       1 lvmnode.go:100] lvm node controller: node volume groups updated current=[], required=[{Name:lvmvg UUID:wioPDs-suYm-P119-Wiec-Trd5-Nr6N-tpKjkC Size:{i:{value:35752247296 scale:0} d:{Dec:<nil>} s: Format:BinarySI} Free:{i:{value:35752247296 scale:0} d:{Dec:<nil>} s: Format:BinarySI} LVCount:0 PVCount:1}]
I0625 01:37:17.896382       1 lvmnode.go:110] lvm node controller: updating node object with &{TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:orm01-vault2 GenerateName: Namespace:openebs SelfLink: UID:5f13269f-1b16-4082-b2d8-0e0f19861820 ResourceVersion:122532 Generation:1 CreationTimestamp:2021-06-25 01:31:17 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[] Annotations:map[] OwnerReferences:[{APIVersion:v1 Kind:Node Name:orm01-vault2 UID:9aa0c223-bbee-4585-867d-9dffe6103077 Controller:0xc00058cf08 BlockOwnerDeletion:<nil>}] Finalizers:[] ClusterName: ManagedFields:[{Manager:lvm-driver Operation:Update APIVersion:local.openebs.io/v1alpha1 Time:2021-06-25 01:31:17 +0000 UTC FieldsType:FieldsV1 FieldsV1:{"f:metadata":{"f:ownerReferences":{}},"f:volumeGroups":{}}}]} VolumeGroups:[{Name:lvmvg UUID:wioPDs-suYm-P119-Wiec-Trd5-Nr6N-tpKjkC Size:{i:{value:35752247296 scale:0} d:{Dec:<nil>} s: Format:BinarySI} Free:{i:{value:35752247296 scale:0} d:{Dec:<nil>} s: Format:BinarySI} LVCount:0 PVCount:1}]}
I0625 01:37:17.993465       1 lvmnode.go:114] lvm node controller: updated node object openebs/orm01-vault2
I0625 01:37:17.993556       1 lvmnode.go:139] Got update event for lvm node openebs/orm01-vault2

k logs -n kube-system openebs-lvm-node-krmw8 openebs-lvm-plugin|grep -v Successfully
I0625 01:31:15.236729       1 main.go:122] LVM Driver Version :- 0.6.0 - commit :- aa439a1e26484f0ba00ccac1aca73f5c2de64e5d
I0625 01:31:15.236899       1 main.go:123] DriverName: local.csi.openebs.io Plugin: agent EndPoint: unix:///plugin/csi.sock NodeID: orm01-vault4 SetIOLimits: false ContainerRuntime: containerd RIopsPerGB: [] WIopsPerGB: [] RBpsPerGB: [] WBpsPerGB: []
I0625 01:31:15.236954       1 driver.go:48] enabling volume access mode: SINGLE_NODE_WRITER
I0625 01:31:15.238140       1 grpc.go:190] Listening for connections on address: &net.UnixAddr{Name:"//plugin/csi.sock", Net:"unix"}
I0625 01:31:15.249934       1 builder.go:107] Creating event broadcaster
I0625 01:31:15.250879       1 snapshot.go:165] Starting Snap controller
I0625 01:31:15.251194       1 snapshot.go:168] Waiting for informer caches to sync
I0625 01:31:15.262468       1 builder.go:107] Creating event broadcaster
I0625 01:31:15.263008       1 volume.go:265] Starting Vol controller
I0625 01:31:15.263140       1 volume.go:268] Waiting for informer caches to sync
I0625 01:31:15.653647       1 grpc.go:72] GRPC call: /csi.v1.Identity/GetPluginInfo requests {}
I0625 01:31:15.658296       1 grpc.go:81] GRPC response: {"name":"local.csi.openebs.io","vendor_version":"0.6.0"}
I0625 01:31:16.561029       1 builder.go:116] Creating event broadcaster
I0625 01:31:16.561284       1 lvmnode.go:191] Starting Node controller
I0625 01:31:16.561300       1 lvmnode.go:194] Waiting for informer caches to sync
I0625 01:31:16.653425       1 snapshot.go:172] Starting Snap workers
I0625 01:31:16.653468       1 snapshot.go:179] Started Snap workers
I0625 01:31:16.663527       1 volume.go:272] Starting Vol workers
I0625 01:31:16.663580       1 volume.go:279] Started Vol workers
I0625 01:31:16.861934       1 lvmnode.go:199] Starting Node workers
I0625 01:31:16.862073       1 lvmnode.go:206] Started Node workers
I0625 01:31:16.944582       1 lvmnode.go:80] lvm node controller: creating new node object for &{TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:orm01-vault4 GenerateName: Namespace:openebs SelfLink: UID: ResourceVersion: Generation:0 CreationTimestamp:0001-01-01 00:00:00 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[] Annotations:map[] OwnerReferences:[{APIVersion:v1 Kind:Node Name:orm01-vault4 UID:2df2a2e7-f9d8-4a15-ab96-4d594db6dd1f Controller:0xc00058e370 BlockOwnerDeletion:<nil>}] Finalizers:[] ClusterName: ManagedFields:[]} VolumeGroups:[]}
I0625 01:31:16.995149       1 lvmnode.go:127] Got add event for lvm node openebs/orm01-vault4
I0625 01:31:17.018545       1 lvmnode.go:84] lvm node controller: created node object openebs/orm01-vault4
I0625 01:41:16.980146       1 lvmnode.go:100] lvm node controller: node volume groups updated current=[], required=[{Name:lvmvg UUID:JGpMU8-NQnw-c5Kg-tdoR-bxbB-pCvu-rRpHG2 Size:{i:{value:107260936192 scale:0} d:{Dec:<nil>} s: Format:BinarySI} Free:{i:{value:107260936192 scale:0} d:{Dec:<nil>} s: Format:BinarySI} LVCount:0 PVCount:1}]
I0625 01:41:16.980370       1 lvmnode.go:110] lvm node controller: updating node object with &{TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:orm01-vault4 GenerateName: Namespace:openebs SelfLink: UID:ae13fe9e-e685-4496-97cf-0053d4b134a6 ResourceVersion:122521 Generation:1 CreationTimestamp:2021-06-25 01:31:16 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[] Annotations:map[] OwnerReferences:[{APIVersion:v1 Kind:Node Name:orm01-vault4 UID:2df2a2e7-f9d8-4a15-ab96-4d594db6dd1f Controller:0xc000138000 BlockOwnerDeletion:<nil>}] Finalizers:[] ClusterName: ManagedFields:[{Manager:lvm-driver Operation:Update APIVersion:local.openebs.io/v1alpha1 Time:2021-06-25 01:31:16 +0000 UTC FieldsType:FieldsV1 FieldsV1:{"f:metadata":{"f:ownerReferences":{}},"f:volumeGroups":{}}}]} VolumeGroups:[{Name:lvmvg UUID:JGpMU8-NQnw-c5Kg-tdoR-bxbB-pCvu-rRpHG2 Size:{i:{value:107260936192 scale:0} d:{Dec:<nil>} s: Format:BinarySI} Free:{i:{value:107260936192 scale:0} d:{Dec:<nil>} s: Format:BinarySI} LVCount:0 PVCount:1}]}
I0625 01:41:17.009632       1 lvmnode.go:114] lvm node controller: updated node object openebs/orm01-vault4
I0625 01:41:17.010411       1 lvmnode.go:139] Got update event for lvm node openebs/orm01-vault4

k logs -n kube-system openebs-lvm-node-xg5bk openebs-lvm-plugin|grep -v Successfully
I0625 01:31:17.062856       1 main.go:122] LVM Driver Version :- 0.6.0 - commit :- aa439a1e26484f0ba00ccac1aca73f5c2de64e5d
I0625 01:31:17.062979       1 main.go:123] DriverName: local.csi.openebs.io Plugin: agent EndPoint: unix:///plugin/csi.sock NodeID: orm01-vault1 SetIOLimits: false ContainerRuntime: containerd RIopsPerGB: [] WIopsPerGB: [] RBpsPerGB: [] WBpsPerGB: []
I0625 01:31:17.063018       1 driver.go:48] enabling volume access mode: SINGLE_NODE_WRITER
I0625 01:31:17.063658       1 grpc.go:190] Listening for connections on address: &net.UnixAddr{Name:"//plugin/csi.sock", Net:"unix"}
I0625 01:31:17.088016       1 builder.go:107] Creating event broadcaster
I0625 01:31:17.088751       1 volume.go:265] Starting Vol controller
I0625 01:31:17.088770       1 volume.go:268] Waiting for informer caches to sync
I0625 01:31:17.094422       1 builder.go:107] Creating event broadcaster
I0625 01:31:17.094742       1 snapshot.go:165] Starting Snap controller
I0625 01:31:17.094761       1 snapshot.go:168] Waiting for informer caches to sync
I0625 01:31:17.162007       1 builder.go:116] Creating event broadcaster
I0625 01:31:17.162484       1 lvmnode.go:191] Starting Node controller
I0625 01:31:17.162504       1 lvmnode.go:194] Waiting for informer caches to sync
I0625 01:31:17.188970       1 volume.go:272] Starting Vol workers
I0625 01:31:17.189060       1 volume.go:279] Started Vol workers
I0625 01:31:17.203866       1 snapshot.go:172] Starting Snap workers
I0625 01:31:17.204107       1 snapshot.go:179] Started Snap workers
I0625 01:31:17.264978       1 lvmnode.go:199] Starting Node workers
I0625 01:31:17.265045       1 lvmnode.go:206] Started Node workers
I0625 01:31:17.358677       1 lvmnode.go:80] lvm node controller: creating new node object for &{TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:orm01-vault1 GenerateName: Namespace:openebs SelfLink: UID: ResourceVersion: Generation:0 CreationTimestamp:0001-01-01 00:00:00 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[] Annotations:map[] OwnerReferences:[{APIVersion:v1 Kind:Node Name:orm01-vault1 UID:f74ca919-fe32-42cc-971d-e331b1f501a3 Controller:0xc000049540 BlockOwnerDeletion:<nil>}] Finalizers:[] ClusterName: ManagedFields:[]} VolumeGroups:[{Name:lvmvg UUID:hg4sp7-zAFF-2v1J-735X-EEOB-J038-7HDOUR Size:{i:{value:35752247296 scale:0} d:{Dec:<nil>} s: Format:BinarySI} Free:{i:{value:35752247296 scale:0} d:{Dec:<nil>} s: Format:BinarySI} LVCount:0 PVCount:1}]}
I0625 01:31:17.397420       1 lvmnode.go:127] Got add event for lvm node openebs/orm01-vault1
I0625 01:31:17.413695       1 lvmnode.go:84] lvm node controller: created node object openebs/orm01-vault1
I0625 01:31:17.493650       1 grpc.go:72] GRPC call: /csi.v1.Identity/GetPluginInfo requests {}
I0625 01:31:17.527359       1 grpc.go:81] GRPC response: {"name":"local.csi.openebs.io","vendor_version":"0.6.0"}

@joshuacox spec.drivers in CSInode object is null. That means lvm driver is not able to register. Can you get me the driver-registrar log from the node daemonset pod openebs-lvm-node-xg5bk.

k logs -n kube-system openebs-lvm-node-xg5bk csi-node-driver-registrar
I0625 01:31:03.752297       1 main.go:113] Version: v2.1.0
I0625 01:31:03.755912       1 main.go:137] Attempting to open a gRPC connection with: "/plugin/csi.sock"
I0625 01:31:03.755975       1 connection.go:153] Connecting to unix:///plugin/csi.sock
W0625 01:31:13.761226       1 connection.go:172] Still connecting to unix:///plugin/csi.sock
I0625 01:31:17.456959       1 main.go:144] Calling CSI driver to discover driver name
I0625 01:31:17.457223       1 connection.go:182] GRPC call: /csi.v1.Identity/GetPluginInfo
I0625 01:31:17.457439       1 connection.go:183] GRPC request: {}
I0625 01:31:17.528581       1 connection.go:185] GRPC response: {"name":"local.csi.openebs.io","vendor_version":"0.6.0"}
I0625 01:31:17.528754       1 connection.go:186] GRPC error: <nil>
I0625 01:31:17.528801       1 main.go:154] CSI driver name: "local.csi.openebs.io"
I0625 01:31:17.529015       1 node_register.go:52] Starting Registration Server at: /registration/local.csi.openebs.io-reg.sock
I0625 01:31:17.529514       1 node_register.go:61] Registration Server started at: /registration/local.csi.openebs.io-reg.sock
I0625 01:31:17.529767       1 node_register.go:83] Skipping healthz server because HTTP endpoint is set to: ""

And here are the other two:
k logs -n kube-system openebs-lvm-node-krmw8 csi-node-driver-registrar
I0625 01:31:02.856962       1 main.go:113] Version: v2.1.0
I0625 01:31:02.858405       1 main.go:137] Attempting to open a gRPC connection with: "/plugin/csi.sock"
I0625 01:31:02.858462       1 connection.go:153] Connecting to unix:///plugin/csi.sock
W0625 01:31:12.858763       1 connection.go:172] Still connecting to unix:///plugin/csi.sock
I0625 01:31:15.647379       1 main.go:144] Calling CSI driver to discover driver name
I0625 01:31:15.647430       1 connection.go:182] GRPC call: /csi.v1.Identity/GetPluginInfo
I0625 01:31:15.647441       1 connection.go:183] GRPC request: {}
I0625 01:31:15.659639       1 connection.go:185] GRPC response: {"name":"local.csi.openebs.io","vendor_version":"0.6.0"}
I0625 01:31:15.659816       1 connection.go:186] GRPC error: <nil>
I0625 01:31:15.659854       1 main.go:154] CSI driver name: "local.csi.openebs.io"
I0625 01:31:15.660382       1 node_register.go:52] Starting Registration Server at: /registration/local.csi.openebs.io-reg.sock
I0625 01:31:15.660863       1 node_register.go:61] Registration Server started at: /registration/local.csi.openebs.io-reg.sock
I0625 01:31:15.661228       1 node_register.go:83] Skipping healthz server because HTTP endpoint is set to: ""

k logs -n kube-system openebs-lvm-node-krmw8 csi-node-driver-registrar
I0625 01:31:02.856962       1 main.go:113] Version: v2.1.0
I0625 01:31:02.858405       1 main.go:137] Attempting to open a gRPC connection with: "/plugin/csi.sock"
I0625 01:31:02.858462       1 connection.go:153] Connecting to unix:///plugin/csi.sock
W0625 01:31:12.858763       1 connection.go:172] Still connecting to unix:///plugin/csi.sock
I0625 01:31:15.647379       1 main.go:144] Calling CSI driver to discover driver name
I0625 01:31:15.647430       1 connection.go:182] GRPC call: /csi.v1.Identity/GetPluginInfo
I0625 01:31:15.647441       1 connection.go:183] GRPC request: {}
I0625 01:31:15.659639       1 connection.go:185] GRPC response: {"name":"local.csi.openebs.io","vendor_version":"0.6.0"}
I0625 01:31:15.659816       1 connection.go:186] GRPC error: <nil>
I0625 01:31:15.659854       1 main.go:154] CSI driver name: "local.csi.openebs.io"
I0625 01:31:15.660382       1 node_register.go:52] Starting Registration Server at: /registration/local.csi.openebs.io-reg.sock
I0625 01:31:15.660863       1 node_register.go:61] Registration Server started at: /registration/local.csi.openebs.io-reg.sock
I0625 01:31:15.661228       1 node_register.go:83] Skipping healthz server because HTTP endpoint is set to: ""

Which look the same to me.

@pawanpraka1  In an attempt to start from scratch I uninstalled openebs by removing the app in the rancher interface and then reinstall, I quickly ran into some borkage where I couldn't create the test pvc:
k apply -f /tmp/test.yml
Error from server (InternalError): error when creating "/tmp/test.yml": Internal error occurred: failed calling webhook "admission-webhook.ope
nebs.io": Post "https://admission-server-svc.openebs.svc:443/validate?timeout=5s": x509: certificate signed by unknown authority (possibly bec
ause of "crypto/rsa: verification error" while trying to verify candidate authority certificate "admission-server-svc-ca")

Which is similar to an error I missed on uninstall:
Error from server (InternalError): error when deleting "https://raw.githubusercontent.com/openebs/lvm-localpv/master/deploy/lvm-operator.yaml"
: Internal error occurred: failed calling webhook "admission-webhook.openebs.io": Post "https://admission-server-svc.openebs.svc:443/validate?
timeout=5s": x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candid
ate authority certificate "admission-server-svc-ca")

Anyhow, I have blown away the entire installation and started from scratch to achieve the same results of no provisions:
$ k logs -n kube-system openebs-lvm-node-cc582 csi-node-driver-registrar
I0625 22:14:57.324167       1 main.go:113] Version: v2.1.0
I0625 22:14:57.325160       1 main.go:137] Attempting to open a gRPC connection with: "/plugin/csi.sock"
I0625 22:14:57.329402       1 connection.go:153] Connecting to unix:///plugin/csi.sock
W0625 22:15:07.329633       1 connection.go:172] Still connecting to unix:///plugin/csi.sock
I0625 22:15:10.309656       1 main.go:144] Calling CSI driver to discover driver name
I0625 22:15:10.309706       1 connection.go:182] GRPC call: /csi.v1.Identity/GetPluginInfo
I0625 22:15:10.309723       1 connection.go:183] GRPC request: {}
I0625 22:15:10.325115       1 connection.go:185] GRPC response: {"name":"local.csi.openebs.io","vendor_version":"master-e12ad25:06-24-2021"}
I0625 22:15:10.325280       1 connection.go:186] GRPC error: <nil>
I0625 22:15:10.325305       1 main.go:154] CSI driver name: "local.csi.openebs.io"
I0625 22:15:10.325451       1 node_register.go:52] Starting Registration Server at: /registration/local.csi.openebs.io-reg.sock
I0625 22:15:10.325791       1 node_register.go:61] Registration Server started at: /registration/local.csi.openebs.io-reg.sock
I0625 22:15:10.326363       1 node_register.go:83] Skipping healthz server because HTTP endpoint is set to: ""

k describe pvc data-whc01elastic-opendistro-es-data-0
Name:          data-whc01elastic-opendistro-es-data-0
Namespace:     default
StorageClass:  openebs-lvmpv
Status:        Pending
Volume:
Labels:        app=whc01elastic-opendistro-es
               heritage=Helm
               release=whc01elastic
               role=data
Annotations:   volume.beta.kubernetes.io/storage-provisioner: local.csi.openebs.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Mounted By:    whc01elastic-opendistro-es-data-0
Events:
  Type     Reason                Age                     From                                                                                Message
  ----     ------                ----                    ----                                                                                -------
  Warning  ProvisioningFailed    25m (x204 over 16h)     local.csi.openebs.io_openebs-lvm-controller-0_3b8c9134-e0f0-4ddd-8efc-5aabf1e841b2  failed to provision volume with StorageClass "openebs-lvmpv": error generating accessibility requirements: no available topology found
  Normal   ExternalProvisioning  2m41s (x4001 over 16h)  persistentvolume-controller                                                         waiting for a volume to be created, either by external provisioner "local.csi.openebs.io" or manually created by system administrator
  Normal   Provisioning          48s (x209 over 16h)     local.csi.openebs.io_openebs-lvm-controller-0_3b8c9134-e0f0-4ddd-8efc-5aabf1e841b2  External provisioner is provisioning volume for claim "default/data-whc01elastic-opendistro-es-data-0"

k describe sc
Name:            openebs-device
IsDefaultClass:  No
Annotations:     cas.openebs.io/config=- name: StorageType
  value: "device"
,openebs.io/cas-type=local
Provisioner:           openebs.io/local
Parameters:            <none>
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     WaitForFirstConsumer
Events:                <none>

Name:            openebs-hostpath
IsDefaultClass:  No
Annotations:     cas.openebs.io/config=- name: StorageType
  value: "hostpath"
- name: BasePath
  value: /var/openebs/local
,openebs.io/cas-type=local
Provisioner:           openebs.io/local
Parameters:            <none>
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     WaitForFirstConsumer
Events:                <none>

Name:            openebs-jiva-default
IsDefaultClass:  No
Annotations:     cas.openebs.io/config=- name: ReplicaCount
  value: "3"
- name: StoragePool
  value: default
#- name: TargetResourceLimits
#  value: |-
#      memory: 1Gi
#      cpu: 100m
#- name: AuxResourceLimits
#  value: |-
#      memory: 0.5Gi
#      cpu: 50m
#- name: ReplicaResourceLimits
#  value: |-
#      memory: 2Gi
,openebs.io/cas-type=jiva
Provisioner:           openebs.io/provisioner-iscsi
Parameters:            <none>
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     Immediate
Events:                <none>

Name:            openebs-lvmpv
IsDefaultClass:  Yes
Annotations:     kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"storage.k8s.io/v1","kind":"StorageClass","metadata":{"annotations":{},"name":"openebs-lvmpv"},"parameters":{"storage":"lvm","volgroup":"lvmvg"},"provisioner":"local.csi.openebs.io"}
,storageclass.kubernetes.io/is-default-class=true
Provisioner:           local.csi.openebs.io
Parameters:            storage=lvm,volgroup=lvmvg
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     Immediate
Events:                <none>

Name:                  openebs-snapshot-promoter
IsDefaultClass:        No
Annotations:           <none>
Provisioner:           volumesnapshot.external-storage.k8s.io/snapshot-promoter
Parameters:            <none>
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     Immediate
Events:                <none>

@joshuacox, it seems like driver registration is not happening. Can you add the following directory mapping to the services_kubelet->extra_binds section of the cluster'scluster.yml file.
/opt/rke/var/lib/kubelet/plugins:/var/lib/kubelet/plugins

The LVM CSI deployment uses /var/lib/kubelet as kubelet directory (https://github.com/openebs/lvm-localpv/blob/master/deploy/lvm-operator.yaml#L1388).

@pawanpraka1  Where do I add this binding?

@joshuacox you can update cluster.yml file with extra
services:
    kubelet:
      extra_binds:
        - "/opt/rke/var/lib/kubelet/:/var/lib/kubelet/"

you can do the same using rancher UI by editing the yaml (see this https://forums.rancher.com/t/solved-rancher-agent-kubelet-extra-binds/14658/2).

@pawanpraka1  hmm, still no luck, I went ahead and blew everything away and started again from scratch.  But still stuck in pending:
k get pvc
NAME                                       STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS    AGE
data-whc01elastic-opendistro-es-data-0     Pending                                      openebs-lvmpv   8m26s
data-whc01elastic-opendistro-es-master-0   Pending                                      openebs-lvmpv   8m26s

here is my full cluster.yml
answers: {}
docker_root_dir: /var/lib/docker
enable_cluster_alerting: false
enable_cluster_monitoring: true
enable_network_policy: false
fleet_workspace_name: fleet-default
local_cluster_auth_endpoint:
  enabled: true
name: carbon6
rancher_kubernetes_engine_config:
  addon_job_timeout: 45
  authentication:
    strategy: x509|webhook
  authorization: {}
  bastion_host:
    ssh_agent_auth: false
  cloud_provider: {}
  dns:
    linear_autoscaler_params: {}
    node_selector: null
    nodelocal:
      node_selector: null
      update_strategy:
        rolling_update: {}
    options: null
    reversecidrs: null
    stubdomains: null
    tolerations: null
    update_strategy: {}
    upstreamnameservers: null
  ignore_docker_version: true
  ingress:
    default_backend: true
    http_port: 0
    https_port: 0
    provider: nginx
  kubernetes_version: v1.20.8-rancher1-1
  monitoring:
    provider: metrics-server
    replicas: 1
  network:
    mtu: 0
    options:
      flannel_backend_type: vxlan
    plugin: flannel
  restore:
    restore: false
  rotate_encryption_key: false
  services:
    etcd:
      backup_config:
        enabled: true
        interval_hours: 12
        retention: 6
        safe_timestamp: false
        timeout: 300
      creation: 12h
      extra_args:
        election-timeout: '5000'
        heartbeat-interval: '500'
      gid: 0
      retention: 72h
      snapshot: false
      uid: 0
    kube-api:
      always_pull_images: false
      pod_security_policy: false
      secrets_encryption_config:
        enabled: false
      service_node_port_range: 30000-32767
    kube-controller: {}
    kubelet:
      extra_binds:
        - '/opt/rke/var/lib/kubelet/:/var/lib/kubelet/'
      fail_swap_on: false
      generate_serving_certificate: false
    kubeproxy: {}
    scheduler: {}
  ssh_agent_auth: false
  upgrade_strategy:
    max_unavailable_controlplane: '1'
    max_unavailable_worker: 10%
    node_drain_input:
      delete_local_data: false
      force: false
      grace_period: -1
      ignore_daemon_sets: true
      timeout: 120

k describe pvc
Name:          data-whc01elastic-opendistro-es-data-0
Namespace:     default
StorageClass:  openebs-lvmpv
Status:        Pending
Volume:
Labels:        app=whc01elastic-opendistro-es
               heritage=Helm
               release=whc01elastic
               role=data
Annotations:   volume.beta.kubernetes.io/storage-provisioner: local.csi.openebs.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Mounted By:    whc01elastic-opendistro-es-data-0
Events:
  Type     Reason                Age                    From                                                                                Message
  ----     ------                ----                   ----                                                                                -------
  Normal   Provisioning          3m40s (x7 over 4m43s)  local.csi.openebs.io_openebs-lvm-controller-0_fbbbbca9-5131-4fd5-9bef-f5c6be53cdf0  External provisioner is provisioning volume for claim "default/data-whc01elastic-opendistro-es-data-0"
  Warning  ProvisioningFailed    3m40s (x7 over 4m43s)  local.csi.openebs.io_openebs-lvm-controller-0_fbbbbca9-5131-4fd5-9bef-f5c6be53cdf0  failed to provision volume with StorageClass "openebs-lvmpv": error generating accessibility requirements: no available topology found
  Normal   Provisioning          67s (x8 over 3m14s)    local.csi.openebs.io_openebs-lvm-controller-0_16e20de8-b1d0-4e1e-a77b-f1d63026c5a0  External provisioner is provisioning volume for claim "default/data-whc01elastic-opendistro-es-data-0"
  Warning  ProvisioningFailed    67s (x8 over 3m14s)    local.csi.openebs.io_openebs-lvm-controller-0_16e20de8-b1d0-4e1e-a77b-f1d63026c5a0  failed to provision volume with StorageClass "openebs-lvmpv": error generating accessibility requirements: no available topology found
  Normal   ExternalProvisioning  5s (x20 over 4m43s)    persistentvolume-controller                                                         waiting for a volume to be created, either by external provisioner "local.csi.openebs.io" or manually created by system administrator

Name:          data-whc01elastic-opendistro-es-master-0
Namespace:     default
StorageClass:  openebs-lvmpv
Status:        Pending
Volume:
Labels:        app=whc01elastic-opendistro-es
               heritage=Helm
               release=whc01elastic
               role=master
Annotations:   volume.beta.kubernetes.io/storage-provisioner: local.csi.openebs.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Mounted By:    whc01elastic-opendistro-es-master-0
Events:
  Type     Reason                Age                    From                                                                                Message
  ----     ------                ----                   ----                                                                                -------
  Normal   Provisioning          3m40s (x7 over 4m43s)  local.csi.openebs.io_openebs-lvm-controller-0_fbbbbca9-5131-4fd5-9bef-f5c6be53cdf0  External provisioner is provisioning volume for claim "default/data-whc01elastic-opendistro-es-master-0"
  Warning  ProvisioningFailed    3m40s (x7 over 4m43s)  local.csi.openebs.io_openebs-lvm-controller-0_fbbbbca9-5131-4fd5-9bef-f5c6be53cdf0  failed to provision volume with StorageClass "openebs-lvmpv": error generating accessibility requirements: no available topology found
  Normal   Provisioning          67s (x8 over 3m14s)    local.csi.openebs.io_openebs-lvm-controller-0_16e20de8-b1d0-4e1e-a77b-f1d63026c5a0  External provisioner is provisioning volume for claim "default/data-whc01elastic-opendistro-es-master-0"
  Warning  ProvisioningFailed    67s (x8 over 3m14s)    local.csi.openebs.io_openebs-lvm-controller-0_16e20de8-b1d0-4e1e-a77b-f1d63026c5a0  failed to provision volume with StorageClass "openebs-lvmpv": error generating accessibility requirements: no available topology found
  Normal   ExternalProvisioning  5s (x21 over 4m43s)    persistentvolume-controller                                                         waiting for a volume to be created, either by external provisioner "local.csi.openebs.io" or manually created by system administrator

 k logs -n kube-system openebs-lvm-node-8wjk5 openebs-lvm-plugin|grep -v Successfully
I0628 22:30:30.803524       1 main.go:136] LVM Driver Version :- master-15a2c7c:06-28-2021 - commit :- 15a2c7c296a4743ce5fb233baefaf45658531afc
I0628 22:30:30.803664       1 main.go:137] DriverName: local.csi.openebs.io Plugin: agent EndPoint: unix:///plugin/csi.sock NodeID: carbon6-vault4 SetIOLimits: false ContainerRuntime: containerd RIopsPerGB: [] WIopsPerGB: [] RBpsPerGB: [] WBpsPerGB: []
I0628 22:30:30.803702       1 driver.go:48] enabling volume access mode: SINGLE_NODE_WRITER
I0628 22:30:30.805897       1 grpc.go:190] Listening for connections on address: &net.UnixAddr{Name:"//plugin/csi.sock", Net:"unix"}
I0628 22:30:30.810551       1 builder.go:107] Creating event broadcaster
I0628 22:30:30.811105       1 snapshot.go:165] Starting Snap controller
I0628 22:30:30.811124       1 snapshot.go:168] Waiting for informer caches to sync
I0628 22:30:30.811106       1 builder.go:107] Creating event broadcaster
I0628 22:30:30.811560       1 volume.go:265] Starting Vol controller
I0628 22:30:30.827828       1 volume.go:268] Waiting for informer caches to sync
I0628 22:30:31.111656       1 snapshot.go:172] Starting Snap workers
I0628 22:30:31.111704       1 snapshot.go:179] Started Snap workers
I0628 22:30:31.128157       1 volume.go:272] Starting Vol workers
I0628 22:30:31.128229       1 volume.go:279] Started Vol workers
I0628 22:30:31.157087       1 builder.go:116] Creating event broadcaster
I0628 22:30:31.157769       1 lvmnode.go:191] Starting Node controller
I0628 22:30:31.157785       1 lvmnode.go:194] Waiting for informer caches to sync
I0628 22:30:31.260529       1 lvmnode.go:199] Starting Node workers
I0628 22:30:31.268490       1 lvmnode.go:206] Started Node workers
I0628 22:30:31.469153       1 lvmnode.go:80] lvm node controller: creating new node object for &{TypeMeta:{Kind: APIVersion:} ObjectMeta:{Name:carbon6-vault4 GenerateName: Namespace:openebs SelfLink: UID: ResourceVersion: Generation:0 CreationTimestamp:0001-01-01 00:00:00 +0000 UTC DeletionTimestamp:<nil> DeletionGracePeriodSeconds:<nil> Labels:map[] Annotations:map[] OwnerReferences:[{APIVersion:v1 Kind:Node Name:carbon6-vault4 UID:59374be9-75a5-4884-8a72-c1e046f32e93 Controller:0xc0000496d0 BlockOwnerDeletion:<nil>}] Finalizers:[] ClusterName: ManagedFields:[]} VolumeGroups:[{Name:lvmvg UUID:AVaEkD-9bYT-qAVS-Hlgt-cIF4-eaYR-dNYo0f Size:{i:{value:107265130496 scale:0} d:{Dec:<nil>} s: Format:BinarySI} Free:{i:{value:107265130496 scale:0} d:{Dec:<nil>} s: Format:BinarySI} LVCount:0 PVCount:1}]}
I0628 22:30:31.496139       1 lvmnode.go:127] Got add event for lvm node openebs/carbon6-vault4
I0628 22:30:31.501878       1 lvmnode.go:84] lvm node controller: created node object openebs/carbon6-vault4
I0628 22:30:31.510939       1 grpc.go:72] GRPC call: /csi.v1.Identity/GetPluginInfo requests {}
I0628 22:30:31.512836       1 grpc.go:81] GRPC response: {"name":"local.csi.openebs.io","vendor_version":"master-15a2c7c:06-28-2021"}

k logs -n kube-system openebs-lvm-node-8wjk5 csi-node-driver-registrar
I0628 22:30:20.466261       1 main.go:113] Version: v2.1.0
I0628 22:30:20.467589       1 main.go:137] Attempting to open a gRPC connection with: "/plugin/csi.sock"
I0628 22:30:20.467764       1 connection.go:153] Connecting to unix:///plugin/csi.sock
W0628 22:30:30.468249       1 connection.go:172] Still connecting to unix:///plugin/csi.sock
I0628 22:30:31.501797       1 main.go:144] Calling CSI driver to discover driver name
I0628 22:30:31.501883       1 connection.go:182] GRPC call: /csi.v1.Identity/GetPluginInfo
I0628 22:30:31.501901       1 connection.go:183] GRPC request: {}
I0628 22:30:31.514198       1 connection.go:185] GRPC response: {"name":"local.csi.openebs.io","vendor_version":"master-15a2c7c:06-28-2021"}
I0628 22:30:31.514593       1 connection.go:186] GRPC error: <nil>
I0628 22:30:31.514936       1 main.go:154] CSI driver name: "local.csi.openebs.io"
I0628 22:30:31.515189       1 node_register.go:52] Starting Registration Server at: /registration/local.csi.openebs.io-reg.sock
I0628 22:30:31.515598       1 node_register.go:61] Registration Server started at: /registration/local.csi.openebs.io-reg.sock
I0628 22:30:31.515883       1 node_register.go:83] Skipping healthz server because HTTP endpoint is set to: ""

hmmmm, @joshuacox Let me check if we have a rancherOS setup in our lab. Will test and update here.

repo: openebs/lvm-localpv


text:
fix(nexus): avoid duplicating replica records when readding replicas

In current implementation there is no check in persistent nexus info against presence of the record for the replica being readded, which leads to multiple records for the same replica being stored in ETCD. The fix adds extra checks to PersistOp::AddChild operation to update existing replica records in place when a replica with the same UUID is readded to nexus.
Signed-off-by: Mikhail Tcymbaliuk mtzaurus@gmail.com

bors try

bors merge

source: gharchive/pull-request

repo: openebs/mayastor

license_type: permissive

license_source: github-api


text:
One of the replica volume is showing pending status

Problem
I am in vagrant/test/k8s/1.6 directory and after creating the volume it shows volume created successfully but when you run vsm-stats ,it shows vol not reachable.
I checked the pods and one of the replica volume is showing pending status,
I checked the nodes also and they are showing Ready status.
Changes i made
Pulled the latest jiva image and changed the tag name from latest to 0.3-RC2
Screenshot
Here is the screenshot attached for more details

It looks as though the volumes were not created properly, does deleting the pod and launching it again solve the problem? Also it is advisable to have 2 minions running to actually see the HA(high availability) working.

Yes, actually i also delete the pods, services and deployments  every time whenever i face this issue.looks like if it is a bug?

The behavior is if you have only 1 Minion, you should be able to see 1 controller pod and 1 replica pod launched. Your application must be able to use the volume provided by the single replica that was launched. Can you confirm whether your application was able to consume the volume that was provided by that single replica?

This is a default provisioning feature via maya api server.
It will spread the replica in different minion hosts.

@yudaykiran , yes it is able to consume the volume. i have tested it with dd command.

You can close the issue now :)

source: gharchive/issue

authors: AmitKumarDas utkarshmani1997 yudaykiran

repo: openebs/openebs


text:
Option to disable free space checks

With thin provisioning it's quite easy to bump into resource exhausted errors.
I ended up disabling some checks
https://git.k-space.ee/k-space/rawfile-localpv/commit/17f653b15ff1edd43473f8c4f3adba33c3703d1a
https://git.k-space.ee/k-space/rawfile-localpv/commit/9c4cda7c0a33b7e1d65cda67608a09f6fe1fae36
Please make this configurable upstream

Those checks are in place to prevent over-provisioning. Are you suggesting that is should be allowed to do so?

I am suggesting making it configurable. I do want over-provisioning

authors: laurivosandi semekh

repo: openebs/rawfile-localpv


text:
feat!: reorder MVs and change data types (FC-0024)

Updates the top-level materialized views in the following ways:

Adds fields to the ORDER BY clause to ensure the entire dataset is migrated during table updates
Truncates emission_time from DateTime64(6), which stores nanosecond granularity, to DateTime, which stores second granularity
Stores video positions as UInt32 (via Decimal32(2)) to avoid the imprecise Float32 type

@SoryRawyer are there any downstream changes in the Superset assets that will be impacted by the type changes like we saw with the datetimes?

@bmtcril not that I can see. The only data type change (aside from the timestamp change) is the video_position type, but that field isn't exposed in any datasets and the only time it's used in a virtual dataset query is after it's cast to an Int32. That cast shouldn't cause any issues, plus I have a change coming to that query anyway so it's a tiny bit of tech debt that'll get taken care of soon.

authors: SoryRawyer bmtcril

repo: openedx/tutor-contrib-aspects


text:
Bug fix in ThreadPool -- holding lock when not needed

ThreadPool::addTask should not keep holding the lock when executing the task with the calling thread. This inadvertently will block any other threads reading or writing exr files concurrently.

I just ran into this also. Would be great if it was merged.

+1 - this severely affects read performance when multiple threads are reading files simultaneously in a paging scenario (an image cache). So much so that using TIFF format (with all the stat() overhead of changing mipmap levels over NFS that it has and therefore usually makes it much slower than OpenEXR) is actually faster than OpenEXR ZIP in highly-threaded scenarios when worker threads are doing the reading.

@ppearson Are you quite sure it's because of this bug? I recently uncovered some big performance differences between TIFF and OpenEXR tiled read timings (TIFF winning handily, to my surprise, as detailed here: http://lists.openimageio.org/pipermail/oiio-dev-openimageio.org/2015-December/013666.html), but I tried with several thread scenarios and the difference was not especially dependent on number of threads (including doing my benchmarks single-threaded). So while this thread problem certainly can't be helping, I suspect that it's not the whole story. I could be wrong -- and would like to be wrong, but so far the evidence is that it's not specifically a threading issue.

Addressed by #280

authors: lgritz mbechard meshula ppearson

repo: openexr/openexr


text:
Updating HorizontalPodAutoscalar

In support of correcting issue #65 I've updated the HPA API version and corrected the spec structure.
Description
Updated the apiVersion to autoscalingv2
Updated .spec.metrics.type[*].resource to use .target structure
References
Pull is based on correcting issue #65
The reference for the API version being deprecated can be found at https://kubernetes.io/docs/reference/using-api/deprecation-guide/#horizontalpodautoscaler-v125
The reference for the spec change can be found at https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-resource-metrics
Review Checklist

[x] I have clicked on "allow edits by maintainers".
[x] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[x] I have added tests to validate that the change in functionality is working as expected

I bumped the chart and app version to play nice with your pull request.

@jliedy mind rebasing on main? We just merged some changes.

One sec

One sec

authors: jliedy jon-whit

repo: openfga/helm-charts


text:
Add more textfield tests

Redo of additional TextField tests. These haven't been tested in the NPM environment or anything, so I'm leaving it as a draft PR for now. I tested the logic on Neko and Wincpp and compared with Flash.

https://gist.github.com/MSGhero/848dabee2b1f210abfb252857e7fcc2a

repo: openfl/openfl

license: mit

license_source: bigquery


text:
Add an in-app changelog

Add an in-app changelog that's triggered when opening the app after an upgrade (or series of upgrades) to let the user know what's new from the last time he/she used the app
Proposed library to use: https://github.com/TonnyL/WhatsNew
We can either hardcode it, or we can have a JSON file on the server, or somewhere in the code like @VaiTon suggested

Hey, I'm interested to work on this. Can I get some details on it?

@hmuhammadazeem we could create a file CHANGELOG.md and then display it after every update in-app or maybe fetch the details from github.

Oh my bad, the file CHANGELOG already exists. The second part of my sentence is still valid though.

Hello. I am new to open source and wanted to start my first project. Do you guys think I can take a crack at this

@rprager18 yes you are very welcome to do so!
@teolemon recommends this library (https://github.com/TonnyL/WhatsNew). Take a look!

@teolemon @VaiTon Hi!
Is it still TBD? Can I take it?

We can do something special with the format you'd like @naivekook

@teolemon @VaiTon Hi!

Hey hi @naivekook and welcome!

Is it still TBD? Can I take it?

Sure you can!

also do we have another source of changelog?
In current case we need to parse CHANGELOG.md via gradle task on each build to get the new changes and store them in application and it quite tricky because this file doesn't have stable formatting.

We could use the file used by the playstore maybe, I really do not know.

authors: VaiTon hmuhammadazeem naivekook rprager18 teolemon

repo: openfoodfacts/openfoodfacts-androidapp


text:
Landscape enabled

Description
#186 Landscape screen orientation enabled in tab
Related issues and discussion
#186
Screen-shots, if any

Checklist
Make sure you've done all the following (You can delete the checklist before submitting)

[x] Apply the AndroidStyle.xml style template to your code in Android Studio.
[x] Code is well documented
[x] Include unit tests for new functionality
[x] All user-visible strings are made translatable
[x] Code passes Travis builds in your branch
[x] If you have multiple commits please combine them into one commit by squashing them.
[x] Read and understood the contribution guidelines .

@teolemon Please review this PR . I have tested this on  TAB Android 8.0.0  Nexus 9 API 26 working well .

I see no issues with the code. Might be best to go the full way and allow for users to use landscape on their phones if they want to. How does a product view look with this?

@teolemon @Karljoones  This is not the way to enable the app for use in landscape mode .
For landscape mode we need to create separate layouts . For designing for tablets we need to implement something called "Master Detail Flow" .
Let the task of enabling the app for tablets be kept for later as there is a lot of work involved .

@Karljoones This is how product view looks

Merged, thanks @iml-v

authors: Karljoones PrajwalM2212 iml-v teolemon


text:
CocoaPods could not find compatible versions for pod "Sentry"

What

[ ] Episode 10 of "CocoaPods vs Sentry"

  CDN: trunk Relative path: Specs/3/7/4/TOCropViewController/2.6.1/TOCropViewController.podspec.json modified during this run! Returning local

[!] CocoaPods could not find compatible versions for pod "Sentry":
In snapshot (Podfile.lock):
Sentry (= 7.18.0, ~> 7.18.0)
In Podfile:
sentry_flutter (from .symlinks/plugins/sentry_flutter/ios) was resolved to 0.0.1, which depends on
Sentry (~> 7.19.0)
https://github.com/openfoodfacts/smooth-app/runs/7200237594?check_suite_focus=true
https://github.com/openfoodfacts/smooth-app/issues?q=is%3Aissue+cocoapods+is%3Aclosed

Also, this build is cursed 😈

cf. The Number of the Beef by Iron Maiden in Spinal Tap mode ;)
Hey I've got good news, it's never going to happen again. Until version 6.6.6.

Fix: cf. https://github.com/openfoodfacts/smooth-app/issues/1300#issuecomment-1075487899
I don't know how we can imagine Sentry version 7.18.0 from a line like this in pubspec.yaml:
  sentry_flutter: ^6.6.0 # careful with upgrading cf: https://github.com/openfoodfacts/smooth-app/issues/1300

I guess or rather hope running smoothie on a Mac and commit your so called "wtf" file changes could fix the issue.
But that's not a long term solution, we should find a way to make this secure.
Unfortunately I have no experience with cocoapods so nearly all of my knowledge comes from reading your comments.
I just checked and dependabot doesn't support cocoapods at the time being.
Is it enough to run the app once a day automatically and PR any changes to the Podfile and Podfile.lock, I don't know.
Another interesting comment from the before linked issue:

The source code from the dependencies is often checked in to the repo as well, so you're right there is a lot of vendoring. In some cases developers choose to not check in the Pods/ directory, in which case simply updating the Podfile and Podfile.lock would be enough. But it wouldn't cover the case where the Pods/ are checked in.

(See: https://guides.cocoapods.org/using/using-cocoapods#should-i-check-the-pods-directory-into-source-control)

Could it be enough to just commit the Pods dir, then we wouldn't have a problem with deleted versions as we have a local copy right? I don't know either but that would save us a Mac VM running on schedule. It's free but looking at the world we don't need to waste any energy.

It's free but looking at the world we don't need to waste any energy.

There could be tons to write about that, including the interest of some attached videos or large screenshots that will stay forever. Or of Codecov mails I still haven't found what they were all about.
I have no experience with cocoapods, dependabot or Podfile and I don't even know what they're here for. I code in OOP and SQL, if possible the rest should be a black box to me - I have limited bandwidth in my brain and limited time.
So, let's be engineers: if we find a solution that works, we use it. When it becomes a priority to find another solution, then we'll think about it.
I've just PR'ed my Podfile.lock. Don't know what could change. Just noticed that the latest change was 2 days ago by @g123k, and that's exactly were my Podfile.lock is different. Not blaming, I don't even know how that file can change.

@teolemon Are we done now, after my suggestions in https://github.com/openfoodfacts/smooth-app/issues/1300#issuecomment-1075487899?

authors: M123-dev monsieurtanuki teolemon

repo: openfoodfacts/smooth-app


text:
Amber non-bonded parity

Description
This PR aims to get non-bonded energies via the Amber energy driver to match the GROMACS and OpenMM energies. This can be thought of as a follow-on to #158.
Checklist

[ ] Add tests
[ ] Lint
[ ] Update docstrings

Initial results are not great:

A separate issue that's cropped up is that angle energies are mangled. I've tried to strip down a MWE:
In:
import numpy as np
from openff.toolkit.topology import Molecule
from openff.toolkit.typing.engines.smirnoff import ForceField
from openff.units import unit

from openff.interchange.components.interchange import Interchange
from openff.interchange.drivers import get_amber_energies, get_openmm_energies

mol = Molecule.from_smiles("ClC#CCl")
mol.name = "HPER"
mol.generate_conformers(n_conformers=1)

parsley = ForceField("openff_unconstrained-1.0.0.offxml")

out = Interchange.from_smirnoff(force_field=parsley, topology=mol.to_topology())
out.box = [4, 4, 4]
out.positions = mol.conformers[0]
out.positions = unit.nanometer * np.round(out.positions.m_as(unit.nanometer), 5)

out["Electrostatics"].method = "pme"

out.to_top("internal.top")
out._to_parmed().save("parmed.top")
out._to_parmed().save("parmed.prmtop")

out.to_gro("internal.gro")
out._to_parmed().save("parmed.gro", precision=8)
out._to_parmed().save("parmed.rst7")

omm_energies = get_openmm_energies(out, combine_nonbonded_forces=True)

omm_energies.compare(
    get_amber_energies(out),
)

Out:
/Users/mwt/miniconda3/envs/openff-system/lib/python3.8/site-packages/pandas/core/dtypes/cast.py:1981: UnitStrippedWarning: The unit of the quantity is stripped when downcasting to ndarray.
  result[:] = values
Traceback (most recent call last):
  File "debug_angle.py", line 32, in <module>
    omm_energies.compare(
  File "/Users/mwt/software/openff-system/openff/interchange/drivers/report.py", line 149, in compare
    raise EnergyError(
openff.interchange.drivers.report.EnergyError:
Some energy difference(s) exceed tolerances!
All values are reported in kJ/mol:
      key      diff   tol    ener1    ener2
    Angle -1.180584 0.001 0.000141 1.180725
Nonbonded -0.004176 0.002 1.769421 1.773598

The two .gro files, and the [ angles ] section of the .top files match; this indicates that the data relevant to angles matches the internal and ParmEd representations, at least expressed in GROMACS files. I manually looked through the two Amber files and everything looks the same to rounding precision, accounting for unit conversions.

This seems to be both a clear improvement but also the tip of the iceberg. No doubt we'll need to return to this at some point in the future.

repo: openforcefield/openff-interchange

license: MIT


text:
fix: closes #938

os error

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 75.00000% with 2 lines in your changes missing coverage. Please review.

Project coverage is 96.19%. Comparing base (9163dbb) to head (95ea458).

Files with missing lines
Patch %
Lines

sepal_ui/sepalwidgets/inputs.py
75.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #947      +/-   ##
==========================================
- Coverage   96.47%   96.19%   -0.28%
==========================================
  Files          39       39
  Lines        4002     3814     -188
==========================================
- Hits         3861     3669     -192
- Misses        141      145       +4

Flag
Coverage Δ

?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter dfguerrerom


text:
Debugger start results in Error 74

Hello,
I created a fresh project and a fresh GOOP4 class. I added persitent and debug info after creating the class.
When I try to start the Debugger from context menu I get Error 74:

Hmm it works for me.
Do you have have "Enable automatic error handling" ON?
Also can you check that this Data type isn't changed?

Version 1.3.9[161] I can still reproduce this when I disable automatic error handling in the calling vi.
The 'Debugger out' cluster looks the same here.
Steps to reproduce:

empty project->save
new goop class (goop4)
create write accesor
right click on class->add design pattern(persistent)
right click on class->add design pattern(debug)
create caller vi -> Run caller.vi
right click menu-> Debug class... -> Error

Can you please update to the latest version on VIPM to check if this is still happening?

Oh sorry, I took the Tools->GOOP->Product Information for granted, which is wrong. I am on latest vipm version, which is 2.1.0.7 for utils

BTW do you know that you can probe your GOOP data with a normal probe as well.
Maybe that is good enough instead of adding the extra design patterns.

authors: Bas-vE MikaelHolmstrom pettaa123

repo: opengds/OpenGDS


text:
fix typo on geoparquet.md

I was reading the spec and found a small typo, shall I just fix it through a PR ? Feel free to let me know if that helps!

Thanks!

repo: opengeospatial/geoparquet


text:
rename signalo_de_CH.qm to signalo_de.qm for future releases

The translation file is not recognized by QGIS when it's called signalo_de_CH.qm. It should be named signalo_de.qm.

fix in RC5

repo: opengisch/signalo


text:
Adding translateable site_description

Thanks a lot Adrien!


text:
Menu of links to other pages

Much like existing site's menu button, leading to a variety of other pages.
Perhaps this should be easy to customize without having to rebuild.

@AurelWu  Perhaps the map could be published as a React component so that the indoorCo2map site can provide its own separate navigation bar above the map component?

yep totally makes sense to have that separate. sorry for the late reply.

authors: AurelWu pwellner

repo: openiaq/map-website


text:
fix: build error

#724

是不是你的 Flutter 版本不是  2.2.x?

或许我们可以把对 flutter 2.5 支持的分支创建出来，把这个 PR 合并进去。

看起来这个方式更好一些, 我们需要把这些分支创建出来, 再把这个 PR 的 target 改成对应分支

repo: openkraken/kraken


text:
Whether serviceQuality can provide customized restart policies, such as Always, Onfailure, Never, to solve the problem of data inconsistency caused by some program crashes;

Whether serviceQualities can provide customized restart policies, such as Always, Onfailure, Never. You can choose to restart the whole pod when some programs crash to solve the problem of data inconsistency caused by some program crashes;
serviceQualities 是否可以提供自定义restartpolicry，如Always、Onfailure、Never，可以选择部分程序崩溃整个pod进行重启，解决部分程序崩溃造成数据不一致的问题；

Whether serviceQualities can provide customized restart policies, such as Always, Onfailure, Never. You can choose to restart the whole pod when some programs crash to solve the problem of data inconsistency caused by some program crashes;
serviceQualities 是否可以提供自定义restartpolicry，如Always、Onfailure、Never，可以选择部分程序崩溃整个pod进行重启，解决部分程序崩溃造成数据不一致的问题；

我理解您希望通过服务质量解决的问题是故障场景下的自动化运维策略，是否是这种的场景。

authors: anhaogege ringtail

repo: openkruise/kruise-game


text:
Export class GeolocationError

The class GeolocationError should be exported, so that the "code"-property be accessible in Typescript.
The issue has already been discussed here: #10905

Great, thank you.

repo: openlayers/openlayers


text:
Pybitcoin

@muneeb-ali can you check to see if this works for you? Hopefully I didn't break anything.

All looks good. Go ahead with the merge.

woohoo! :p

repo: openname/pybitcoin


text:
Renamings

We should start cleaning up some of the names.
Approach I recommend for discussion: top post contains consensus. Below we can add discussion for suggestions. Once we have consensus on new name, we add the change to the top post. Once the rename is complete (in a PR), we check it off the list.
Please add more suggestions for things to rename. Let’s just keep this issue going until we finish 1.0.

[ ]  LiveVisualization
[ ]  SingleTrajectoryAnalysis
[ ]  PathMoveChange
[ ]  spatial and atoms (in features)
[ ] nsteps_per_frame (in engine options)
[ ] CVRangeVolume, CVRangeVolumePeriodic
[ ] all CVs from CV_Name to NameCV to be consistant with other OPS objects naming
[ ] allow_partial (in storage)

My first suggestions for fixes (don't have suggestions for everything yet):

spatial and atoms => n_spatial, n_atoms
nsteps_per_frame => n_steps_per_frame

LiveVisualization presumably only applies to 2D projections, right? Perhaps the new name should indicate that?

LiveVisualization presumably only applies to 2D projections, right? Perhaps the new name should indicate that?

I agree. Maybe MCStep2DVisualizer? The point is that it takes an MC step, and plots the move done in that step. The visualization changes depending on whether the move was accepted or not.
(OTOH, I think that PathSampling.live_visualization should keep the same name. The point is that the LiveVisualization object isn't only for use in the live_visualization variable!)

Also, added a new one above: CVRangeVolume. The problem is that this is too close to our naming convention for CV_Function, etc. To us it is obvious, since they're in different files. But to a user, they're both in the openpathsampling namespace, and share a prefix (the difference of the underscore is pretty subtle). We should either change the CVs to end with CV, or (my preference), change the CVRangeVolume to something that doesn't either begin or end with CV. RangeCVVolume isn't pretty, but would avoid the problem. Better ideas would be very welcome. (PhaseSpaceCVVolume? even just PhaseSpaceVolume? but neither of those are exactly accurate)

Maybe allow_partial => allow_incomplete? It seems to me like partial here is the opposite of complete, is that correct?
My concern is that allow_partial isn't so obviously connected to what is "partial" about it. If a user made a complicated CV (e.g., one that returned an array -- possible now, right?), then allow_partial could be misunderstood as "part of the array."

all CVs from CV_Name to NameCV to be consistant with other OPS objects naming

Agreed. @jhprinz : do you want to make a PR for this one?

Sure. If you want to do it now. Please do so.

I can do the change for numbers_of to n_... in a quick PR. I would prefer to leave dimension names as atoms, spatial because netcdf+ uses _ to separate object and attribute. Also, a dimension is always a number and this is kind of weird.

I would prefer to leave dimension names as atoms, spatial because netcdf+ uses _ to separate object and attribute. Also, a dimension is always a number and this is kind of weird.

But the point is that it isn't always totally obvious that these are dimensions (unless argument names are given explicitly). In particular, atoms can just as easily apply to a list of specific atom objects (and often does in, e.g., MDTraj!) It's also strange that we have a single inconsistency in nomenclature when dealing with internal storage aspects of netcdf+. Everywhere else we use n_; except this one place.
Is it possible to have the user-facing labels have the n prefix, and strip that internally in netcdf+?

Is it possible to have the user-facing labels have the n prefix, and strip that internally in netcdf+?

I think so. Currently this is handles by the engine. It is resposible to provide properties to get the dimensions.
Actually. Now that I think of it, we can use dimension names including n_... that should not be a problem. It is kind of redundant to have netcdf_file.dimensions = ['n_atoms', 'n_spatial', ...] but who cares...

Also, added a new one above: CVRangeVolume.

Would renaming the CVs to ...CV fix this? Or is this still confusing. If we strictly have the type at the end that might be okay.

allow_incomplete

I like that that will make a PR

Would renaming the CVs to ...CV fix this?

Sort of. It definitely resolves the confusion I was most concerned about. But I still think the name is a bit unclear. What about CVBasedVolume or CVDefinedVolume or SingleCVVolume?

global_state
Agree that this should change. I think I like sampleset most of the options. Key point to remember: even though this always represents the current state of the system, the user mainly sees it when setting initial conditions. So I think sampleset=initial_conditions reads best of the suggestions.

Skype with @jhprinz : SingleTrajectoryAnalysis => TrajectoryTransitionAnalysis (and I'll do the PR to change that)

visualize_frequency
This actually controls both the PathSampling.live_visualization and the step-by-step output of step number, which @jhprinz recently extended to add an estimated time remaining.
In an ipynb, it's great at every step. But in the output from a pure-Python run, you'll want less frequent updates. And since it isn't just for the visualization, let's give it a better name.
Maybe status_update_frequency or just status_frequency?

I just looked at this again. Maybe we should try not to make the visualization explicitly a part of the PathSampling, but rather an optional component that has access to the current status. Like adding a logger. We could provide several events and you can add an eventlistener that is called when something is happening.
This would mean that the frequency would be part of the LiveVisualization object and not the PathSampling.
lv = LiveVisualization
Pathsampling.add_event_listener('update', lv)

That makes it very flexible to add more output for all sorts of purposes. Can be past 1.0.

Maybe we should try not to make the visualization explicitly a part of the PathSampling, but rather an optional component that has access to the current status.

I like this idea; I think it should wait for after 1.0. I agree that this is a better and more flexible approach. But not worth cleaning up on a short timeframe.

With #596 merged, all the tasks in this issue are completed. Closing it; we can always do another round of renaming later!
(Also, I really like the way this renaming issue went: the top post is a great record of what changes were made, and in what PR they occurred. Really useful when trying to fix work from other projects.)

authors: dwhswenson jchodera jhprinz

repo: openpathsampling/openpathsampling


text:
Revoir la gestion des types de périmètres dans le formulaire

Actuellement, les fonctions getPerimetersByName et getPerimetersByCode utilisent une URL qui intègre un "S" en dur, ce qui est une mauvaise pratique.
La correction de problème en entraine beaucoup d’autres.
Dans components/suivi-form/perimetres/index.js , on reçoit une liste de périmètres sous la forme type:code dans lequel le type n’a pas de "s".
Le type est ensuite utilisé ici pour récupérer le nom du périmètre.
Or, l'appel échoue car il attend une valeur type:code où le type comporte un "s".
Il faudrait revoir le fonctionnement du formulaire plus en profondeur afin de pouvoir le modifier sans créer des bugs.

@GllmR est-ce que la PR sur la calculette a complètement résolu ce point ou il reste des choses à faire ?

@GllmR est-ce que la PR sur la calculette a complètement résolu ce point ou il reste des choses à faire ?

Il n’y a plus de problème visible, cette PR concerne un problème dans le code qui n’impacte pas le site directement.

authors: GllmR flacombe


text:
Update PHOENIX data to use API instead of CSV file

The API appears to be called CKAN. CKAN data loader needs to be added.
Example: https://phoenixopendata.com/dataset/ois/resource/24fe89fb-9d4f-4fba-8b40-9330a5f7d9e7
Click Data API button.

Boston uses this too: https://data.boston.gov/

San Jose also uses CKAN: https://data.sanjoseca.gov/dataset?q=police

Milwaukee: https://data.milwaukee.gov/dataset/fpc-citizen-complaints

Santa Monica: https://data.santamonica.gov/dataset/police-incidents/resource/ff0f4877-3731-4476-b2ca-065f5819bf12

repo: openpolicedata/openpolicedata


text:
don't show authored papers in the Paper status tab

This is already in the live site.

Can you merge this please?

repo: openreview/openreview-py


text:
Add GCP adapter for S3 compatible interfaces and added data mover interfaces for GCP backend

New updated PR, this PR adds GCP adapter for S3 compatible interfaces and migration scenario from GCP to AWS also tested.

Hi, two suggestions:

Migration from other cloud  to GCP also need to be tested.
Remove duplicated import record, for example, the following two records are duplicate:
"github.com/webrtcn/s3client"
. "github.com/webrtcn/s3client"

Hi,

Migration from other cloud to GCP is done.

"github.com/webrtcn/s3client"
. "github.com/webrtcn/s3client" both import have different significant so it generate errors if removed.
(.) import let  the package's exported identifiers  declared in the current file's file block and can be accessed without a qualifier.so some places it is utilising reference.

Well, for the second one, maybe you can try to reference each identifier exported from the package in the same way, say, with the prefix of (s3client.)
But that is not necessary, just a suggestion.

@sfzeng it is increasing complexity so if current way is accepted please let us know.

OK, go ahead please.

@sfzeng thanks. we are waiting for your final review and merge update.

@Click2Cloud-Gamma It's OK, need @xing-yang to merge.

LGTM~

authors: Click2Cloud-Gamma sfzeng wisererik

repo: opensds/multi-cloud


text:
Scheduler echancement

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Solve Issue #290
Special notes for your reviewer:
Release note:

Coverage increased (+0.6%) to 60.521% when pulling d7ddcf652cad591c9db332b7d2f8e6f3930f0d8a on PengYiOfOpenSDS:scheduler_echancement into 94acb4ed7cfc037a80b12e3bb12685c54c138d3a on opensds:development.

Coverage increased (+0.6%) to 60.521% when pulling d7ddcf652cad591c9db332b7d2f8e6f3930f0d8a on PengYiOfOpenSDS:scheduler_echancement into 94acb4ed7cfc037a80b12e3bb12685c54c138d3a on opensds:development.

Coverage increased (+0.6%) to 60.521% when pulling d7ddcf652cad591c9db332b7d2f8e6f3930f0d8a on PengYiOfOpenSDS:scheduler_echancement into 94acb4ed7cfc037a80b12e3bb12685c54c138d3a on opensds:development.

Coverage increased (+0.6%) to 60.521% when pulling d7ddcf652cad591c9db332b7d2f8e6f3930f0d8a on PengYiOfOpenSDS:scheduler_echancement into 94acb4ed7cfc037a80b12e3bb12685c54c138d3a on opensds:development.

Coverage increased (+0.6%) to 60.521% when pulling d7ddcf652cad591c9db332b7d2f8e6f3930f0d8a on PengYiOfOpenSDS:scheduler_echancement into 94acb4ed7cfc037a80b12e3bb12685c54c138d3a on opensds:development.

Why is this closed?

authors: PengYiOfOpenSDS coveralls xing-yang

repo: opensds/opensds


text:
Test failure on Chromium Linux

Interesting that it's so close. Maybe we're running into some anti-aliasing? Should we sample from a different location?

authors: avandecreme iangilman

repo: openseadragon/openseadragon


text:
canvas-key did not work

viewer.addHandler('canvas-key', ()=>{
console.log(1)
})
it did not work

thanks


text:
Annotation get shifted by 5px when rendered back using fabric

we are using open sea dragon with fabric overlay, where i draw annotations and get back contour from the backend. But this contour gets shifted by 3-5px when it is rendered back on the image. Is there any optimal solution for this kind of issue ?

Is it 3 - 5px at every zoom level, or does the gap change as you zoom in? If it's the former, I wonder if there is some CSS that's bumping the overlay a little.
Have you filed this issue on the fabric overlay project page?
Anyway, might be good to be able to see a link to a repro. I'm not sure what the cause is off the top of my head.

I was thinking possibly some CSS as well...

authors: iangilman msalsbery techiepop


text:
Wrong positioning in add overlay

Hi I'm trying to work with openseadragon, everything is working but the position on the overaly is incorrect even when the viewport position is correct, I Try it hardcoding 0.5,0.5 and it doesn't go to the middle.
async getData() {
        const artworkId = this.props.match.params.artworkId;

        let API = `https://backend.itinerariosonline.museobilbao.com/artworks/${artworkId}/`;

        await axios.get(API)
        .then(response => {this.setState({ artwork: response.data, isLoading: false })})
        .then(() => {
            this.viewer = OpenSeaDragon({
                id: "museo-detail",
                prefixUrl: "/openseadragon/",
                navImages: {
                    zoomIn: {
                        REST:   'zoomin_grouphover.png',
                        GROUP:  'zoomin_grouphover.png',
                        HOVER:  'zoomin_hover.png',
                        DOWN:   'zoomin_pressed.png'
                    },
                    zoomOut: {
                        REST:   'zoomout_grouphover.png',
                        GROUP:  'zoomout_grouphover.png',
                        HOVER:  'zoomout_hover.png',
                        DOWN:   'zoomout_pressed.png'
                    },
                    home: {
                        REST:   'home_grouphover.png',
                        GROUP:  'home_grouphover.png',
                        HOVER:  'home_hover.png',
                        DOWN:   'home_pressed.png'
                    },
                    fullpage: {
                        REST:   'fullpage_grouphover.png',
                        GROUP:  'fullpage_grouphover.png',
                        HOVER:  'fullpage_hover.png',
                        DOWN:   'fullpage_pressed.png'
                    }
                },
                zoomInButton: "zoom-in",
                zoomOutButton: "zoom-out",
                fullPageButton: "full-page",
                homeButton: "home",
                visibilityRatio: 1.0,
                animationTime: 0.5,
                blendTime: 0.1,
                constrainDuringPan: true,
                defaultZoomLevel: 1,
                minZoomLevel: 0,
                maxZoomLevel: 10,
				degrees: 0,
                showNavigator: false,
                autoHideControls: false,
                showFullPageControl: true,
				supportsCanvas: true,
                tileSources: {
                    Image: {
                        xmlns:    "http://schemas.microsoft.com/deepzoom/2008",
                        Url:      `url`,
                        Format:   "png",
                        Overlap:  "1",
                        TileSize: "254",
                        Size: {
                            Height: this.state.artwork.height,
                            Width:  this.state.artwork.width
                        }
                    },
                },
                debugMode: true,
            })
            this.createOverlays();

        })
        .catch(error => this.setState({ error, isLoading: false }));
    };

	createOverlays () {
		var i;
            for (i = 0; i < this.state.artwork.pois.length; i++){
                var overlayid = `example-overlay${this.state.artwork.pois[i].id}`;
              	var overlayx = (this.state.artwork.pois[i].x/this.state.artwork.width);
                var overlayy = (this.state.artwork.pois[i].y/this.state.artwork.height);
                var overlaywidth = this.state.artwork.pois[i].width/1000;
                var overlayheight = this.state.artwork.pois[i].height/1000;
				var textPoint = new OpenSeaDragon.Point(overlayx,overlayy);
				var coordinates = this.viewer.viewport.imageToViewportCoordinates(textPoint);
				var rect = new OpenSeaDragon.Rect(coordinates.x, coordinates.y,overlaywidth,overlayheight);
				var elt = document.createElement("div");
				elt.id = `div${i}`;
				elt.className = "highlight";

                var overlay = this.viewer.addOverlay({
					element: elt,
                    id: overlayid,
					location: rect,
					placement: OpenSeaDragon.Placement.CENTER,
					checkResize: false
                })

				elt.addEventListener("click", this.showModalPoint.bind(null,this.state.artwork.pois[i]));
            }
	}

I don't know if I'm committing a mistake, I tried a lot of things but the positioning is not working properly.
Best regards

Thanks, so in the x and y I have the exact pixels on X and Y, with the point and imagetoViewportCoordinates it gives me the exact viewport coordinates no?
Thanks a lot, like you said it worked perfect with square images but the problem appeared with other type of images.
Thanks a lot


text:
Add positive_score_impact support for rank_features

Is your feature request related to a problem? Please describe.
No support for positive_score_impact parameter for rank_features
Describe the solution you'd like
Add support

Partially relates to https://github.com/opensearch-project/OpenSearch/issues/977

Closing since #2725 has been merged

authors: Hronom kartg

repo: opensearch-project/OpenSearch


text:
[Backport 2.x] Allow customization of netty channel handles before and during decompression (#10261)

Description
Backport of #10261 from dad525a
Related Issues

Related https://github.com/opensearch-project/OpenSearch/issues/10260

Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff
[X] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[ ] ~Public documentation issue/PR created~

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Closing in favor of https://github.com/opensearch-project/OpenSearch/pull/10443


text:
Upgrading gson to 2.8.9

Signed-off-by: Vacha vachshah@amazon.com
Description
Upgrading gson to latest 2.8.9 in direct dependency and via hadoop-common.
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[X] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

❌   Gradle Check failure d7b78ba Log 1066
Reports 1066

Tests with failures:
 - org.opensearch.discovery.StableMasterDisruptionIT.testStaleMasterNotHijackingMajority

2632 tests completed, 1 failed, 4 skipped

1> [2021-11-12T16:43:27,115][WARN ][o.o.c.NodeConnectionsService] [node_t2] failed to connect to {node_t1}{sPuJWTDSQC-Dglo7tjZfog}{6VrTsrXIRcaOHwn8m9dFdw}{127.0.0.1}{127.0.0.1:43109}{dimr}{shard_indexing_pressure_enabled=true} (tried [1] times)
  1> org.opensearch.transport.ConnectTransportException: [node_t1][127.0.0.1:43109] connect_exception
  1> 	at org.opensearch.transport.TcpTransport$ChannelsConnectedListener.onFailure(TcpTransport.java:1064) ~[main/:?]
  1> 	at org.opensearch.action.ActionListener.lambda$toBiConsumer$2(ActionListener.java:213) ~[main/:?]
  1> 	at org.opensearch.common.concurrent.CompletableContext.lambda$addListener$0(CompletableContext.java:55) ~[opensearch-core-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863) ~[?:?]
  1> 	at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841) ~[?:?]
  1> 	at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510) ~[?:?]
  1> 	at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162) ~[?:?]
  1> 	at org.opensearch.common.concurrent.CompletableContext.completeExceptionally(CompletableContext.java:70) ~[opensearch-core-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at org.opensearch.nio.SocketChannelContext.connect(SocketChannelContext.java:160) ~[opensearch-nio-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at org.opensearch.nio.EventHandler.handleConnect(EventHandler.java:130) ~[opensearch-nio-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at org.opensearch.transport.nio.TestEventHandler.handleConnect(TestEventHandler.java:139) ~[framework-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at org.opensearch.nio.NioSelector.attemptConnect(NioSelector.java:446) ~[opensearch-nio-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at org.opensearch.nio.NioSelector.registerChannel(NioSelector.java:469) ~[opensearch-nio-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at org.opensearch.nio.NioSelector.setUpNewChannels(NioSelector.java:458) ~[opensearch-nio-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at org.opensearch.nio.NioSelector.preSelect(NioSelector.java:279) ~[opensearch-nio-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at org.opensearch.nio.NioSelector.singleLoop(NioSelector.java:172) ~[opensearch-nio-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at org.opensearch.nio.NioSelector.runLoop(NioSelector.java:148) ~[opensearch-nio-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	at java.lang.Thread.run(Thread.java:833) [?:?]
  1> Caused by: java.net.ConnectException: Connection refused
  1> 	at sun.nio.ch.Net.pollConnect(Native Method) ~[?:?]
  1> 	at sun.nio.ch.Net.pollConnectNow(Net.java:672) ~[?:?]
  1> 	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946) ~[?:?]
  1> 	at org.opensearch.nio.SocketChannelContext.connect(SocketChannelContext.java:157) ~[opensearch-nio-2.0.0-SNAPSHOT.jar:2.0.0-SNAPSHOT]
  1> 	... 9 more

start gradle check

❌   Gradle Check failure d7b78ba Log 1067
Reports 1067

> Task :test:fixtures:s3-fixture:composeUp

ERROR: for 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture-with-ec2_1  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
Creating 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture-repositories-metering_1 ... done
Creating 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture-with-ecs_1              ... done
Creating 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture-with-session-token_1    ... done
Creating 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture-other_1                 ... done
Creating 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture_1                       ... done

ERROR: for s3-fixture-with-ec2  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
Stopping 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture-repositories-metering_1 ...
Stopping 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture-with-ecs_1              ...
Stopping 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture_1                       ...
Stopping 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture-other_1                 ...
Stopping 56aa93ed60e3e11b06e2067e06b0dd8c_s3-fixture__s3-fixture-with-session-token_1    ...

start gradle check

❌   Gradle Check failure d7b78ba Log 1068
Reports 1068

REPRODUCE WITH: ./gradlew ':server:test' --tests "org.opensearch.monitor.fs.FsHealthServiceTests.testFailsHealthOnHungIOBeyondHealthyTimeout" -Dtests.seed=20C97377870AC21B -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=nb -Dtests.timezone=Australia/Sydney -Druntime.java=17

org.opensearch.monitor.fs.FsHealthServiceTests > testFailsHealthOnHungIOBeyondHealthyTimeout FAILED
    java.lang.AssertionError
        at __randomizedtesting.SeedInfo.seed([20C97377870AC21B:A2BD2D7EF3F6B453]:0)
        at org.junit.Assert.fail(Assert.java:86)
        at org.junit.Assert.assertTrue(Assert.java:41)
        at org.junit.Assert.assertTrue(Assert.java:52)
        at org.opensearch.monitor.fs.FsHealthServiceTests.testFailsHealthOnHungIOBeyondHealthyTimeout(FsHealthServiceTests.java:239)

The test failure from ./gradlew ':server:test' --tests "org.opensearch.monitor.fs.FsHealthServiceTests.testFailsHealthOnHungIOBeyondHealthyTimeout" has been reported before, in issue #1307 and #1450.

start gradle check

authors: VachaShah tlfeng


text:
[Deprecate] Setting explicit version on analysis component

Lucene 9 removes the ability to define an explicit version on an analysis component. In this PR the version parameter for an analysis component is deprecated at parse time and a warning issued to the user through the deprecation logger. A separate PR will completely remove the parameter in 2.0.0

Another #1957 failure unrelated to this PR. Adding to #1715
  2> REPRODUCE WITH: ./gradlew ':server:test' --tests "org.opensearch.cluster.routing.MovePrimaryFirstTests.testClusterGreenAfterPartialRelocation" -Dtests.seed=1A5D9D8511119DE0 -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=hr-HR -Dtests.timezone=Europe/Busingen -Druntime.java=17

  2> java.lang.AssertionError: timed out waiting for green state
        at __randomizedtesting.SeedInfo.seed([1A5D9D8511119DE0:4997F9E03A55E2F4]:0)
        at org.junit.Assert.fail(Assert.java:89)
        at org.opensearch.test.OpenSearchIntegTestCase.ensureColor(OpenSearchIntegTestCase.java:986)
        at org.opensearch.test.OpenSearchIntegTestCase.ensureGreen(OpenSearchIntegTestCase.java:925)
        at org.opensearch.test.OpenSearchIntegTestCase.ensureGreen(OpenSearchIntegTestCase.java:914)
        at org.opensearch.cluster.routing.MovePrimaryFirstTests.testClusterGreenAfterPartialRelocation(MovePrimaryFirstTests.java:67)

start gradle check

LGTM minor question though same as on the other PR #1981 - which release we plan to deprecate this?

1.3. I'll backport to 1.x and open a removal PR to remove in main.