All container managed by pacemaker stopped during step2

Solution In Progress - Updated -

Issue

  • When we launch the overcloud deploy command on an existing running overcloud, all the containers managed by pacemaker are stopped for around 10mn during step2.

  • All API and floating ip are not available during this time frame.

  • This happens every time we're running an overcloud deploy

Environment

  • Red Hat OpenStack Platform 13.0 (RHOSP)

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