My Favorites

Please login to see your favorites.

Bookmark

Resource nova-compute cannot be started

This document (7022317) is provided subject to the disclaimer at the end of this document.

Environment

SUSE OpenStack Cloud 6

Situation

In a cluster with two control nodes and two compute nodes configured as a remote Pacemaker nodes, resource nova-compute cannot be started. Whole environment has been patched and restarted.

Resolution

Check whether control node has attribute "evacuate" set to "Yes":

attrd_updater -p -n evacuate -N d94-18-82-7b-67-d0'.

Expected output:

name="evacuate" host="d94-18-82-7b-67-d0" value="yes"

Delete the attribute "evacuate":

attrd_updater -p -n evacuate -N d94-18-82-7b-67-d0 -D

In case that you didn't start your nodes yet, start the computes first then controllers. In such scenario the attribute will not be set.

Cause

If all nodes go down (during patching or power outage) and controller starts first, pacemaker receives timeout when starting remote-<mac> resources on compute nodes. Therefore it marks them "off" and prevents running of nova-compute by setting "evacuate" attribute. If computes are running, this situation shouldn't happen.

Status

Reported to Engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.