Workspace fails to start and prevents node drain due to postStart timeout

Solution Verified - Updated -

Issue

  • When a workspace fails to start because the postStart command does not exit within the configured timeout period, the workspace pod becomes stuck in the Terminating state.

Environment

  • Red Hat OpenShift Container Platform 4 (RHOCP)

  • Red Hat OpenShift DevSpaces

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content