Review the error messages
You may see errors such as:

• ERROR, Failed to update the launchSpec ols-xxxxxxx with the latest changes in GKE cluster tagging-stg-xxx-x. Reason: Node pool tagging-stg-xxx-x does not exist.

• ERROR, Failed to update the group with the latest changes in GKE cluster tagging-stg-xxx-x. Reason: Node pool tagging-stg-xxx-x-pool does not exist.

These messages show that Flexera Ocean can’t access the original pool. This can happen if the original node pool is deleted, which prevents Ocean from fetching/updating the new GKE configuration. In the future, preserve the original node pool instead of deleting it. 

Verify whether the original node pool still exists
Check your GKE cluster to see if the node pool tied to the launchSpec has been removed. Ocean depends on this pool to fetch configuration details.

Choose one of these resolution options

• Option A: Re‑create the node pool

  Create a new node pool using the original name. It doesn’t need to run any active nodes, it only needs to exist so Flexera Ocean can retrieve settings.

• Option B: Remove and re-import the cluster

  Delete the cluster from the Flexera console (Actions > Delete cluster) or by using the Flexera API. Then import the cluster again through the Flexera console or the API. This ensures the control plane manager has the correct node pool configuration.
  
  

Trigger a configuration refresh
Flexera Ocean automatically checks for GKE configuration updates every 30 minutes. You can trigger this update manually in the Flexera console if you don’t want to wait.