ops guide for ha tests needs to warn about using ifdown

Bug #1404418 reported by Andrew Woodward
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Meg McRoberts

Bug Description

In the ops guide we have information about performing HA tests at a couple of points we talking about 'unpluggin' interfaces.

this is known to cause splitbrain issues and should _NOT_ be performed.

Note: using ifdown, ifup or commands that would use them can cause the corosync service to update cluster state and in most cases will cause a split-brain and will result in an unsuccessful test. please use ip link down <ethX> instead or remove the link state from outside of the node (ie physically unplug)

Tags: docs
Andrew Woodward (xarses)
Changed in fuel:
status: New → Confirmed
importance: Undecided → High
Changed in fuel:
milestone: none → 6.0
Changed in fuel:
assignee: Fuel Documentation Team (fuel-docs) → Irina (ipovolotskaya)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-docs (master)

Fix proposed to branch: master
Review: https://review.openstack.org/143696

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-docs (master)

Reviewed: https://review.openstack.org/143696
Committed: https://git.openstack.org/cgit/stackforge/fuel-docs/commit/?id=9aaa8de5037a9325a56ffcef8a5672093e3d1e50
Submitter: Jenkins
Branch: master

commit 9aaa8de5037a9325a56ffcef8a5672093e3d1e50
Author: Irina Povolotskaya <email address hidden>
Date: Tue Dec 23 20:00:09 2014 +0300

    Adds a note about commands usage when running tests

    Change-Id: I86955583b0d79d7cbc569811bf09ee822d6487b0
    Closes-Bug: 1404418

Changed in fuel:
assignee: Irina (ipovolotskaya) → Meg McRoberts (dreidellhasa)
status: In Progress → Fix Committed
Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.