Search Engine: Elastic

Article ID: 129400, created on Sep 12, 2016, last review on Apr 7, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0
  • Operations Automation 5.5

Symptoms

VE performance tab is not updated after VE migration from one hardware node to another, in case the target node was the owner of this VE in the past already.

The following errors appear in /var/log/pa/vps.snmp.log on OACI IM server:

2017-03-21 23:57:17,807 () DEBUG SnmpManager [VF executor thread #176 @COMMON] - VE statistics update for VE [test-migration] has been ignored: 8598962888457597295 <= 8944612235448396073
2017-03-21 23:57:17,807 () WARN  SnmpManager [VF executor thread #222 @COMMON] - Node uuid discrepancy found for [test-migration]: 10003 != 10007
2017-03-21 23:57:17,807 () TRACE SnmpManager [VF executor thread #222 @COMMON] - VE state update for VE [test-migration] ignored: currentState.isBusy() == false; state: STARTED vs STARTED; node: [10003] vs [10003]

No service restart helps to bring resource usage statistics back.

Other VEs on the same nodes are not affected.

Cause

In case the target node already contained records of the VE in the past, the statistics fail to get updated. The issue is acknowledged as CCU-14758.

Resolution

Contact Odin Technical Support to apply a workaround for the problem.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF