[documentation] Need to describe how to recover the node after cleaning of the full disks partitions on controller

Bug #1595146 reported by Timur Nurlygayanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel Documentation Team

Bug Description

We need to add the description of the recovering procedure for the following case:

1. Customer have HA environment with MOS 8.x-9.x
2. One partition on one controller become full (not enough free disk space error)
3. Pacemaker automatically shut down all services on this controller
4. Operator should login to the controller node, move/remove extra files from the disks and then execute the following command to recover pacemaker:
crm node status-attr `hostname -f` delete "#health_disk"

Other possible workarounds:
1. Restart pacemaker service:
service pacemaker restart
2. Reboot controller node

We need to describe in the documentation for OpenStack operators and support team the right workflow of recovering for this situation.

Please see comments from Vladimir Kuklin here for more detailed information:
https://bugs.launchpad.net/fuel/+bug/1595100

Tags: area-docs
Changed in fuel:
assignee: nobody → Fuel Documentation Team (fuel-docs)
milestone: none → 9.0
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
tags: added: area-docs
tags: removed: need-info
Revision history for this message
Alex Schultz (alex-schultz) wrote :
description: updated
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.