Instance in Paused State after setting Incorrect RAM Size

Solution Verified - Updated -

Issue

  • Instance was accidentally resized to a flavor with insufficient ram, preventing the instance from starting
  • Instance remains in paused state after attempting to start
  • Unable to resize paused instance with insufficient ram

Environment

  • Red Hat OpenStack Platform 10.0

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
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.