Forum Discussion

amber_polak's avatar
amber_polak
Novice I
2 years ago
Solved

In general, is there a need to refresh, or remove/readd

In general, is there a need to refresh, or remove/readd storage provider registrations in VMWare, after upgrading Purity? I remember when moving from Purity 5.x to 6.x, there was a requirement, and it was specifically called out in release notes. We are moving from 6.1.x to 6.3.x, and am wondering if we need to do it again? I noticed the registration details in VMWare are not showing the correct Purity version for arrays that have already been upgraded.
  • Got the case opened - I can send it over to you if you want to take a look.
  • Unfortunately vcenter keeps that storage provider information kind of cached in the sps service. Which leads to the gui having out of date information for vasa provider version or purity version. While it will eventually update when vcenter is rebooted or services restarted, sometimes it's easier to just re-register the storage providers to get that reporting in vcenter up to date
  • We've tried working with vmware to get it so vcenter can update that info when an upgrade happens, and of the most part on the backend it does update and reflect the right info, but the gui just doesn't still.
  • I removed the CT1 registry last night, then this morning tried to re-register, and vcenter is telling me that the provider is already registered. It doesn't show in the GUI or via CLI's Get-VasaProvider. The CT0 controller is still registered and still shows the old version of Purity as well. Stuck.
  • That is a bit weird. Wonder if sps is holding something in the backend, but isn't returned back from queries. I have seen this before though, it's where the vcenter db doesn't actually correctly clean up the entries. Do you have a support case open with Pure yet?
  • Not yet - I was hoping it would be something simple. I'll get one opened now.
  • Got the case opened - I can send it over to you if you want to take a look.