PowerVC, One inaccessible cluster (pvc-cluster) on one of three hosts caused the unavailability of all storage resources

Product version:
PowerVC 1.2.3.2

Customer sees this error:
NV-F991BC3 Cannot retrieve any VIOS clusters. ***K2 Operator Error***: HTTP error for GET /rest/api/uom/Cluster?group=None: 500 (Internal Server Error) [K2 Error body Message: Unexpected error occurred while fetching Cluster/SSP information : 8247-21L*2121E7A/1 : No partitions found in cluster ]
...
NV-FBD2B4D Host storage topology returned with an error condition set: [u'NV-F991BC3 Cannot retrieve any VIOS clusters. ***K2 Operator Error***: HTTP error for GET /rest/api/uom/Cluster?group=None: 500 (Internal Server Error) [K2 Error body Message: Unexpected error occurred while fetching Cluster/SSP information : 8247-21L*2121E7A/1 : No partitions found in cluster ]']

The client then reported:
Since there was no success with rebuilding the VIOS DB, we decided to delete and rebuild the cluster 'pvc-cluster'. Maybe the cluster was damaged during the last PowerVC migration from version 1.2.2.2 to 1.2.3.2 ?

So we deleted the cluster, reset rsct and created the pvc-cluster again. After that activity, the state of all storage provider related resources returned to OK (green) again. Also the state and health of the Boot Volumes is available / OK again.



Summary:

One inaccessible cluster (pvc-cluster) on one of three pSeries hosts also caused the unavailability of the storage resources on the other 2 pSeries hosts.

It looks like the PowerVC management host uses a one after another approach to check storage resources?

At least a problem with an independent cluster / storage pool (pvc-cluster) on pSeries 'AD-P801-8247-21L' caused also an inaccessibility of the resources on the other 2 pSeries 'AD-P802-8286-41A' and 'p6-14-8203-E4A'.
We think, this behaviour is not usable for a production environment.

Please let us know the opinion of the IBM PowerVC support team and whether there are enhancements in sight.