This bug was initially created as a copy of Bug #2276533

I am copying this bug because:

My TAM customer ran into the issue described in KCS 7041554 when upgrading their dev cluster from 4.12.40 to 4.13.45. They require a backport to 4.13 so they can upgrade their prod clusters.

Description of problem (please be detailed as possible and provide log:

Customer upgraded from 4.12.40 to 4.13.45 we have noticed that all OSDs are in crahs loop with the expand-bluefs container showing errors about devices that can not be found.

Version of all relevant components (if applicable):
ODF 4.13

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, all osds are down

Is there any workaround available to the best of your knowledge?
Yes. https://access.redhat.com/solutions/7041554

Can this issue reproducible?
yes, at customer environment