Description of problem: Selecting a certain host as SPM is not available,UI reports vague message "Host $HOST_NAME was force selected by admin" nothing happens Version-Release number of selected component (if applicable): beta How reproducible: 100% Steps to Reproduce: Setup:have dc with 2 or more hosts 1.switch SPM vi UI's "Select as SPM" button Actual results: nothing happens but unclear UI message Expected results: a message on UI should be something like "switching host $HOST_NAME to be SPM" and the command should be executed. Additional info:
Steps to Reproduce(2): Setup:have dc with 2 or more hosts 1.maintain the SPM host Actual results: nothing happens but a UI message "Failed to change status of host 'vdsb' due to a failure to stop the spm."
Ori, please add engine and VDSM logs.
Created attachment 918339 [details] vdsm+engine logs sure Alon.
actually I have been mistaken regarding steps to reproduce,it seems that it is a little bit more tricky: Steps to Reproduce: Setup:have dc with 2 or more hosts 1.reboot the none-SPM host 2.while hosts reboot,remove dc 3.create a new dc (with domain) add the the two hosts 4.switch SPM twice
This bug isn't a regression, that was happening since this new command was introduced. removing the regression keyword.
verified on vt4
oVirt 3.5 has been released and should include the fix for this issue.