My Oracle Support Banner

OSM CN :Timeout After Waiting More Than 4400 Seconds (Doc ID 3045099.1)

Last updated on SEPTEMBER 09, 2024

Applies to:

Oracle Communications Order and Service Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 7.5.0.0.0 version, Cloud Native Toolkit

 Timeout after waiting more than 4400 seconds in OSM CN Env

The Customer is getting below error after running upgrade-instance script .


ERROR
-----------------------

@@ [2024-08-14T04:47:30][seconds=0] Info: Waiting up to 4400 seconds for exactly '2' WebLogic Server pods to reach the following criteria:
@@ [2024-08-14T04:47:30][seconds=0] Info: ready='true'
@@ [2024-08-14T04:47:30][seconds=0] Info: image='localhost/osm-cn-base:7.5.0'
@@ [2024-08-14T04:47:30][seconds=0] Info: domainRestartVersion='v1-v1-v1-1722987063'
@@ [2024-08-14T04:47:30][seconds=0] Info: introspectVersion='v1-v1-v1-1723610836'
@@ [2024-08-14T04:47:30][seconds=0] Info: namespace='project'
@@ [2024-08-14T04:47:30][seconds=0] Info: domainUID='project-sit2'
@@ [2024-08-14T04:47:30][seconds=0] Info: Current pods that match the above criteria = 0

@@ [2024-08-14T06:00:50][seconds=4400] Error: Timeout after waiting more than 4400 seconds.

 

We are seeing same issue in their managed server logs while the managed server is coming up using create-instance.sh

<Emergency> <oracle.dfw.incident> <BEA-000000> <incident 1 created with problem key "DFW-99998 [java.lang.ClassNotFoundException][oracle.communications.ordermanagement.automation.plugin.AutomationPluginManager.isAutomationPluginScriptAccessible][oms]">  

Changes

 

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.