Search Engine: Elastic

Article ID: 131327, created on Aug 18, 2017, last review on Aug 18, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1


Upon creating an OACI VE, it ends up in Failed to delete state.

Starting/stopping a VE results in a failure.

/var/log/pa/vps.log on the OACI IM node contains the messages:

2017-08-18 15:01:12,837 (aps_2d4a4257-f53f-4a16-a6bc-ff209670274a_102) WARN  Heartbeat [Shared executor thread #2 @1 @INTERACTIVE] - invoke stop_ve_cb to route state: OPEN value: -93 ms


2017-08-18 15:01:12,851 () ERROR VeOperationTask [Shared executor thread #2 @1 @INTERACTIVE] - VE operation failed
java.lang.reflect.UndeclaredThrowableException: null
        at com.sun.proxy.$Proxy96.stop_ve_cb(Unknown Source) ~[na:na]
        at com.parallels.c2u.vm2vf.VF.stopVe( ~[im.jar:na]
        at ~[im.jar:na]
Caused by: com.parallels.c2u.vm2vf.rpc.OpenCircuitException: null
        at com.parallels.c2u.vm2vf.rpc.CircuitBreaker$DefaultExceptionSupplier.get( ~[im.jar:na]
        at com.parallels.c2u.vm2vf.rpc.CircuitBreaker$DefaultExceptionSupplier.get( ~[im.jar:na]
        at com.parallels.c2u.vm2vf.rpc.HeartbeatAcceptorCircuitBreaker.invoke( ~[im.jar:na]
        at com.parallels.c2u.vm2vf.rpc.DefaultCircuitBreakerSelector.invoke( ~[im.jar:na]


There is a time drift between OACI nodes, which causes negative values in the vm2vf service heartbeat calculation.


Configure NTP or any other time synchronization in the OACI environment to make sure there is no big difference in time between the nodes.

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF