If the environment does not progress and remains in the 1/4 Running state and mediaserver CR is not successful
If the environment does not progress and remains in the 2/3 Running state, verify the media server host mapping:
Check the NetBackup operator log for an error similar to the following:
ERROR Error in updating CS_POD_KEEP_LOG_SIZE_GB in bp.conf for MediaServer <prefix>-media-0 ... "error": "Error while fetching host ID: Error to get host uuid in get-host API call: Could not find host ID for server <prefix>-media-0"
Run the kubectl describe mediaserver -n <namespace> command and check whether the reconcilationDoneMedia section is present in the output.
If the reconcilationDoneMedia section is missing, remove the media server pod host mapping entry from the primary server. In the Web UI, navigate to , select the menu next to the primary server host name, select , delete the <prefix>-media-0 entry, and then click .
Delete the media server pod:
kubectl delete pod <prefix>-media-0 -n <namespace>
The operator adds the media server host mapping entry back to the primary server mappings automatically. Run the kubectl describe mediaserver -n <namespace> command again and confirm that the reconcilationDoneMedia section now lists the <prefix>-media-0 entry.
Note:
This is a timing related condition. It occurs when the host mapping for a newly deployed media server was not added on the first attempt.