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
The resources weren't created successfully in the test "test_resize_osd_with_node_restart" with vSphere IPI.
The test pod didn't reach the Ready state:
E Warning FailedScheduling 5m2s default-scheduler 0/6 nodes are available: 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }, 3 node(s) had untolerated taint {node.ocs.openshift.io/storage: true}. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
The error above is with vSphere, which may indicate that it's related to a lack of resources. We should check locally to see if it failed with other platforms, such as AWS, GCP, or IBMCloud.
The text was updated successfully, but these errors were encountered:
The resources weren't created successfully in the test "test_resize_osd_with_node_restart" with vSphere IPI.
The test pod didn't reach the Ready state:
The error above is with vSphere, which may indicate that it's related to a lack of resources. We should check locally to see if it failed with other platforms, such as AWS, GCP, or IBMCloud.
The text was updated successfully, but these errors were encountered: