NMShell Pod Status Seems Incorrect
(Doc ID 2921896.1)
Last updated on APRIL 13, 2023
Applies to:
Oracle Communications Offline Mediation Controller - Version 12.0.0.5.0 and laterInformation in this document applies to any platform.
Goal
Scenario:
- During deployment, user has observed one issue in NMShell pob wherein, if there is any error while executing the NMShell commands, the NMShell pob does not fall into Error state.
- It goes into Completed state even if there is any error and gets terminated automatically and so it moves to the next stage.
- So the user is not able to check if there was any error in NMShell pob through Jenkins because of this issue.
Question:
What is the reason for above behavior? And is there any possible way to make the pod itself in error state?
Solution
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
Goal |
Solution |
References |