[QUESTION]: Post Upgrade of Dell CSI Operator on Openshift from 1.8 to 1.10, its not working anymore #647

soudamsugit · 2023-02-07T05:38:20Z

How can the Team help you today?

Details: ?

Post Upgrade of Dell CSI Operator on Openshift from 1.8 to 1.10, its not working anymore and below are the errors from the pod logs. Can you please advice on the upgrade path?

There seems to be new configs introduced, and this has broken the operator

W0207 05:26:51.893435 I0207 05:26:51.893502 I0207 05:26:51.893523 I0207 05:26:51.893530 I0207 05:26:51.894296 W0207 05:27:01.894795 W0207 05:27:11.894500 W0207 05:27:21.894595 W0207 05:27:31.894767 W0207 05:27:41.895241 W0207 05:27:51.894623 W0207 05:28:01.894734 W0207 05:28:11.894726 W0207 05:28:21.895019 W0207 05:28:31.894834 W0207 05:28:41.900501 W0207 05:28:51.894738 E0207 05:28:55.581158 F0207 05:28:55.581253 I0207 05:26:52.646149 I0207 05:26:52.647924 W0207 05:27:02.648876 W0207 05:27:12.648497 W0207 05:27:22.648572 W0207 05:27:32.648326 W0207 05:27:42.648893 W0207 05:27:52.648375 W0207 05:28:02.648705 W0207 05:28:12.648568 W0207 05:28:22.648351 W0207 05:28:32.648074 W0207 05:28:42.655753 W0207 05:28:52.659526 E0207 05:28:55.326594 F0207 05:28:55.326693 I0207 05:26:53.281276 I0207 05:26:53.283238 W0207 05:27:03.284144 W0207 05:27:13.283802 W0207 05:27:23.284330 W0207 05:27:33.283431 W0207 05:27:43.284224 W0207 05:27:53.283390 W0207 05:28:03.283487 W0207 05:28:13.283914 W0207 05:28:23.283488 W0207 05:28:33.283333 W0207 05:28:43.290502 W0207 05:28:53.292500 E0207 05:28:55.718412 F0207 05:28:55.718525 I0207 05:26:53.964398 I0207 05:26:53.964434 I0207 05:26:53.967169 W0207 05:27:03.967793 W0207 05:27:13.967656 W0207 05:27:23.967490 W0207 05:27:33.967903 W0207 05:27:43.967257 W0207 05:27:53.968121 W0207 05:28:03.967686 W0207 05:28:13.967682 W0207 05:28:23.967283 W0207 05:28:33.967509 W0207 05:28:43.976492 W0207 05:28:53.967290 E0207 05:28:54.977596 F0207 05:28:54.977683 1 feature_gate.go:237] Setting GA feature gate Topology=true. It will be removed in a future release.
1 feature_gate.go:245] feature gates: &{map[Topology:true]}
1 csi-provisioner.go:150] Version: v3.3.0
1 csi-provisioner.go:173] Building kube configs for running in cluster...
1 connection.go:154] Connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:132] Lost connection to unix:///var/run/csi/csi.sock.
1 connection.go:87] Lost connection to CSI driver, exiting
1 main.go:94] Version: v4.0.0
1 connection.go:154] Connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:132] Lost connection to unix:///var/run/csi/csi.sock.
1 connection.go:87] Lost connection to CSI driver, exiting
1 main.go:104] Version: v6.1.0
1 connection.go:154] Connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:132] Lost connection to unix:///var/run/csi/csi.sock.
1 connection.go:87] Lost connection to CSI driver, exiting
1 main.go:93] Version : v1.6.0
1 feature_gate.go:245] feature gates: &{map[]}
1 connection.go:154] Connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:173] Still connecting to unix:///var/run/csi/csi.sock
1 connection.go:132] Lost connection to unix:///var/run/csi/csi.sock.
1 connection.go:87] Lost connection to CSI driver, exiting

soudamsugit · 2023-02-07T05:52:31Z

Hello Team,

This is a Certified Operator that we are using, can you pls let us know how to reach you over call? This is a blocker for us

rensyct · 2023-02-07T05:59:43Z

@soudamsugit , we work in IST timezone and we can get into a call after half an hour which is 12:00 PM IST. Please let us know if that works for you

soudamsugit · 2023-02-07T06:01:25Z

@rensyct, 12 PM IST will be great. Also, pls let me know if you will be able to join the teams call and I can paste the link

rensyct · 2023-02-07T06:04:02Z

Yes @soudamsugit, we will be able to join the teams call

soudamsugit · 2023-02-07T06:13:42Z

@rensyct https://teams.microsoft.com/l/meetup-join/19%3ameeting_NjM0Y2UxODMtNDg1MC00ZTExLTkyZWEtYzg3Njg3NGNkMjg4%40thread.v2/0?context=%7b%22Tid%22%3a%221f4f7eda-6e51-425e-a0f9-4c2fcef58a52%22%2c%22Oid%22%3a%2263a774a0-2e52-48bd-b0db-edde453cc553%22%7d

soudamsugit · 2023-02-08T00:37:24Z

Hello @rensyct,

Thanks for yourtime yesterday. I had ran this with storage team, the credentails look fine.

Also, I have tested them from inside pod and they seem to work fine

[soudamv@qocpa001l ~/powermax/2.3] $ oc rsh powermax-controller-5ccddb4b7-mn2hf

sh-4.4$ curl -kv -u username:password https://10.204.214.25:8443/univmax/restapi/version

Trying 10.204.214.25...
TCP_NODELAY set
Connected to 10.204.214.25 (10.204.214.25) port 8443 (#0)
ALPN, offering h2
ALPN, offering http/1.1
successfully set certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
TLSv1.3 (OUT), TLS handshake, Client hello (1):
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.2 (IN), TLS handshake, Certificate (11):
TLSv1.2 (IN), TLS handshake, Server key exchange (12):
TLSv1.2 (IN), TLS handshake, Server finished (14):
TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
TLSv1.2 (OUT), TLS handshake, Finished (20):
TLSv1.2 (IN), TLS handshake, Finished (20):
SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
ALPN, server did not agree to a protocol
Server certificate:
subject: C=US; ST=Massachusetts; L=Hopkinton; O=EMC Corporation; OU=Storage Platform Enablers and Applications; CN=VMAX-000497600159
start date: Aug 3 23:42:18 2021 GMT
expire date: Aug 1 23:42:18 2031 GMT
issuer: C=US; ST=Massachusetts; L=Hopkinton; O=EMC Corporation; OU=Storage Platform Enablers and Applications; CN=VMAX-000497600159
SSL certificate verify result: self signed certificate (18), continuing anyway.
Server auth using Basic with user 'username'

GET /univmax/restapi/version HTTP/1.1
Host: 10.204.214.25:8443
Authorization: Basic YXVwb3dlcm1heGRzYTpFdipsdXRpKm4wNDU2Nzg5
User-Agent: curl/7.61.1
Accept: /

< HTTP/1.1 200 OK
< X-Content-Security-Policy: default-src 'self'
< X-XSS-Protection: 1; mode=block
< X-Frame-Options: SAMEORIGIN
< Referrer-Policy: no-referrer-when-downgrade
< Content-Security-Policy: default-src 'self'
< X-WebKit-CSP: default-src 'self'
< RESTAPI-PROCESSING-TIME: 13252
< Date: Wed, 08 Feb 2023 00:35:07 GMT
< Connection: keep-alive
< Strict-Transport-Security: max-age=31536000; includeSubDomains
< X-Content-Type-Options: nosniff
< RESTAPI-ACTIVE-SESSION-COUNT: 1
< Transfer-Encoding: chunked
< Content-Type: application/json
< U4V-SHARDPROXY-TIME: 0
<

Connection #0 to host 10.204.214.25 left intact
{"version":"V9.2.3.15"}sh-4.4$

sh-4.4$
sh-4.4$ curl -kv -u username:password https://10.204.214.25:8443/univmax/restapi/91/system/symmetrix/000497600159

Trying 10.204.214.25...
TCP_NODELAY set
Connected to 10.204.214.25 (10.204.214.25) port 8443 (#0)
ALPN, offering h2
ALPN, offering http/1.1
successfully set certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
TLSv1.3 (OUT), TLS handshake, Client hello (1):
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.2 (IN), TLS handshake, Certificate (11):
TLSv1.2 (IN), TLS handshake, Server key exchange (12):
TLSv1.2 (IN), TLS handshake, Server finished (14):
TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
TLSv1.2 (OUT), TLS handshake, Finished (20):
TLSv1.2 (IN), TLS handshake, Finished (20):
SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
ALPN, server did not agree to a protocol
Server certificate:
subject: C=US; ST=Massachusetts; L=Hopkinton; O=EMC Corporation; OU=Storage Platform Enablers and Applications; CN=VMAX-000497600159
start date: Aug 3 23:42:18 2021 GMT
expire date: Aug 1 23:42:18 2031 GMT
issuer: C=US; ST=Massachusetts; L=Hopkinton; O=EMC Corporation; OU=Storage Platform Enablers and Applications; CN=VMAX-000497600159
SSL certificate verify result: self signed certificate (18), continuing anyway.
Server auth using Basic with user 'username'

GET /univmax/restapi/91/system/symmetrix/000497600159 HTTP/1.1
Host: 10.204.214.25:8443
Authorization: Basic YXVwb3dlcm1heGRzYTpFdipsdXRpKm4wNDU2Nzg5
User-Agent: curl/7.61.1
Accept: /

< HTTP/1.1 200 OK
< X-Content-Security-Policy: default-src 'self'
< X-XSS-Protection: 1; mode=block
< X-Frame-Options: SAMEORIGIN
< Referrer-Policy: no-referrer-when-downgrade
< Content-Security-Policy: default-src 'self'
< X-WebKit-CSP: default-src 'self'
< RESTAPI-PROCESSING-TIME: 32
< Date: Wed, 08 Feb 2023 00:36:19 GMT
< Connection: keep-alive
< Strict-Transport-Security: max-age=31536000; includeSubDomains
< X-Content-Type-Options: nosniff
< RESTAPI-ACTIVE-SESSION-COUNT: 1
< Transfer-Encoding: chunked
< Content-Type: application/json
< U4V-SHARDPROXY-TIME: 0
<
{"symmetrixId":"000497600159","local":true,"display_name":"pmax8k0159_qa004","model":"PowerMax_8000","ucode":"5978.711.711","ucode_date":"08-10-2022","cache_size_mb":3567616,"fe_dir_count":12,"be_dir_count":8,"rdf_dir_count":8,"max_hyper_per_disk":128,"dev_masking_aclx_config":"Mixed","aclx_lun_addr":0,"access_control_config":"Enabled","config_change_state":"Enabled","disk_group_assignment":"In Use","raid_config":"RAID-5 (7+1)","pav_model":"DynamicStandardPAV","pav_alias_limit":255,"sddf_state":"Enabled","switched_rdf_config":"Enabled","concurrent_rdf_config":"Enabled","dynamic_rdf_config":"Enabled","concurrent_dynamic_rdf_config":"Enabled","rdf_data_mobility_config":"Disabled","srdfa_max_throttle":0,"srdfa_cache_usage":75,"num_ava_cache_slot":8558276,"max_sys_slot":6418707,"max_dev_slot":320935,"last_ipl_time":"2021-09-04 01:17:11","last_fast_ipl_time":"2022-10-01 01:01:25","symm_alert":"19/30","hot_swap_policy":"Permanent","fba_geo_emulation":"Native","cache_partition":"Disabled","disk_service_state":"Defer* Connection #0 to host 10.204.214.25 left intact
red","data_encryption":"Enabled","rep_cache_usage":0,"device_count":1539,"disk_count":80,"spare_disk_count":4,"unconfig_disk_count":0,"all_flash":true,"lockInfo":[]}sh-4.4$
sh-4.4$

soudamsugit · 2023-02-08T00:46:26Z

@rensyct, I believe it is something with configs that is missing. Can we please connect at 10 AM IST today?

rensyct · 2023-02-08T04:26:36Z

Hi @soudamsugit, thank you for your response, Since the operator part is working as expected now and the current issue is related to PowerMax, we will need to have the Powermax team on the call. I will reach out to them and let you know the time that works for the PowerMax team

soudamsugit · 2023-02-08T04:32:15Z

Thanks a lot @rensyct. Sorry for chasing, appreciate if you can prioritise this issue

rensyct · 2023-02-08T04:36:41Z

Np @soudamsugit. I can understand. This issue is a priority for us. Will keep you posted on the time when we can connect today

rensyct · 2023-02-08T04:51:18Z

@soudamsugit, team is available at 11:00 AM IST. Does that time work for you?

soudamsugit · 2023-02-08T05:31:18Z

sure, we can have a chat at 11 AM

soudamsugit · 2023-02-08T05:31:46Z

https://teams.microsoft.com/l/meetup-join/19%3ameeting_NjM0Y2UxODMtNDg1MC00ZTExLTkyZWEtYzg3Njg3NGNkMjg4%40thread.v2/0?context=%7b%22Tid%22%3a%221f4f7eda-6e51-425e-a0f9-4c2fcef58a52%22%2c%22Oid%22%3a%2263a774a0-2e52-48bd-b0db-edde453cc553%22%7d

prablr79 · 2023-02-08T06:07:26Z

@rensyct any update on this case ?

soudamsugit · 2023-02-08T07:27:51Z

@rensyct , sorry for bugging. I still see few pods crashloopbacking

[soudamv@qocpa001l ~/powermax/2.3] $ oc get pods
NAME READY STATUS RESTARTS AGE
powermax-controller-b8f87cdb6-jnmv5 5/5 Running 0 21m
powermax-controller-b8f87cdb6-qq5tf 5/5 Running 0 21m
powermax-node-2gc4d 2/2 Running 0 21m
powermax-node-6vn8f 1/2 CrashLoopBackOff 8 (2m7s ago) 21m
powermax-node-97b8j 1/2 CrashLoopBackOff 8 (77s ago) 21m
powermax-node-fldjp 1/2 CrashLoopBackOff 8 (2m31s ago) 21m
powermax-node-g4krm 2/2 Running 0 21m
powermax-node-j9n86 2/2 Running 0 21m
powermax-node-nr6n5 1/2 CrashLoopBackOff 8 (4m9s ago) 21m
powermax-node-nwlzk 2/2 Running 0 21m
powermax-node-qxt4v 1/2 CrashLoopBackOff 8 (71s ago) 21m
powermax-node-r6rl7 1/2 CrashLoopBackOff 8 (95s ago) 21m
powermax-node-x9h8l 2/2 Running 0 21m
powermax-node-xjsw5 2/2 Running 0 21m
powermax-node-zblfk 1/2 CrashLoopBackOff 8 (2m42s ago) 21m
powermax-node-zhcjb 1/2 CrashLoopBackOff 8 (3m32s ago) 21m

error:

{"level":"error","msg":"No topology keys could be generated","time":"2023-02-08T07:19:51.188623463Z"}
{"level":"info","msg":"/csi.v1.Node/NodeGetInfo: REP 0016: rpc error: code = FailedPrecondition desc = no topology keys could be generate","time":"2023-02-08T07:19:51.188642894Z"}
{"level":"info","msg":"/csi.v1.Identity/GetPluginInfo: REQ 0017: XXX_NoUnkeyedLiteral={}, XXX_sizecache=0","time":"2023-02-08T07:24:57.360533138Z"}
{"level":"info","msg":"/csi.v1.Identity/GetPluginInfo: REP 0017: Name=csi-powermax.dellemc.com, VendorVersion=2.3.0, Manifest=map[commit:9ee4c6afaedb58725f6518239fc527e076c3e0a9 formed:Tue, 14 Jun 202
{"level":"info","msg":"/csi.v1.Node/NodeGetInfo: REQ 0018: XXX_NoUnkeyedLiteral={}, XXX_sizecache=0","time":"2023-02-08T07:24:59.336730277Z"}
{"level":"error","msg":"Couldn't find any ip interfaces on any of the port-groups","time":"2023-02-08T07:24:59.336778092Z"}
{"level":"error","msg":"No topology keys could be generated","time":"2023-02-08T07:24:59.336785694Z"}
{"level":"info","msg":"/csi.v1.Node/NodeGetInfo: REP 0018: rpc error: code = FailedPrecondition desc = no topology keys could be generate","time":"2023-02-08T07:24:59.336800696Z"}

boyamurthy · 2023-02-08T07:44:53Z

hi @soudamsugit , the nodes which are failing would be having FC connection issues hence it is not creating any topology keys.
could you please check FC/iscsi connection for nodes .

soudamsugit · 2023-02-08T07:52:05Z

Thanks @boyamurthy, Can you pls let me know if any documentation on checking the FC/iscsi connection for nodes

boyamurthy · 2023-02-08T07:58:45Z

hi @soudamsugit , please find the documentation for prerequisites .
https://dell.github.io/csm-docs/docs/csidriver/installation/helm/powermax/#prerequisites

soudamsugit · 2023-02-08T08:17:51Z

Hello @boyamurthy

I had verified all the node having issues as per below documentation, and all seem to be looking fine but still getting errors

Set up the iSCSI initiators as follows:

soudamsugit · 2023-02-08T08:37:07Z

sh-4.4# rpm -qa | grep iscsi
iscsi-initiator-utils-iscsiuio-6.2.1.2-1.gita8fcb37.el8.x86_64
iscsi-initiator-utils-6.2.1.2-1.gita8fcb37.el8.x86_64
sh-4.4# storage
sh: storage: command not found
sh-4.4# cat /etc/iscsi/initiatorname.iscsi;
InitiatorName=iqn.1994-05.com.redhat:cfed26c7f7aa
sh-4.4# curl -v telnet://10.204.xxx.xx:8443

Rebuilt URL to: telnet://10.204.xxx.xx:8443/
Trying 10.204.xxx.xx...
TCP_NODELAY set
Connected to 10.204.xxx.xx (10.204.xxx.xx) port 8443 (#0)

rensyct · 2023-02-08T09:10:05Z

@soudamsugit , could we connect over a call so that the Powermax driver team can take a look at the environment to check the issue

soudamsugit · 2023-02-08T10:56:07Z

Thanks @rensyct @delldubey

Can we please connect tomorrow 9 AM IST on this issue?

rensyct · 2023-02-08T11:20:13Z

Hi @soudamsugit,
We can connect at 10:30 AM tomorrow. Please let us know if that time works for you

soudamsugit · 2023-02-08T21:42:16Z

Thanks @rensyct, 10:30 AM works fine

soudamsugit · 2023-02-09T04:57:47Z

is the invite. Can you guys pls join
https://teams.microsoft.com/l/meetup-join/19%3ameeting_NjM0Y2UxODMtNDg1MC00ZTExLTkyZWEtYzg3Njg3NGNkMjg4%40thread.v2/0?context=%7b%22Tid%22%3a%221f4f7eda-6e51-425e-a0f9-4c2fcef58a52%22%2c%22Oid%22%3a%2263a774a0-2e52-48bd-b0db-edde453cc553%22%7d

rensyct · 2023-02-09T04:59:45Z

Sure @soudamsugit

rensyct · 2023-02-09T08:57:27Z

Hi @soudamsugit

Posting the updates after today's call
@boyamurthy figured out that FC HBA's(WWN's ) are not having connectivity/zoning to the respective storage array . Hence it is failing to create initiator group and topology keys on the nodes where driver is in crashloopback state. We dont see a failure on the nodes where the zoning is done properly

Requested @soudamsugit to reach out to the storage team from their end and ensure that the zoning is done properly between the array and the host.

boyamurthy · 2023-02-13T06:50:56Z

hi @soudamsugit ,
if it is working fine, could you close this .

soudamsugit · 2023-02-14T00:18:54Z

Hello @rensyct,
Thank you for the support you provided, I am closing this case.
Appreciate the support you guys project

Regards,
Suresh

rensyct · 2023-02-14T05:02:20Z

Thank you @soudamsugit for the confirmation and for closing the case.
Thank you @boyamurthy and @delldubey for helping with the queries and looking into the configuration issues related to Powermax driver.

…and Resiliency" (#647) * Added support for csi-driver upgrades via csm-operator (#638) Updating documentation for k8s 1.27 (#643) * Revert "Updating documentation for k8s 1.27 (#643)" This reverts commit 2fc2a53. Signed-off-by: Peres Kereotubo <peres_kereotubo@dell.com> Revert "Updating documentation for k8s 1.27 (#643)" This reverts commit 2fc2a53. Revert "Updating documentation for k8s 1.27 (#643)" This reverts commit 2fc2a53. Revert "Updating documentation for k8s 1.27 (#643)" This reverts commit 2fc2a53. Revert "Updating documentation for k8s 1.27 (#643)" This reverts commit 2fc2a53. Revert "Updating documentation for k8s 1.27 (#643)" This reverts commit 2fc2a53. Reverting changes * Reverting changes * Updating documentation for k8s 1.27 (#643) * Revert "Updating documentation for k8s 1.27 (#643)" This reverts commit 2fc2a53. Signed-off-by: Peres Kereotubo <peres_kereotubo@dell.com> --------- Signed-off-by: Peres Kereotubo <peres_kereotubo@dell.com> Co-authored-by: Meghana GM <41953467+meggm@users.noreply.github.com>

soudamsugit added the type/question Ask a question. This is the default label associated with a question issue. label Feb 7, 2023

prablr79 assigned rajendraindukuri Feb 7, 2023

prablr79 added area/csi-unity Issue pertains to the CSI Driver for Dell EMC Unity area/dell-csi-operator labels Feb 7, 2023

prablr79 assigned satyakonduri Feb 7, 2023

rensyct removed the area/csi-unity Issue pertains to the CSI Driver for Dell EMC Unity label Feb 7, 2023

rajendraindukuri assigned rensyct and unassigned rajendraindukuri Feb 7, 2023

rensyct assigned boyamurthy Feb 8, 2023

rensyct assigned delldubey Feb 8, 2023

rensyct added the area/csi-powermax Issue pertains to the CSI Driver for Dell EMC PowerMax label Feb 8, 2023

rensyct added needs-triage Issue requires triage. backlog and removed type/question Ask a question. This is the default label associated with a question issue. labels Feb 8, 2023

soudamsugit closed this as completed Feb 14, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[QUESTION]: Post Upgrade of Dell CSI Operator on Openshift from 1.8 to 1.10, its not working anymore #647

[QUESTION]: Post Upgrade of Dell CSI Operator on Openshift from 1.8 to 1.10, its not working anymore #647

soudamsugit commented Feb 7, 2023

soudamsugit commented Feb 7, 2023

rensyct commented Feb 7, 2023

soudamsugit commented Feb 7, 2023 •

edited

Loading

rensyct commented Feb 7, 2023

soudamsugit commented Feb 7, 2023

soudamsugit commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

rensyct commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

rensyct commented Feb 8, 2023

rensyct commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

prablr79 commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

boyamurthy commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

boyamurthy commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

rensyct commented Feb 8, 2023 •

edited

Loading

soudamsugit commented Feb 8, 2023

rensyct commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

soudamsugit commented Feb 9, 2023

rensyct commented Feb 9, 2023

rensyct commented Feb 9, 2023

boyamurthy commented Feb 13, 2023

soudamsugit commented Feb 14, 2023

rensyct commented Feb 14, 2023

[QUESTION]: Post Upgrade of Dell CSI Operator on Openshift from 1.8 to 1.10, its not working anymore #647

[QUESTION]: Post Upgrade of Dell CSI Operator on Openshift from 1.8 to 1.10, its not working anymore #647

Comments

soudamsugit commented Feb 7, 2023

How can the Team help you today?

soudamsugit commented Feb 7, 2023

rensyct commented Feb 7, 2023

soudamsugit commented Feb 7, 2023 • edited Loading

rensyct commented Feb 7, 2023

soudamsugit commented Feb 7, 2023

soudamsugit commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

rensyct commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

rensyct commented Feb 8, 2023

rensyct commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

prablr79 commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

boyamurthy commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

boyamurthy commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

rensyct commented Feb 8, 2023 • edited Loading

soudamsugit commented Feb 8, 2023

rensyct commented Feb 8, 2023

soudamsugit commented Feb 8, 2023

soudamsugit commented Feb 9, 2023

rensyct commented Feb 9, 2023

rensyct commented Feb 9, 2023

boyamurthy commented Feb 13, 2023

soudamsugit commented Feb 14, 2023

rensyct commented Feb 14, 2023

soudamsugit commented Feb 7, 2023 •

edited

Loading

rensyct commented Feb 8, 2023 •

edited

Loading