Resolving an issue related to invalid nodepool
Invalid nodepool is mentioned in primary server or media server CR nodeSelector spec. Due to this, primary server or media server pod fails to schedule.
The following error is displayed:
Error: Did not match Pod's node affinity/selector.
To resolve an issue related to invalid nodepool
- For media server CR, ensure that you copy spec information of the media server CR. The spec information is used to reapply the media server CR.
- Edit the environment CR using the following command in primary/mediaServer section in environment CR update the nodeSelector, and save the changes
helm upgrade cloudscale cloudscale-<version>.tgz -n netbackup --reuse-values --set environment.primary.nodeSelector.labelKey=agentpool --set environment.primary.nodeSelector.labelValue=nbupoo