Issue with storage policies being collected twice from vCenter to VCF Automation 9.
Article ID: 427245
Updated On:
Products
Issue/Introduction
After manually renaming a Storage Policy from vCenter, you can see both the current Storage Policy details as well as the renamed Storage Policy details visible in VCF Automation under the Region Quota for a given Organisation.
Environment
VCF Automation 9
VMware vSphere Kubernetes Services
Cause
Issue with Storage Policy naming convention manual change from VMware Kubernetes Service.
If you rename a Storage Policy from VMware vSphere Kubernetes Services and refresh the connection in the VCF Automation Provider Portal for the related vCenter then both the previous and current Storage Policies will show in VCF Automation.
Resolution
A resolution for this issue is scheduled for the upcoming VCF Automation 9.1 release. For immediate assistance in the meantime, please open a Support Request with Broadcom Technical Support and note this Article ID (427245) in the problem description. For more information, see Creating and managing Broadcom support cases.
Feedback
