innotecsol

Hi abhilashshetty04, ``` kubectl get crd diskpools.openebs.io -oyaml apiVersion: apiextensions.k8s.io/v1 kind: CustomResourceDefinition metadata: creationTimestamp: "2024-02-27T22:42:06Z" generation: 4 name: diskpools.openebs.io resourceVersion: "188484267" uid: 2abef297-28b5-4533-a6b3-f8354ab63fd8 spec: conversion: strategy: None group: openebs.io names:...

Sorry, there exists a deploy with mayastor prefix ``` kubectl get deploy mayastor-operator-diskpool -n mayastor -oyaml apiVersion: apps/v1 kind: Deployment metadata: annotations: deployment.kubernetes.io/revision: "3" meta.helm.sh/release-name: mayastor meta.helm.sh/release-namespace: mayastor creationTimestamp: "2024-02-27T22:40:26Z"...

Hi, many thanks for following up. I downloaded mayastor kubectl plugin from https://github.com/openebs/mayastor/releases/download/v2.7.0/kubectl-mayastor-x86_64-linux-musl.tar.gz and executed `kubectl mayastor upgrade --skip-single-replica-volume-validation -d` `kubectl mayastor upgrade --skip-single-replica-volume-validation` Initially (2.5.0 version) I came from...

Hi niladrih, here the required output: ``` helm ls -n mayastor NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION mayastor mayastor 3 2024-08-05 04:12:08.24708259 +0000 UTC failed mayastor-2.5.0 2.5.0 ```...

For me it looks like all the components are still on 2.5.0 except etcd, it uses docker.io/bitnami/etcd:3.5.6-debian-11-r10 image - here I am not sure, but the statefulset was definitly changed...

``` kubectl mayastor delete upgrade --force Job mayastor-upgrade-v2-7-0 in namespace mayastor deleted ConfigMap mayastor-upgrade-config-map-v2-7-0 in namespace mayastor deleted ClusterRoleBinding mayastor-upgrade-role-binding-v2-7-0 in namespace mayastor deleted ClusterRole mayastor-upgrade-role-v2-7-0 in namespace mayastor deleted...

It seems the pods were upgraded except for io engine Image: docker.io/openebs/mayastor-metrics-exporter-io-engine:v2.5.0 Image: docker.io/openebs/mayastor-io-engine:v2.5.0 all others run with images of 2.7.0 ``` helm ls -n mayastor NAME NAMESPACE REVISION UPDATED...

Hi, I ve redone the steps above. This time `helm rollback mayastor -n mayastor` resulted in ``` helm ls -n mayastor NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION mayastor...

Hi, I am not sure about your answer. All the volumes are mounted and as displayed in my previous entry ``` kubectl mayastor get volumes ID REPLICAS TARGET-NODE ACCESSIBILITY STATUS...

[mayastor-2024-08-12--18-54-41-UTC-partaa-of-tar.gz](https://github.com/user-attachments/files/16591024/mayastor-2024-08-12--18-54-41-UTC-partaa-of-tar.gz) [mayastor-2024-08-12--18-54-41-UTC-partab-of-tar.gz](https://github.com/user-attachments/files/16591026/mayastor-2024-08-12--18-54-41-UTC-partab-of-tar.gz) [mayastor-2024-08-12--18-54-41-UTC-partac-of-tar.gz](https://github.com/user-attachments/files/16591027/mayastor-2024-08-12--18-54-41-UTC-partac-of-tar.gz) I have uploaded the files. As the tar.gz is too big (48MB) I splitted it - you need to cat mayastor-2024-08-12--18-54-41-UTC-parta* >mayastor-2024-08-12--18-54-41-UTC.tar.gz Thanks