Deregistering a VBR server is not working correctly

[kevin.boddy]

Hi,

Referring to cases #07964135 and #07976699. The deregister process does not appear to be working correctly.
If you deregister a VBR server it does not show it in the tenant's Vault workload registrations list anymore which is correct.

If you then try to authorize the VBR server again you get an error Exception of type 'System.Exception' was thrown and the VBR server still thinks it's authorized even though it's not.
Not sure where the fault lies but surely if you deregister a VBR server within Vault this should be communicated back to the VBR server. This would be the expected behaviour.

If you then authorize the VBR server again you will see in the VDC tenant workload registrations that the registration date is the previous date when the VBR server was first registered. This is incorrect. It should be the current date.
This would lead me to believe that the deregister process did not actually remove any of the VBR servers details during the deregister process and merely flagged it as hidden from view in Vault.

Thanks
Kevin

[Mildur]

Hi Kevin,

I see that case 07964135 has been escalated and is now with our R&D team.
Our QA and Development teams are currently discussing the details, so let’s wait for their conclusion.

Regarding the second case, it appears to be a different issue. Please continue working with our support team for now. If necessary, that case will also be escalated to R&D.

Best regards,
Fabian