Why dependent resources restart when doing `pcs resource create --force` but not when `pcs resource delete --force` is used?

Solution Unverified - Updated -

Issue

  • When the resource is removed using pcs resource delete --force cluster doesn't do anything to remaining resources, but same behaviour is not observed when the pcs resource create --force is used - the dependant resources are the restarted. Why doesn't --force behave same way in both pcs resource create and pcs resource delete?
  • Why creating resource in the middle of the resource group causes the dependent resources to restart even when --force is used?

Environment

  • Red Hat Enterprise Linux 7 with High-Availability or Resilient Storage add-on
  • pcs-0.9.152-10.el7_3.3

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.