Random Satellite6 tasks turn into paused/error state

Solution Verified - Updated -

Issue

  • having dynflow executor memory limit enabled
  • random foreman/dynflow tasks end up in paused/error state, at random times
  • the tasks stay in that status forever, until human intervention

Environment

Red Hat Satellite 6.4 or newer

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In