You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I also run into the similar error when using persistence volume for grafana.
One of my pods is stuck at pending state due to error pod (deis-monitor-grafana-465911159-nkhmp) failed to fit in any node fit failure summary on nodes : NoVolumeZoneConflict (2), PodToleratesNodeTaints (1). The followings are the zones my AWS resources running on:
It seems to be related to which zones the master/nodes are hosted on as it works by running the master, nodes, volume in different zones (don't have an example at this moment).
From @vdice on March 28, 2017 18:17
On GKE, upgrading with grafana persistence enabled leads to a
Failed to attach volume
error:Copied from original issue: deis/monitor#188
The text was updated successfully, but these errors were encountered: