My Oracle Support Banner

Fail to join OVS into an existing pool if the any cluster value is customized other than default (Doc ID 2286986.1)

Last updated on FEBRUARY 02, 2019

Applies to:

Oracle VM - Version 3.4.2 to 3.4.3 [Release OVM34]
Oracle Cloud Infrastructure - Version N/A and later
Linux x86-64

Symptoms

When try to join a fresh installed OVS into an existing pool, below error found in OVMM Web GUI failed Job details:


 

Changes

With first sample "... uses a heartbeat timeout of 300000 ms, but we use 120000 ms locally", before joining OVS ovs3.oracle.com into this existing pool, the O2CB_HEARTBEAT_THRESHOLD value of this cluster is customized to 151 from default value 61. 

With second sample "... uses a network idle timeout of 60000 ms, but we use 90000 ms locally", it has customized O2CB_IDLE_TIMEOUT_MS value in pool.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.