Search Engine: Elastic

Article ID: 131647, created on Oct 20, 2017, last review on Oct 20, 2017

  • Applies to:
  • Operations Automation 7.1

Symptoms

Recreation process of VE was hanging for several hours and then ended with failure. The following entries could be found in vps.vm2vf.log:

# Start of the request:
16:01:46,325 () INFO  Vm2VfApiOperationsProvider [ActiveMQ Session Task-4598] - ...// create_ve_cb::sync_request to following node: 192.168.10.67
"reqUuid" : "web_5d9adc09-7ef6-4e6a-817e-277de43b36b8_107779",

After 20 minutes request has failed with timeout:

16:21:46,333 (web_5d9adc09-7ef6-4e6a-817e-277de43b36b8_107779 create_ve_cb callback) INFO  LogCallbackWithCapacityAndId [Thread-750232] - INF pthread_cond_timedwait [110]: cbp 0x7f2a44009690 job 0xac5d6 [__PrlSrv_GetVmConfig] index [14438]
16:21:46,333 (web_5d9adc09-7ef6-4e6a-817e-277de43b36b8_107779 create_ve_cb callback) INFO  LogCallbackWithCapacityAndId [Thread-750233] - INF PrlJob_GetStatus : job 0xac5d6 PJS_FINISHED
16:21:46,334 (web_5d9adc09-7ef6-4e6a-817e-277de43b36b8_107779 create_ve_cb callback) INFO  LogCallbackWithCapacityAndId [Thread-750234] - INF job [0xac5d6] finished already

But IM did not receive this reply and waited for several hours for operation timeout.

Cause

The operation got stuck in internal call to the Virtuozzo SDK interface, which led to incorrect result of the operation. The behavior is planned to be improved in CCU-16874.

Resolution

It is required to restart PACI-vm2vf service in order to flush all stuck events:

# service PACI-vm2vf restart

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 8c199f0ee4305da1a577740620df4a51 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF