Failed dm-devices visible after Upgrade of Trident from pre-22.07 to 22.10

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 134

Visibility:: Public

Votes:: 1

Category:: trident-openshift

Specialty:: snapx

Last Updated:

Applies to

Astra Trident versions 22.10 to 23.04 as upgrade targets

Issue

The following effects are visible after the upgrade to Trident version 22.10 (or higher):

| sddj: couldn't get target port group

| sdbv: couldn't get target port group

multipath -ll shows the following for a lot of /dev/sd... devices and multipathing devices:

3600a098038305654752b503177444141 dm-64 NETAPP  ,LUN C-Mode

size=SIZE_IN_G features='3 pg_init_retries 50 retain_attached_hw_handler' hwhandler='1 alua' wp=rw

|-+- policy='round-robin 0' prio=0 status=enabled

| `- 3:0:0:45 sddj 71:16  failed faulty running

`-+- policy='round-robin 0' prio=0 status=enabled

  `- 2:0:0:45 sdbv 68:144 failed faulty running

Additionally, syslog on the node shows the following errors for the underlying disk devices as well:

multipathd[991]: 3600a098038305654752b503177444141: sddj - tur checker reports path is down multipathd[991]: 3600a098038305654752b503177444141: sdbv - tur checker reports path is down