What exactly did you do? If you've changed the iSCSI storage connection, please check on the hosts if they have an open iSCSI session with the storage server. Run on both the active and the problematic hosts: iscsiadm -m session Check if there is any difference between them regarding the sessions they have with the storage. If they don't have the same sessions, try to rescan the targets and to login to them with 'iscsiadm' commands: For discover the target: iscsiadm -m discover -t st -p <storage_ip> --discover To login to the target: iscsiadm -m node <iqn> -l Run 'multipath -ll' to verify which LUNs they are connected to. ----- Original Message ----- From: "Koen Vanoppen" <vanoppen.koen(a)gmail.com&gt; To: users(a)ovirt.org Sent: Thursday, February 6, 2014 4:44:05 PM Subject: Re: [Users] Storage server Damn... I have 4 hosts in my domain. One host came back up succesfully after changing the ip. FOr the rest of the 3 hosts in the domain, they just won't come up. I tried everythin (I think). I removed the hosts from ovirt. Reinstalled the host rebooted the hosts. I have no further Idea's... THis is the error log: 2014-02-06 15:36:00,261 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (pool-6-thread-43) FINISH, ConnectStorageServerVDSCommand, return: {f3451e53-68ba-4c40-95ad-abe11ed975ff=0}, log id: 4f691c55 2014-02-06 15:36:00,264 INFO [org.ovirt.engine.core.bll.storage.ConnectDomainToStorageCommand] (DefaultQuartzScheduler_Worker-98) ConnectDomainToStorage. After Connect all hosts to pool. Time:2/6/14 3:36 PM 2014-02-06 15:36:03,309 INFO [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation soyuz.brusselsairport.aero : Stage: Misc configuration 2014-02-06 15:36:03,339 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1, Message: Installing Host soyuz. Stage: Misc configuration. 2014-02-06 15:36:03,339 INFO [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation soyuz.brusselsairport.aero : Setting time 2014-02-06 15:36:03,359 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1, Message: Installing Host soyuz. Setting time. 2014-02-06 15:36:07,118 INFO [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation soyuz.brusselsairport.aero : Enrolling certificate 2014-02-06 15:36:07,145 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1, Message: Installing Host soyuz. Enrolling certificate. 2014-02-06 15:36:08,306 INFO [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation soyuz.brusselsairport.aero : Stage: Transaction commit 2014-02-06 15:36:08,324 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1, Message: Installing Host soyuz. Stage: Transaction commit. 2014-02-06 15:36:08,373 INFO [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation soyuz.brusselsairport.aero : Stage: Closing up 2014-02-06 15:36:08,392 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1, Message: Installing Host soyuz. Stage: Closing up. 2014-02-06 15:36:09,371 INFO [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation soyuz.brusselsairport.aero : Starting vdsm 2014-02-06 15:36:09,389 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1, Message: Installing Host soyuz. Starting vdsm. 2014-02-06 15:36:14,409 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-45) Command org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand return value StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=304, mMessage=Cannot find master domain: 'spUUID=5849b030-626e-47cb-ad90-3ce782d831b3, msdUUID=f3fd055b-2764-44ed-9d77-81bd58984842']] 2014-02-06 15:36:14,418 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-45) HostName = progress 2014-02-06 15:36:14,421 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-45) Command ConnectStoragePoolVDS execution failed. Exception: IRSNoMasterDomainException: IRSGenericException: IRSErrorException: IRSNoMasterDomainException: Cannot find master domain: 'spUUID=5849b030-626e-47cb-ad90-3ce782d831b3, msdUUID=f3fd055b-2764-44ed-9d77-81bd58984842' 2014-02-06 15:36:14,428 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-45) FINISH, ConnectStoragePoolVDSCommand, log id: 644a6ef6 2014-02-06 15:36:14,431 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-45) Could not connect host progress to pool Test-Dev 2014-02-06 15:36:14,472 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-48) START, ConnectStoragePoolVDSCommand(HostName = buran, HostId = 8d777379-2d3f-4b2f-80b7-f3905d9db78e, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, vds_spm_id = 3, masterDomainId = f3fd055b-2764-44ed-9d77-81bd58984842, masterVersion = 3), log id: d77ff5c 2014-02-06 15:36:14,495 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (DefaultQuartzScheduler_Worker-8) Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 7ab1a0d7-8c72-44d1-9cb5-320c456be77d Type: VDS 2014-02-06 15:36:14,557 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-8) START, SetVdsStatusVDSCommand(HostName = progress, HostId = 7ab1a0d7-8c72-44d1-9cb5-320c456be77d, status=NonOperational, nonOperationalReason=STORAGE_DOMAIN_UNREACHABLE), log id: 432ba3a7 2014-02-06 15:36:14,568 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-8) FINISH, SetVdsStatusVDSCommand, log id: 432ba3a7 2014-02-06 15:36:14,584 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-8) Correlation ID: 411df7ec, Job ID: 9b3b5aef-797e-4545-90e6-1c7776f6d286, Call Stack: null, Custom Event ID: -1, Message: Host progress cannot access one of the Storage Domains attached to the Data Center Test-Dev. Setting Host state to Non-Operational. 2014-02-06 15:36:14,652 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-8) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Power Management test failed for Host progress.There is no other host in the data center that can be used to test the power management settings. 2014-02-06 15:36:14,658 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-8) Correlation ID: 3e035b12, Call Stack: null, Custom Event ID: -1, Message: Failed to connect Host progress to Storage Pool Test-Dev 2014-02-06 15:36:14,663 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler_Worker-8) Initializing Host: progress 2014-02-06 15:36:14,683 INFO [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (DefaultQuartzScheduler_Worker-8) Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 7ab1a0d7-8c72-44d1-9cb5-320c456be77d Type: VDS 2014-02-06 15:36:14,704 INFO [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (DefaultQuartzScheduler_Worker-8) Running command: HandleVdsVersionCommand internal: true. Entities affected : ID: 7ab1a0d7-8c72-44d1-9cb5-320c456be77d Type: VDS 2014-02-06 15:36:14,708 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-8) Host 7ab1a0d7-8c72-44d1-9cb5-320c456be77d : progress is already in NonOperational status. SetNonOperationalVds command is skipped. 2014-02-06 15:36:27,361 INFO [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (pool-6-thread-43) [2203da18] Running command: MaintenanceNumberOfVdssCommand internal: false. Entities affected : ID: 7ab1a0d7-8c72-44d1-9cb5-320c456be77d Type: VDS 2014-02-06 15:36:27,388 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-6-thread-43) [2203da18] START, SetVdsStatusVDSCommand(HostName = progress, HostId = 7ab1a0d7-8c72-44d1-9cb5-320c456be77d, status=PreparingForMaintenance, nonOperationalReason=NONE), log id: 266ce176 2014-02-06 15:36:27,394 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-6-thread-43) [2203da18] FINISH, SetVdsStatusVDSCommand, log id: 266ce176 2014-02-06 15:36:27,529 INFO [org.ovirt.engine.core.bll.MaintenanceVdsCommand] (pool-6-thread-43) [2203da18] Running command: MaintenanceVdsCommand internal: true. Entities affected : ID: 7ab1a0d7-8c72-44d1-9cb5-320c456be77d Type: VDS 2014-02-06 15:36:27,548 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-6-thread-43) [2203da18] Correlation ID: 2203da18, Job ID: e59d4cd6-8c81-40a2-b333-674de1a9ad08, Call Stack: null, Custom Event ID: -1, Message: Host progress was switched to Maintenance mode by admin@internal. 2014-02-06 15:36:29,867 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-67) Updated vds status from Preparing for Maintenance to Maintenance in database, vds = 7ab1a0d7-8c72-44d1-9cb5-320c456be77d : progress 2014-02-06 15:36:53,120 INFO [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation soyuz.brusselsairport.aero : Stage: Pre-termination 2014-02-06 15:36:53,173 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1, Message: Installing Host soyuz. Stage: Pre-termination. 2014-02-06 15:36:53,192 INFO [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation soyuz.brusselsairport.aero : Retrieving installation logs to: '/var/log/ovirt-engine/host-deploy/ovirt-20140206153653-soyuz.brusselsairport.aero-43728c8d.log' 2014-02-06 15:36:53,242 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1, Message: Installing Host soyuz. Retrieving installation logs to: '/var/log/ovirt-engine/host-deploy/ovirt-20140206153653-soyuz.brusselsairport.aero-43728c8d.log'. 2014-02-06 15:36:53,729 INFO [org.ovirt.engine.core.bll.InstallerMessages] (VdsDeploy) Installation soyuz.brusselsairport.aero : Stage: Termination 2014-02-06 15:36:53,794 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) Correlation ID: 43728c8d, Call Stack: null, Custom Event ID: -1, Message: Installing Host soyuz. Stage: Termination. 2014-02-06 15:36:53,831 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-50) java.util.concurrent.ExecutionException: java.lang.reflect.InvocationTargetException 2014-02-06 15:36:53,839 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-50) Command PollVDS execution failed. Exception: RuntimeException: java.util.concurrent.ExecutionException: java.lang.reflect.InvocationTargetException 2014-02-06 15:36:54,351 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-50) java.util.concurrent.ExecutionException: java.lang.reflect.InvocationTargetException 2014-02-06 15:36:54,352 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (pool-6-thread-50) Command PollVDS execution failed. Exception: RuntimeException: java.util.concurrent.ExecutionException: java.lang.reflect.InvocationTargetException 2014-02-06 15:36:54,895 INFO [org.ovirt.engine.core.bll.network.NetworkConfigurator] (pool-6-thread-50) Engine managed to communicate with VDSM agent on host soyuz 2014-02-06 15:36:55,709 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-6-thread-50) START, SetVdsStatusVDSCommand(HostName = soyuz, HostId = 35f37cb4-0f93-4f21-bd0b-20327c96cdb8, status=Initializing, nonOperationalReason=NONE), log id: 224c09f9 2014-02-06 15:36:55,732 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-6-thread-50) FINISH, SetVdsStatusVDSCommand, log id: 224c09f9 2014-02-06 15:36:55,736 INFO [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-6-thread-50) After Installation host soyuz, VDS 2014-02-06 15:36:55,747 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-6-thread-50) Correlation ID: 43728c8d, Job ID: 9b8f065c-efab-4dd7-8ab1-a599674c4881, Call Stack: null, Custom Event ID: -1, Message: Host soyuz installed 2014-02-06 15:36:55,752 INFO [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-6-thread-50) Lock freed to object EngineLock [exclusiveLocks= key: 35f37cb4-0f93-4f21-bd0b-20327c96cdb8 value: VDS , sharedLocks= ] 2014-02-06 15:36:58,402 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-52) START, GetHardwareInfoVDSCommand(HostName = soyuz, HostId = 35f37cb4-0f93-4f21-bd0b-20327c96cdb8, vds=Host[soyuz]), log id: 65c31dd5 2014-02-06 15:36:58,488 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-52) FINISH, GetHardwareInfoVDSCommand, log id: 65c31dd5 2014-02-06 15:36:58,660 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-52) START, GetHardwareInfoVDSCommand(HostName = soyuz, HostId = 35f37cb4-0f93-4f21-bd0b-20327c96cdb8, vds=Host[soyuz]), log id: 1c804bfc 2014-02-06 15:36:58,675 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetHardwareInfoVDSCommand] (DefaultQuartzScheduler_Worker-52) FINISH, GetHardwareInfoVDSCommand, log id: 1c804bfc 2014-02-06 15:36:58,747 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-52) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: State was set to Up for host soyuz. 2014-02-06 15:36:58,760 INFO [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (DefaultQuartzScheduler_Worker-52) Running command: InitVdsOnUpCommand internal: true. Entities affected : ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool 2014-02-06 15:36:58,768 INFO [org.ovirt.engine.core.bll.storage.ConnectHostToStoragePoolServersCommand] (DefaultQuartzScheduler_Worker-52) Running command: ConnectHostToStoragePoolServersCommand internal: true. Entities affected : ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool 2014-02-06 15:36:58,893 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-52) START, ConnectStorageServerVDSCommand(HostName = soyuz, HostId = 35f37cb4-0f93-4f21-bd0b-20327c96cdb8, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, storageType = ISCSI, connectionList = [{ id: c20125b0-1600-4f69-bb1c-c9d0c1f289ce, connection: 172.16.90.103, iqn: iqn.2004-09.com.hp:fcgw.mez75.2.01.5001438011399129, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };{ id: 61d30940-e328-4bf1-91fd-20f07ef7b1c0, connection: 172.16.90.103, iqn: iqn.2004-09.com.hp:fcgw.mez75.2.01.500143801139912d, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: 1db9564 2014-02-06 15:37:38,515 INFO [org.ovirt.engine.core.bll.network.host.SetupNetworksCommand] (ajp--127.0.0.1-8702-6) Running command: SetupNetworksCommand internal: false. Entities affected : ID: 7ab1a0d7-8c72-44d1-9cb5-320c456be77d Type: VDS 2014-02-06 15:37:38,602 INFO [org.ovirt.engine.core.bll.network.host.CommitNetworkChangesCommand] (ajp--127.0.0.1-8702-5) Running command: CommitNetworkChangesCommand internal: false. Entities affected : ID: 7ab1a0d7-8c72-44d1-9cb5-320c456be77d Type: VDS 2014-02-06 15:37:38,638 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetSafeNetworkConfigVDSCommand] (ajp--127.0.0.1-8702-5) START, SetSafeNetworkConfigVDSCommand(HostName = progress, HostId = 7ab1a0d7-8c72-44d1-9cb5-320c456be77d), log id: 6d4fc4e7 2014-02-06 15:37:38,660 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetSafeNetworkConfigVDSCommand] (ajp--127.0.0.1-8702-5) FINISH, SetSafeNetworkConfigVDSCommand, log id: 6d4fc4e7 2014-02-06 15:37:38,665 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-5) Correlation ID: 53ec69d5, Job ID: 07dfe601-d101-4564-9086-b3ae39d091a1, Call Stack: null, Custom Event ID: -1, Message: Network changes were saved on host progress 2014-02-06 15:38:12,342 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-48) Command org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand return value StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=304, mMessage=Cannot find master domain: 'spUUID=5849b030-626e-47cb-ad90-3ce782d831b3, msdUUID=f3fd055b-2764-44ed-9d77-81bd58984842']] 2014-02-06 15:38:12,343 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-48) HostName = buran 2014-02-06 15:38:12,345 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-48) Command ConnectStoragePoolVDS execution failed. Exception: IRSNoMasterDomainException: IRSGenericException: IRSErrorException: IRSNoMasterDomainException: Cannot find master domain: 'spUUID=5849b030-626e-47cb-ad90-3ce782d831b3, msdUUID=f3fd055b-2764-44ed-9d77-81bd58984842' 2014-02-06 15:38:12,347 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-48) FINISH, ConnectStoragePoolVDSCommand, log id: d77ff5c 2014-02-06 15:38:12,350 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-48) Could not connect host buran to pool Test-Dev 2014-02-06 15:38:12,359 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (pool-6-thread-45) Clearing cache of pool: 5849b030-626e-47cb-ad90-3ce782d831b3 for problematic entities of VDS: progress. 2014-02-06 15:38:12,395 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand] (DefaultQuartzScheduler_Worker-67) START, DisconnectStoragePoolVDSCommand(HostName = progress, HostId = 7ab1a0d7-8c72-44d1-9cb5-320c456be77d, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, vds_spm_id = 2), log id: 45481fd6 2014-02-06 15:38:12,434 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (DefaultQuartzScheduler_Worker-9) Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 8d777379-2d3f-4b2f-80b7-f3905d9db78e Type: VDS 2014-02-06 15:38:12,502 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand] (DefaultQuartzScheduler_Worker-67) FINISH, DisconnectStoragePoolVDSCommand, log id: 45481fd6 2014-02-06 15:38:12,503 INFO [org.ovirt.engine.core.bll.storage.DisconnectHostFromStoragePoolServersCommand] (DefaultQuartzScheduler_Worker-67) Running command: DisconnectHostFromStoragePoolServersCommand internal: true. Entities affected : ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool 2014-02-06 15:38:12,544 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-9) START, SetVdsStatusVDSCommand(HostName = buran, HostId = 8d777379-2d3f-4b2f-80b7-f3905d9db78e, status=NonOperational, nonOperationalReason=STORAGE_DOMAIN_UNREACHABLE), log id: 5f3ae88b 2014-02-06 15:38:12,571 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-9) FINISH, SetVdsStatusVDSCommand, log id: 5f3ae88b 2014-02-06 15:38:12,591 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-9) Correlation ID: 721270c3, Job ID: d4b7ff29-b848-40ec-ada9-cb1e80c854e0, Call Stack: null, Custom Event ID: -1, Message: Host buran cannot access one of the Storage Domains attached to the Data Center Test-Dev. Setting Host state to Non-Operational. 2014-02-06 15:38:12,753 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-9) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Power Management test failed for Host buran.There is no other host in the data center that can be used to test the power management settings. 2014-02-06 15:38:12,756 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-67) START, DisconnectStorageServerVDSCommand(HostName = progress, HostId = 7ab1a0d7-8c72-44d1-9cb5-320c456be77d, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, storageType = ISCSI, connectionList = [{ id: c20125b0-1600-4f69-bb1c-c9d0c1f289ce, connection: 172.16.90.103, iqn: iqn.2004-09.com.hp:fcgw.mez75.2.01.5001438011399129, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };{ id: 61d30940-e328-4bf1-91fd-20f07ef7b1c0, connection: 172.16.90.103, iqn: iqn.2004-09.com.hp:fcgw.mez75.2.01.500143801139912d, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: 1438e342 2014-02-06 15:38:12,779 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-9) Correlation ID: 60d23644, Call Stack: null, Custom Event ID: -1, Message: Failed to connect Host buran to Storage Pool Test-Dev 2014-02-06 15:38:12,801 INFO [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler_Worker-9) Initializing Host: buran 2014-02-06 15:38:12,880 INFO [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (DefaultQuartzScheduler_Worker-9) Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 8d777379-2d3f-4b2f-80b7-f3905d9db78e Type: VDS 2014-02-06 15:38:12,919 INFO [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (DefaultQuartzScheduler_Worker-9) Running command: HandleVdsVersionCommand internal: true. Entities affected : ID: 8d777379-2d3f-4b2f-80b7-f3905d9db78e Type: VDS 2014-02-06 15:38:12,922 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-9) Host 8d777379-2d3f-4b2f-80b7-f3905d9db78e : buran is already in NonOperational status. SetNonOperationalVds command is skipped. 2014-02-06 15:38:14,895 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-67) FINISH, DisconnectStorageServerVDSCommand, return: {c20125b0-1600-4f69-bb1c-c9d0c1f289ce=0, 61d30940-e328-4bf1-91fd-20f07ef7b1c0=0}, log id: 1438e342 2014-02-06 15:38:14,926 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-67) START, DisconnectStorageServerVDSCommand(HostName = progress, HostId = 7ab1a0d7-8c72-44d1-9cb5-320c456be77d, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, storageType = NFS, connectionList = [{ id: 4af8d33f-679d-4c6b-b93e-1ba08b8510ce, connection: vega.brusselsairport.aero:/var/lib/exports/iso, iqn: null, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: cb1c8ea 2014-02-06 15:38:17,073 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-67) FINISH, DisconnectStorageServerVDSCommand, return: {4af8d33f-679d-4c6b-b93e-1ba08b8510ce=0}, log id: cb1c8ea 2014-02-06 15:38:17,102 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-67) START, DisconnectStorageServerVDSCommand(HostName = progress, HostId = 7ab1a0d7-8c72-44d1-9cb5-320c456be77d, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, storageType = NFS, connectionList = [{ id: f3451e53-68ba-4c40-95ad-abe11ed975ff, connection: buran.brusselsairport.aero:/root/NfsStorageBuran, iqn: null, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: 1250f642 2014-02-06 15:38:19,230 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-67) FINISH, DisconnectStorageServerVDSCommand, return: {f3451e53-68ba-4c40-95ad-abe11ed975ff=477}, log id: 1250f642 2014-02-06 15:38:27,172 INFO [org.ovirt.engine.core.bll.MaintenanceNumberOfVdssCommand] (pool-6-thread-48) [3245c5b5] Running command: MaintenanceNumberOfVdssCommand internal: false. Entities affected : ID: 8d777379-2d3f-4b2f-80b7-f3905d9db78e Type: VDS 2014-02-06 15:38:27,214 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-6-thread-48) [3245c5b5] START, SetVdsStatusVDSCommand(HostName = buran, HostId = 8d777379-2d3f-4b2f-80b7-f3905d9db78e, status=PreparingForMaintenance, nonOperationalReason=NONE), log id: 54962eb0 2014-02-06 15:38:27,222 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-6-thread-48) [3245c5b5] FINISH, SetVdsStatusVDSCommand, log id: 54962eb0 2014-02-06 15:38:27,329 INFO [org.ovirt.engine.core.bll.MaintenanceVdsCommand] (pool-6-thread-48) [3245c5b5] Running command: MaintenanceVdsCommand internal: true. Entities affected : ID: 8d777379-2d3f-4b2f-80b7-f3905d9db78e Type: VDS 2014-02-06 15:38:27,338 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (pool-6-thread-48) [3245c5b5] Correlation ID: 3245c5b5, Job ID: 15347f93-fcfc-4517-8bc4-bbac6d1615bd, Call Stack: null, Custom Event ID: -1, Message: Host buran was switched to Maintenance mode by admin@internal. 2014-02-06 15:38:28,183 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-6) Updated vds status from Preparing for Maintenance to Maintenance in database, vds = 8d777379-2d3f-4b2f-80b7-f3905d9db78e : buran 2014-02-06 15:38:28,194 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (pool-6-thread-46) Clearing cache of pool: 5849b030-626e-47cb-ad90-3ce782d831b3 for problematic entities of VDS: buran. 2014-02-06 15:38:28,243 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand] (DefaultQuartzScheduler_Worker-6) START, DisconnectStoragePoolVDSCommand(HostName = buran, HostId = 8d777379-2d3f-4b2f-80b7-f3905d9db78e, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, vds_spm_id = 3), log id: 3ad44b37 2014-02-06 15:38:28,264 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStoragePoolVDSCommand] (DefaultQuartzScheduler_Worker-6) FINISH, DisconnectStoragePoolVDSCommand, log id: 3ad44b37 2014-02-06 15:38:28,265 INFO [org.ovirt.engine.core.bll.storage.DisconnectHostFromStoragePoolServersCommand] (DefaultQuartzScheduler_Worker-6) Running command: DisconnectHostFromStoragePoolServersCommand internal: true. Entities affected : ID: 5849b030-626e-47cb-ad90-3ce782d831b3 Type: StoragePool 2014-02-06 15:38:28,374 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-6) START, DisconnectStorageServerVDSCommand(HostName = buran, HostId = 8d777379-2d3f-4b2f-80b7-f3905d9db78e, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, storageType = ISCSI, connectionList = [{ id: c20125b0-1600-4f69-bb1c-c9d0c1f289ce, connection: 172.16.90.103, iqn: iqn.2004-09.com.hp:fcgw.mez75.2.01.5001438011399129, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };{ id: 61d30940-e328-4bf1-91fd-20f07ef7b1c0, connection: 172.16.90.103, iqn: iqn.2004-09.com.hp:fcgw.mez75.2.01.500143801139912d, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: 26c57238 2014-02-06 15:38:30,497 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-6) FINISH, DisconnectStorageServerVDSCommand, return: {c20125b0-1600-4f69-bb1c-c9d0c1f289ce=0, 61d30940-e328-4bf1-91fd-20f07ef7b1c0=0}, log id: 26c57238 2014-02-06 15:38:30,527 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-6) START, DisconnectStorageServerVDSCommand(HostName = buran, HostId = 8d777379-2d3f-4b2f-80b7-f3905d9db78e, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, storageType = NFS, connectionList = [{ id: 4af8d33f-679d-4c6b-b93e-1ba08b8510ce, connection: vega.brusselsairport.aero:/var/lib/exports/iso, iqn: null, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: 6365b27b 2014-02-06 15:38:33,830 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-6) FINISH, DisconnectStorageServerVDSCommand, return: {4af8d33f-679d-4c6b-b93e-1ba08b8510ce=0}, log id: 6365b27b 2014-02-06 15:38:33,860 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-6) START, DisconnectStorageServerVDSCommand(HostName = buran, HostId = 8d777379-2d3f-4b2f-80b7-f3905d9db78e, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, storageType = NFS, connectionList = [{ id: f3451e53-68ba-4c40-95ad-abe11ed975ff, connection: buran.brusselsairport.aero:/root/NfsStorageBuran, iqn: null, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: 6d41bbb8 2014-02-06 15:38:36,002 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DisconnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-6) FINISH, DisconnectStorageServerVDSCommand, return: {f3451e53-68ba-4c40-95ad-abe11ed975ff=0}, log id: 6d41bbb8 2014-02-06 15:39:58,911 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-52) Command ConnectStorageServerVDS execution failed. Exception: VDSNetworkException: java.util.concurrent.TimeoutException 2014-02-06 15:39:58,916 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (DefaultQuartzScheduler_Worker-52) FINISH, ConnectStorageServerVDSCommand, log id: 1db9564 2014-02-06 15:39:58,921 ERROR [org.ovirt.engine.core.bll.storage.ConnectHostToStoragePoolServersCommand] (DefaultQuartzScheduler_Worker-52) Command org.ovirt.engine.core.bll.storage.ConnectHostToStoragePoolServersCommand throw Vdc Bll exception. With error message VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: java.util.concurrent.TimeoutException (Failed with error VDS_NETWORK_ERROR and code 5022) 2014-02-06 15:39:58,989 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-46) START, ConnectStoragePoolVDSCommand(HostName = soyuz, HostId = 35f37cb4-0f93-4f21-bd0b-20327c96cdb8, storagePoolId = 5849b030-626e-47cb-ad90-3ce782d831b3, vds_spm_id = 4, masterDomainId = f3fd055b-2764-44ed-9d77-81bd58984842, masterVersion = 3), log id: 776585bc 2014-02-06 15:40:00,012 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (DefaultQuartzScheduler_Worker-31) Autorecovering 1 storage domains 2014-02-06 15:40:00,013 INFO [org.ovirt.engine.core.bll.AutoRecoveryManager] (DefaultQuartzScheduler_Worker-31) Autorecovering storage domains id: 83b1867f-4aea-400e-9ce0-efbd5add4216 2014-02-06 15:40:00,015 INFO [org.ovirt.engine.core.bll.storage.ConnectDomainToStorageCommand] (DefaultQuartzScheduler_Worker-31) Running command: ConnectDomainToStorageCommand internal: true. Entities affected : ID: 83b1867f-4aea-400e-9ce0-efbd5add4216 Type: Storage 2014-02-06 15:40:00,023 INFO [org.ovirt.engine.core.bll.storage.ConnectDomainToStorageCommand] (DefaultQuartzScheduler_Worker-31) ConnectDomainToStorage. Before Connect all hosts to pool. Time:2/6/14 3:40 PM 2014-02-06 15:40:00,064 INFO [org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand] (pool-6-thread-47) Running command: ConnectStorageToVdsCommand internal: true. Entities affected : ID: aaa00000-0000-0000-0000-123456789aaa Type: System 2014-02-06 15:40:00,178 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (pool-6-thread-47) START, ConnectStorageServerVDSCommand(HostName = vostok, HostId = 2a8b1829-2235-44db-be12-ac71dc6777f8, storagePoolId = 00000000-0000-0000-0000-000000000000, storageType = NFS, connectionList = [{ id: f3451e53-68ba-4c40-95ad-abe11ed975ff, connection: buran.brusselsairport.aero:/root/NfsStorageBuran, iqn: null, vfsType: null, mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log id: 6a3abae9 2014-02-06 15:40:47,341 INFO [org.ovirt.engine.core.bll.network.host.SetupNetworksCommand] (ajp--127.0.0.1-8702-2) Running command: SetupNetworksCommand internal: false. Entities affected : ID: 8d777379-2d3f-4b2f-80b7-f3905d9db78e Type: VDS 2014-02-06 15:40:55,442 INFO [org.ovirt.engine.core.bll.network.host.SetupNetworksCommand] (ajp--127.0.0.1-8702-6) Running command: SetupNetworksCommand internal: false. Entities affected : ID: 8d777379-2d3f-4b2f-80b7-f3905d9db78e Type: VDS 2014-02-06 15:40:55,488 INFO [org.ovirt.engine.core.bll.network.host.CommitNetworkChangesCommand] (ajp--127.0.0.1-8702-12) Running command: CommitNetworkChangesCommand internal: false. Entities affected : ID: 8d777379-2d3f-4b2f-80b7-f3905d9db78e Type: VDS 2014-02-06 15:40:55,507 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetSafeNetworkConfigVDSCommand] (ajp--127.0.0.1-8702-12) START, SetSafeNetworkConfigVDSCommand(HostName = buran, HostId = 8d777379-2d3f-4b2f-80b7-f3905d9db78e), log id: 320cfe56 2014-02-06 15:40:55,531 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetSafeNetworkConfigVDSCommand] (ajp--127.0.0.1-8702-12) FINISH, SetSafeNetworkConfigVDSCommand, log id: 320cfe56 2014-02-06 15:40:55,538 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-12) Correlation ID: 809fe4a, Job ID: 35117851-fc65-489e-a90a-885de1d62b80, Call Stack: null, Custom Event ID: -1, Message: Network changes were saved on host buran 2014-02-06 15:41:00,264 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] (pool-6-thread-47) FINISH, ConnectStorageServerVDSCommand, return: {f3451e53-68ba-4c40-95ad-abe11ed975ff=0}, log id: 6a3abae9 2014-02-06 15:41:00,266 INFO [org.ovirt.engine.core.bll.storage.ConnectDomainToStorageCommand] (DefaultQuartzScheduler_Worker-31) ConnectDomainToStorage. After Connect all hosts to pool. Time:2/6/14 3:41 PM 2014-02-06 15:41:05,360 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-46) Command org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand return value StatusOnlyReturnForXmlRpc [mStatus=StatusForXmlRpc [mCode=304, mMessage=Cannot find master domain: 'spUUID=5849b030-626e-47cb-ad90-3ce782d831b3, msdUUID=f3fd055b-2764-44ed-9d77-81bd58984842']] 2014-02-06 15:41:05,361 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-46) HostName = soyuz 2014-02-06 15:41:05,362 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-46) Command ConnectStoragePoolVDS execution failed. Exception: IRSNoMasterDomainException: IRSGenericException: IRSErrorException: IRSNoMasterDomainException: Cannot find master domain: 'spUUID=5849b030-626e-47cb-ad90-3ce782d831b3, msdUUID=f3fd055b-2764-44ed-9d77-81bd58984842' 2014-02-06 15:41:05,362 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStoragePoolVDSCommand] (pool-6-thread-46) FINISH, ConnectStoragePoolVDSCommand, log id: 776585bc 2014-02-06 15:41:05,363 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-46) Could not connect host soyuz to pool Test-Dev 2014-02-06 15:41:05,386 INFO [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (DefaultQuartzScheduler_Worker-52) Running command: SetNonOperationalVdsCommand internal: true. Entities affected : ID: 35f37cb4-0f93-4f21-bd0b-20327c96cdb8 Type: VDS 2014-02-06 15:41:05,405 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-52) START, SetVdsStatusVDSCommand(HostName = soyuz, HostId = 35f37cb4-0f93-4f21-bd0b-20327c96cdb8, status=NonOperational, nonOperationalReason=STORAGE_DOMAIN_UNREACHABLE), log id: 249f8181 2014-02-06 15:41:05,410 INFO [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (DefaultQuartzScheduler_Worker-52) FINISH, SetVdsStatusVDSCommand, log id: 249f8181 2014-02-06 15:41:05,417 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-52) Correlation ID: 68bef83b, Job ID: acc010e5-32a7-4a3c-b6bc-2b315db478e6, Call Stack: null, Custom Event ID: -1, Message: Host soyuz cannot access one of the Storage Domains attached to the Data Center Test-Dev. Setting Host state to Non-Operational. 2014-02-06 15:41:05,442 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-52) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: Power Management test failed for Host soyuz.There is no other host in the data center that can be used to test the power management settings. 2014-02-06 15:41:05,447 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-52) Correlation ID: 5f74bf21, Call Stack: null, Custom Event ID: -1, Message: Failed to connect Host soyuz to Storage Pool Test-Dev 2014-02-06 15:41:05,467 INFO [org.ovirt.engine.core.bll.HandleVdsCpuFlagsOrClusterChangedCommand] (DefaultQuartzScheduler_Worker-52) Running command: HandleVdsCpuFlagsOrClusterChangedCommand internal: true. Entities affected : ID: 35f37cb4-0f93-4f21-bd0b-20327c96cdb8 Type: VDS 2014-02-06 15:41:05,489 INFO [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (DefaultQuartzScheduler_Worker-52) Running command: HandleVdsVersionCommand internal: true. Entities affected : ID: 35f37cb4-0f93-4f21-bd0b-20327c96cdb8 Type: VDS 2014-02-06 15:41:05,493 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-52) Host 35f37cb4-0f93-4f21-bd0b-20327c96cdb8 : soyuz is already in NonOperational status. SetNonOperationalVds command is skipped. 2014-02-06 Koen Vanoppen < vanoppen.koen(a)gmail.com > : Thanks. Found the command! For further reference to users: update storageconnection <storageconnectionid> --address <IP-Address> Kind regards, Koen 2014-02-06 Itamar Heim < iheim(a)redhat.com > : On 02/06/2014 01:48 PM, Koen Vanoppen wrote: I would like to keep the vms... I know that there is a command in the CLI "update storageconnection", but how do I use this to change only the IP of the storage connection? Kind regards, Koen On Feb 6, 2014 12:55 PM, "Itamar Heim" < iheim(a)redhat.com <mailto: iheim(a)redhat.com >> wrote: On 02/06/2014 12:54 PM, Koen Vanoppen wrote: What if I remove the "old ip" storage domains and import the same iscsi luns with the new IP, would that work? removing a domain *deletes* all disks/vms, other than that... (we are working on ability to detach/attach domains post 3.4) Kind Regards 2014-02-06 Koen Vanoppen < vanoppen.koen(a)gmail.com <mailto: vanoppen.koen@gmail. com > <mailto: vanoppen.koen@gmail. __ com <mailto: vanoppen.koen@gmail. com >>>: Can I change the storagedomain ip from the ovirt-shell? Thanks in advance 2014-02-06 Itamar Heim < iheim(a)redhat.com <mailto: iheim(a)redhat.com > <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com >>>: On 02/06/2014 12:03 PM, Koen Vanoppen wrote: Can I change the storagedomain ip from the ovirt-shell? Thanks in advance please reply to list, thanks 2014-02-06 Itamar Heim < iheim(a)redhat.com <mailto: iheim(a)redhat.com > <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com >> <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com > <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com >>>>: On 02/06/2014 05:16 AM, Koen Vanoppen wrote: It's not on DNS... The storage server in ovirt is on IP... So... What are my options in this case? you would need to 'edit the connection'. since 3.3.1 this is possible via the rest api without hacking the db: http://www.ovirt.org/Features/ ______Manage_Storage_ Connections < http://www.ovirt.org/ Features/____Manage_Storage_ Connections > < http://www.ovirt.org/__ Features/__Manage_Storage___ Connections < http://www.ovirt.org/ Features/__Manage_Storage_ Connections >> < http://www.ovirt.org/____ Features/Manage_Storage_____ Connections < http://www.ovirt.org/__ Features/Manage_Storage___ Connections > < http://www.ovirt.org/__ Features/Manage_Storage___ Connections < http://www.ovirt.org/ Features/Manage_Storage_ Connections >>> Thanx! Kind regards, Koen On Feb 5, 2014 9:08 AM, "Itamar Heim" < iheim(a)redhat.com <mailto: iheim(a)redhat.com > <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com >> <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com > <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com >>> <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com > <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com >> <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com > <mailto: iheim(a)redhat.com <mailto: iheim(a)redhat.com >>>>> wrote: On 02/04/2014 03:10 PM, Elad Ben Aharon wrote: Actually, the best way to do it would be to create another storage domain and migrate all the VMs's disks to it (you can do it while the VMs are running), then you won't suffer from a down time. notice this will create a snapshot for your vms and may change them from raw to qcow. also, this not supported for shared disks. If you don't have the option to do so, the best way to do it would be to shut down the VMs, put the storage domain to 'Maintenance' and then perform the storage server network change. When the connection to the storage is fixed, activate the domain and resume the VMs manually. that's assuming the domain was added using dns and not ip address, and that the dns expiration/caching on all hosts will notice the new ip address. ----- Original Message ----- From: "Koen Vanoppen" < vanoppen.koen(a)gmail.com <mailto: vanoppen.koen@gmail. com > <mailto: vanoppen.koen@gmail. __ com <mailto: vanoppen.koen@gmail. com >> <mailto: vanoppen.koen@gmail . <mailto: vanoppen.koen@gmail .>_ ___com <mailto: vanoppen.koen@gmail. __ com <mailto: vanoppen.koen@gmail. com >>> <mailto: vanoppen.koen@gmail <mailto: vanoppen.koen@gmail >. <mailto: vanoppen.koen@gmail <mailto: vanoppen.koen@gmail >.> ______com <mailto: vanoppen.koen@gmail . <mailto: vanoppen.koen@gmail .>_ ___com <mailto: vanoppen.koen@gmail. __ com <mailto: vanoppen.koen@gmail. com >>>>> To: "Elad Ben Aharon" < ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com > <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com >> <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com > <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com >>> <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com > <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com >> <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com > <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com >>> >__>__, users(a)ovirt.org <mailto: users(a)ovirt.org > <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org >> <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org > <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org >>> <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org > <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org >> <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org > <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org >>>> Sent: Tuesday, February 4, 2014 2:57:57 PM Subject: Re: [Users] Storage server For the moment, nothing is going on. The change is planned on Thursday. So, correct me if I'm wrong, you say that the fastest and easiest way is to suspend all the machines, make the change of the storage server, rediscover the iscsi server and then bring the vm's back up? Kind regards, Koen On Feb 4, 2014 1:47 PM, "Elad Ben Aharon" < ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com > <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com >> <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com > <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com >>> <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com > <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com >> <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com > <mailto: ebenahar(a)redhat.com <mailto: ebenahar(a)redhat.com >>> >__> wrote: Hi, I suppose that those VMs are now in 'Paused' state, correct me if I'm wrong. After connectivity with storage comes back, all VMs which couldn't detect their disks should be resumed from 'Paused' to 'Up' state automatically. It shouldn't take them a long time to change their state (a few minutes). ----- Original Message ----- From: "Koen Vanoppen" < vanoppen.koen(a)gmail.com <mailto: vanoppen.koen@gmail. com > <mailto: vanoppen.koen@gmail. __ com <mailto: vanoppen.koen@gmail. com >> <mailto: vanoppen.koen@gmail . <mailto: vanoppen.koen@gmail .>_ ___com <mailto: vanoppen.koen@gmail. __ com <mailto: vanoppen.koen@gmail. com >>> <mailto: vanoppen.koen@gmail <mailto: vanoppen.koen@gmail >. <mailto: vanoppen.koen@gmail <mailto: vanoppen.koen@gmail >.> ______com <mailto: vanoppen.koen@gmail . <mailto: vanoppen.koen@gmail .>_ ___com <mailto: vanoppen.koen@gmail. __ com <mailto: vanoppen.koen@gmail. com >>>>> To: users(a)ovirt.org <mailto: users(a)ovirt.org > <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org >> <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org > <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org >>> <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org > <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org >> <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org > <mailto: users(a)ovirt.org <mailto: users(a)ovirt.org >>>> Sent: Tuesday, February 4, 2014 2:32:46 PM Subject: [Users] Storage server Dear All, At work, the network guys have come to a discovery that they have made a mistake in their network configuration... The Storage server that we use as ISCSI target in oVirt, is in the wrong VLAN, so the wrong IP address... What is the best way to make sure that all of our vms (40) that are using this scsi storage will come up again after the storage server has changed his ip? What are the best steps to be taken...? We are using oVirt Engine Version: 3.3.1-2.el6 Kind Regards, Koen ______________________________ _________________________ Users mailing list Users(a)ovirt.org <mailto: Users(a)ovirt.org > <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org >> <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org > <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org >>> <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org > <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org >> <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org > <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org >>>> http://lists.ovirt.org/_______ _mailman/listinfo/users < http://lists.ovirt.org/______ mailman/listinfo/users > < http://lists.ovirt.org/______ mailman/listinfo/users < http://lists.ovirt.org/____ mailman/listinfo/users >> < http://lists.ovirt.org/______ mailman/listinfo/users < http://lists.ovirt.org/____ mailman/listinfo/users > < http://lists.ovirt.org/____ mailman/listinfo/users < http://lists.ovirt.org/__ mailman/listinfo/users >>> < http://lists.ovirt.org/______ mailman/listinfo/users < http://lists.ovirt.org/____ mailman/listinfo/users > < http://lists.ovirt.org/____ mailman/listinfo/users < http://lists.ovirt.org/__ mailman/listinfo/users >> < http://lists.ovirt.org/____ mailman/listinfo/users < http://lists.ovirt.org/__ mailman/listinfo/users > < http://lists.ovirt.org/__ mailman/listinfo/users < http://lists.ovirt.org/ mailman/listinfo/users >>>> ______________________________ _________________________ Users mailing list Users(a)ovirt.org <mailto: Users(a)ovirt.org > <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org >> <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org > <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org >>> <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org > <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org >> <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org > <mailto: Users(a)ovirt.org <mailto: Users(a)ovirt.org >>>> http://lists.ovirt.org/_______ _mailman/listinfo/users < http://lists.ovirt.org/______ mailman/listinfo/users > < http://lists.ovirt.org/______ mailman/listinfo/users < http://lists.ovirt.org/____ mailman/listinfo/users >> < http://lists.ovirt.org/______ mailman/listinfo/users < http://lists.ovirt.org/____ mailman/listinfo/users > < http://lists.ovirt.org/____ mailman/listinfo/users < http://lists.ovirt.org/__ mailman/listinfo/users >>> < http://lists.ovirt.org/______ mailman/listinfo/users < http://lists.ovirt.org/____ mailman/listinfo/users > < http://lists.ovirt.org/____ mailman/listinfo/users < http://lists.ovirt.org/__ mailman/listinfo/users >> < http://lists.ovirt.org/____ mailman/listinfo/users < http://lists.ovirt.org/__ mailman/listinfo/users > < http://lists.ovirt.org/__ mailman/listinfo/users < http://lists.ovirt.org/ mailman/listinfo/users >>>> ______________________________ ___________________ Users mailing list Users(a)ovirt.org <mailto: Users(a)ovirt.org > http://lists.ovirt.org/__ mailman/listinfo/users < http://lists.ovirt.org/ mailman/listinfo/users > ______________________________ _________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/ mailman/listinfo/users juan replied to that _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users