Created attachment 786507 [details] Engine log Description of problem: When having a working DC with a couple of running VMs, the data domain's state moved to down and couldn't be brought back to state up. This might have something to do with the single host in the DC not chosen as the SPM despite being up (pressing "Select as SPM" doesn't work either). The possible trigger might have been that the engine changed IP address; I took my laptop home and ran the engine. Despite connecting to the VPN my IP address changed, the host's state changed to non-responsive and it was dropped as SPM, and the state of the VMs to unknown. When I connected from the office the next day, the host could be moved to up but couldn't regain its role as SPM, nor could the data domain be brought up. Version-Release number of selected component (if applicable): oVirt 3.3 master branch. How reproducible: Not sure. Additional info: Attached engine and relevant VDSM logs.
Created attachment 786508 [details] Latest VDSM log
Created attachment 786509 [details] Earlier VDSM log