PowerMax - legacy PowerMax issue with generations
Bug #1938572 reported by
Helen Walsh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
Helen Walsh |
Bug Description
In the previous version of PowerMax OS and HyperMax OS, generations of snapVx were
used instead of unique snap ids which were just introduced.
A generation can be returned as a 0 integer which equates to False
in python. The fix is to convert the int to a string if it is
returned from REST as an int.
How to reproduce.
Older versions of PowerMax and HyperMax OS installed, Unisphere for PowerMax can return a 0 integer which causes a failure in snapshots
Changed in cinder: | |
assignee: | nobody → Helen Walsh (walshh2) |
Changed in cinder: | |
status: | New → In Progress |
Changed in cinder: | |
importance: | Undecided → Low |
tags: | added: hypermax powermax snapshot snapvx unisphere |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /cinder/ +/778907 /opendev. org/openstack/ cinder/ commit/ ee1b5e2b756f49a 384d348555e9611 526c0c1217
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit ee1b5e2b756f49a 384d348555e9611 526c0c1217
Author: Helen Walsh <email address hidden>
Date: Fri Mar 5 12:56:28 2021 +0000
PowerMax Driver - Fix for legacy PowerMax OS around generations
In the previous version of PowerMax OS generations of snapVx were
used instead of unique snap ids which were just introduced.
A generation can be returned as a 0 integer which equates to False
in python. The fix is to convert the int to a string if it is
returned from REST as an int.
Closes-Bug: #1938572 26296d6d3237bd3 b0d609f769f
Change-Id: I5b660776190f30