Media server remains in running state after Helm upgrade
After triggering a Helm upgrade for the media server, the media server custom resource (CR) does not transition to a successful state and continues to remain in the Running state.
This issue can occur when the environment.mediaServers[0].name value specified during the Helm upgrade does not match the existing media server name. Due to this mismatch, a new media server is created with a different name, but it is not properly registered with the storage server.
In this scenario, the NetBackup operator logs display an error similar to the following:
Error in registering additional media servers in storage server. Please add manually{"controller": "mediaserver", "controllerGroup": "netbackup.veritas.com", "controllerKind": "MediaServer","MediaServer": {"name":"new1","namespace":"netbackup"}, "namespace": "netbackup", "name": "new1","reconcileID": "6f45dee4-ff55-43b1-bb49-0482d5abb638","storage server id": "PureDisk:<storage server name>","error": "failed to update additional media server details for storage server: Failed to update storage server."}Workaround:
To resolve this issue, perform the following:
Log in to the primary server pod:
kubectl exec -it -n <namespace> <primary-server-pod-name> -- bash
Manually register the media server with the storage server using the tpconfig command:
tpconfig -add -storage_server <server_name> -stype <server_type> -sts_user_id <user_ID> -password <password>
Wait for the new media server to transition to the Success state.
Re-run the Helm upgrade command using the correct media server name to restore the original configuration.