Red Hat Bugzilla – Bug 1249943
Failed to power fence host - No route to host
Last modified: 2015-08-04 08:25:09 EDT
Created attachment 1058983 [details]
Description of problem:
Host is not started automatically after turning it off manually in manager, even though power management is configured properly. However the host can be restarted through the engine's power management.
Version-Release number of selected component (if applicable):
always on my setup
Steps to Reproduce:
1. turn host down
2. wait for engine to try to start the host through power management
host wont start
host starts correctly
Host shouldn't be started automatically after they are brought down manually, whether by using the admin portal, or manually.
We only stop/start hosts automatically as part of the fencing mechanism.
Well, I was testing if it behaves the same as 3.5 after fencing refactoring, which after manual shutdown of host starts the host automatically, but I suppose that approach changed.
It hasn't changed.
I'm highly surprised that it happened before.
Only fencing triggers a flow of:
1. stop host
2. wait for it to be done (determined by power management)
3. start host
Manual stop isn't followed by manual start.