[ovirt-users] Problem to add a node.

Jiri Belka jbelka at redhat.com
Fri Jul 10 07:31:00 UTC 2015


> Hello again, guys...
> 
> I am in trouble again:
> 
> When I try to add some my 3d node I have Install Failed.
> 
> Here the last log from engine.
> 
> 2015-07-01 11:11:20,759 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] FINISH,
> SetVdsStatusVDSCommand, log id: 27123183
> 2015-07-01 11:11:20,872 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Correlation ID: null, Call
> Stack: null, Custom Event ID: -1, Message: Host host-d.sisfron from cluster
> Sisfron was chosen as a proxy to execute Stop command on Host
> host-c.sisfron.
> 2015-07-01 11:11:20,873 INFO [org.ovirt.engine.core.bll.FenceExecutor]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Using Host host-d.sisfron
> from cluster Sisfron as proxy to execute Stop command on Host host-c.sisfron
> 2015-07-01 11:11:20,892 INFO
> [org.ovirt.engine.core.bll.VdsArchitectureHelper]
> (org.ovirt.thread.pool-8-thread-23) Failed to get architecture type from
> host information for host 'host-c.sisfron'. Using cluster 'Sisfron'
> architecture value instead.
> 2015-07-01 11:11:20,893 INFO [org.ovirt.engine.core.bll.FenceExecutor]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Executing <Stop> Power
> Management command, Proxy Host:host-d.sisfron, Agent:ipmilan, Target
> Host:host-c.sisfron, Management IP:192.168.131.33, User:root,
> Options:privlvl=OPERATOR,lanplus,delay=10, Fencing policy:{
> fencingEnabled=true, skipFencingIfSDActive=false,
> skipFencingIfConnectivityBroken=false,
> hostsWithBrokenConnectivityThreshold=50 }
> 2015-07-01 11:11:20,911 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] START,
> FenceVdsVDSCommand(HostName = host-d.sisfron, HostId =
> 72baa80b-8e83-46c8-9643-54632298b446, targetVdsId =
> 148a3ae2-8a1c-42b0-bf09-92156927ea40, action = Stop, ip = 192.168.131.33,
> port = , type = ipmilan, user = root, password = ******, options =
> 'privlvl=OPERATOR,lanplus,delay=10', policy = '{ fencingEnabled=true,
> skipFencingIfSDActive=false, skipFencingIfConnectivityBroken=false,
> hostsWithBrokenConnectivityThreshold=50 }'), log id: 3ad804ab
> 2015-07-01 11:12:10,998 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] FINISH, FenceVdsVDSCommand,
> return: Test Failed, [Powering off machine @ IPMI:192.168.131.33...Failed,
> ipmilan: Failed to connect after 20 seconds], log id: 3ad804ab
> 2015-07-01 11:12:10,998 WARN [org.ovirt.engine.core.bll.FenceExecutor]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Fencing operation failed with
> proxy host 72baa80b-8e83-46c8-9643-54632298b446, trying another proxy...
> 2015-07-01 11:12:11,094 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Correlation ID: null, Call
> Stack: null, Custom Event ID: -1, Message: Host host-e.sisfron from cluster
> Sisfron was chosen as a proxy to execute Stop command on Host
> host-c.sisfron.
> 2015-07-01 11:12:11,095 INFO [org.ovirt.engine.core.bll.FenceExecutor]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Using Host host-e.sisfron
> from cluster Sisfron as proxy to execute Stop command on Host host-c.sisfron
> 2015-07-01 11:12:11,096 INFO
> [org.ovirt.engine.core.bll.VdsArchitectureHelper]
> (org.ovirt.thread.pool-8-thread-23) Failed to get architecture type from
> host information for host 'host-c.sisfron'. Using cluster 'Sisfron'
> architecture value instead.
> 2015-07-01 11:12:11,097 INFO [org.ovirt.engine.core.bll.FenceExecutor]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Executing <Stop> Power
> Management command, Proxy Host:host-e.sisfron, Agent:ipmilan, Target
> Host:host-c.sisfron, Management IP:192.168.131.33, User:root,
> Options:privlvl=OPERATOR,lanplus,delay=10, Fencing policy:{
> fencingEnabled=true, skipFencingIfSDActive=false,
> skipFencingIfConnectivityBroken=false,
> hostsWithBrokenConnectivityThreshold=50 }
> 2015-07-01 11:12:11,117 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] START,
> FenceVdsVDSCommand(HostName = host-e.sisfron, HostId =
> 23729a9f-a687-42cf-b3e6-2504ea732d86, targetVdsId =
> 148a3ae2-8a1c-42b0-bf09-92156927ea40, action = Stop, ip = 192.168.131.33,
> port = , type = ipmilan, user = root, password = ******, options =
> 'privlvl=OPERATOR,lanplus,delay=10', policy = '{ fencingEnabled=true,
> skipFencingIfSDActive=false, skipFencingIfConnectivityBroken=false,
> hostsWithBrokenConnectivityThreshold=50 }'), log id: 6f8beb33
> 2015-07-01 11:13:01,204 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] FINISH, FenceVdsVDSCommand,
> return: Test Failed, [Powering off machine @ IPMI:192.168.131.33...Failed,
> ipmilan: Failed to connect after 20 seconds], log id: 6f8beb33
> 2015-07-01 11:13:01,204 ERROR [org.ovirt.engine.core.bll.StopVdsCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Failed to stop VDS using
> Primary Power Management agent
> 2015-07-01 11:13:01,227 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Correlation ID: null, Call
> Stack: null, Custom Event ID: -1, Message: Host host-c.sisfron became non
> responsive. It has no power management configured. Please check the host
> status, manually reboot it, and click "Confirm Host Has Been Rebooted"
> 2015-07-01 11:13:01,247 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] START,
> SetVdsStatusVDSCommand(HostName = host-c.sisfron, HostId =
> 148a3ae2-8a1c-42b0-bf09-92156927ea40, status=NonResponsive,
> nonOperationalReason=NONE, stopSpmFailureLogged=false), log id: 1a96fb96
> 2015-07-01 11:13:01,249 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] FINISH,
> SetVdsStatusVDSCommand, log id: 1a96fb96
> 2015-07-01 11:13:01,273 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Correlation ID: null, Call
> Stack: null, Custom Event ID: -1, Message: Failed to power fence host
> host-c.sisfron. Please check the host status and it's power management
> settings, and then manually reboot it and click "Confirm Host Has Been
> Rebooted"
> 2015-07-01 11:13:01,274 ERROR [org.ovirt.engine.core.bll.StopVdsCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Command
> org.ovirt.engine.core.bll.StopVdsCommand throw Vdc Bll exception. With error
> message VdcBLLException: VDS_FENCE_OPERATION_FAILED (Failed with error
> VDS_FENCE_OPERATION_FAILED and code 5021)
> 2015-07-01 11:13:01,277 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Correlation ID: 4906a083, Job
> ID: 91c0393b-61fb-4559-8df7-082834a72cff, Call Stack: null, Custom Event ID:
> -1, Message: Failed to stop Host host-c.sisfron, (User: null at N/A).
> 2015-07-01 11:13:01,287 WARN
> [org.ovirt.engine.core.bll.VdsNotRespondingTreatmentCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Restart host action failed,
> updating host 148a3ae2-8a1c-42b0-bf09-92156927ea40 to NonResponsive
> 2015-07-01 11:13:01,306 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] START,
> SetVdsStatusVDSCommand(HostName = host-c.sisfron, HostId =
> 148a3ae2-8a1c-42b0-bf09-92156927ea40, status=NonResponsive,
> nonOperationalReason=NONE, stopSpmFailureLogged=false), log id: 7d593ef3
> 2015-07-01 11:13:01,308 INFO
> [org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] FINISH,
> SetVdsStatusVDSCommand, log id: 7d593ef3
> 2015-07-01 11:13:01,310 INFO
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Correlation ID: 160b5809, Job
> ID: 47210bb5-7772-4202-937b-81d1857f0709, Call Stack: null, Custom Event ID:
> -1, Message: Host host-c.sisfron is rebooting.
> 2015-07-01 11:13:01,313 INFO
> [org.ovirt.engine.core.bll.VdsNotRespondingTreatmentCommand]
> (org.ovirt.thread.pool-8-thread-23) [4906a083] Lock freed to object
> EngineLock [exclusiveLocks= key: 148a3ae2-8a1c-42b0-bf09-92156927ea40 value:
> VDS_FENCE
> , sharedLocks= ]
> 2015-07-01 11:13:03,462 INFO
> [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp Reactor)
> Connecting to / 192.168.131.23
> 2015-07-01 11:13:03,476 ERROR
> [org.ovirt.vdsm.jsonrpc.client.reactors.Reactor] (SSL Stomp Reactor) Unable
> to process messages
> 2015-07-01 11:13:18,755 INFO
> [org.ovirt.engine.core.bll.storage.FenceVdsManualyCommand]
> (ajp--127.0.0.1-8702-9) [3835b1fb] Lock Acquired to object EngineLock
> [exclusiveLocks= key: 148a3ae2-8a1c-42b0-bf09-92156927ea40 value: VDS_FENCE
> , sharedLocks= ]
> 2015-07-01 11:13:18,756 INFO
> [org.ovirt.engine.core.bll.storage.FenceVdsManualyCommand]
> (org.ovirt.thread.pool-8-thread-18) [3835b1fb] Running command:
> FenceVdsManualyCommand internal: false. Entities affected : ID:
> 148a3ae2-8a1c-42b0-bf09-92156927ea40 Type: VDSAction group MANIPULATE_HOST
> with role type ADMIN
> 2015-07-01 11:13:18,816 INFO
> [org.ovirt.engine.core.bll.ClearNonResponsiveVdsVmsCommand]
> (org.ovirt.thread.pool-8-thread-18) [5e48b81d] Running command:
> ClearNonResponsiveVdsVmsCommand internal: true. Entities affected : ID:
> 148a3ae2-8a1c-42b0-bf09-92156927ea40 Type: VDS
> 2015-07-01 11:13:18,875 INFO
> [org.ovirt.engine.core.vdsbroker.UpdateVdsVMsClearedVDSCommand]
> (org.ovirt.thread.pool-8-thread-18) [5e48b81d] START,
> UpdateVdsVMsClearedVDSCommand(HostName = host-c.sisfron, HostId =
> 148a3ae2-8a1c-42b0-bf09-92156927ea40), log id: 4dd83ef1
> [root at hypervisor ovirt-engine]#

There should be host-deploy log on engine host for each host installation.
Check it.

j.



More information about the Users mailing list