Brmdomain-admin-server Not Being Redployed by Weblogic Operator
(Doc ID 2880768.1)
Last updated on OCTOBER 12, 2023
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version,
One user is running Billing and Revenue Management (BRM) 184.108.40.206.0 in a cloud solution using Kubernetes where the Web Services Manager(WSM) pod "brmdomain-admin-server" was not running.
This seems to happen once in a while and the workaround is to delete the weblogic-operator pod. When the pod is recreated, it realizes the brmdomain pod again. But in one instance, this workaround does not help, the user managed to get it running again by uninstalling and reinstalling the weblogic-operator.
From the log, there were two secrets that could not be found:
But these two secrets do exist in the environment. How to resolve this issue?
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