You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WLSKO-0175=Job {0} in namespace {1} failed with status {2}. Check log messages \
111
-
copied from the introspector pod {3} log for additional information.
106
+
copied from the introspector Pod {3} log for additional information.
112
107
WLSKO-0176=Job {1} in namespace {0} failed, job details are {2}
113
-
WLSKO-0177=Pod {0} in namespace {1} failed, the pod status is {2}
108
+
WLSKO-0177=Pod {0} in namespace {1} failed, the Pod status is {2}
114
109
WLSKO-0178=Operator cannot proceed, as the Custom Resource Definition for ''domains.weblogic.oracle'' or ''clusters.weblogic.oracle'' is not installed.
115
110
WLSKO-0179=Pod {0} in namespace {1} detected as stuck, and force-deleted
116
111
WLSKO-0180=Creating event: {0}
@@ -122,19 +117,16 @@ WLSKO-0185=Patching Pod Disruption Budget for WebLogic domain with UID: {0}. Clu
122
117
WLSKO-0186=Start managing namespace {0}
123
118
WLSKO-0187=Stop managing namespace {0}
124
119
WLSKO-0189=HTTP request method {0} to {1} failed with exception {2}.
125
-
WLSKO-0190=Rolling restart of WebLogic domain server pods started.
126
-
WLSKO-0192=Executing make right domain operation, recheck count for server {0} is {1}.
127
-
WLSKO-0193=Waiting for server {0} to start, recheck count is {1}.
120
+
WLSKO-0190=Rolling restart of WebLogic domain server Pods started.
128
121
WLSKO-0194=Internal identity initialization step failed with exception {0}.
129
122
WLSKO-0195=The operator failed after retrying for {0,number,#} minutes. \
130
123
This time limit may be specified in spec.failureRetryLimitMinutes. \
131
124
Please resolve the error and then update 'domain.spec.introspectVersion' to force another retry.
132
-
WLSKO-0198={0} Fiber {1}
133
-
WLSKO-0199=WL pod shutdown: Initiating shutdown of WebLogic server {0} via REST interface.
134
-
WLSKO-0200=WL pod shutdown: Successfully shutdown WebLogic server {0} via REST interface.
135
-
WLSKO-0201=WL pod shutdown: Failed to shut down WebLogic server {0} via REST interface with response: {1}.
136
-
WLSKO-0203=WL pod shutdown: Failed to shut down WebLogic server {0} via REST interface due to exception: {1}.
137
-
WLSKO-0204=WL pod shutdown: Retry shutdown of WebLogic server {0} via REST interface.
125
+
WLSKO-0199=WLS Pod shutdown: Initiating shutdown of WebLogic server {0} via REST interface.
126
+
WLSKO-0200=WLS Pod shutdown: Successfully shutdown WebLogic server {0} via REST interface.
127
+
WLSKO-0201=WLS Pod shutdown: Failed to shut down WebLogic server {0} via REST interface with response: {1}.
128
+
WLSKO-0203=WLS Pod shutdown: Failed to shut down WebLogic server {0} via REST interface due to exception: {1}.
129
+
WLSKO-0204=WLS Pod shutdown: Retry shutdown of WebLogic server {0} via REST interface.
138
130
WLSKO-0213=InputFile: {0} does not exist or could not be read.
139
131
WLSKO-0214=The output dir {0} specified by ''-d'' does not exist or could not be read.
140
132
WLSKO-0215=The output file {0} already exists, remove it and try again. \
@@ -146,12 +138,12 @@ WLSKO-0218=Domain custom resource converter: Name of the converted file. If not
146
138
file name by appending "__converted." and the input file extension to the base name of the input file name.
147
139
WLSKO-0219=Enable overwriting the existing output file, if any.
but there are pending non-dynamic changes that require \
197
-
pod restarts to take effect. The changes are:
188
+
Pod restarts to take effect. The changes are:
198
189
WLSDO-0021=DomainUID ''{0}'' server ''{1}'' does not have a port available for the operator to send REST calls. \
199
190
The default listen port and SSL port are disabled, the admin port is not configured and there is no channel with admin privileges.
200
191
WLSDO-0027=The Monitoring Exporter port {0,number,#} specified by ''spec.monitoringExporter.port'' conflicts with a port in WebLogic Server instance ''{1}''.
@@ -205,25 +196,25 @@ WLSDO-0031=Container port name ''{2}'' for domain with domainUID ''{0}'' and con
205
196
WLSDO-0032=Network channel name ''{2}'' for domain with domainUID ''{0}'' and server with \
206
197
name ''{1}'' exceeds maximum allowed length ''{3}''. Please specify a shorter channel name.
207
198
WLSDO-0033=Failure invoking ''{0}'' on {1} {2} in namespace {3}: {4}
208
-
WLSDO-0034=Failure on pod ''{0}'' in namespace ''{1}'': {2}
199
+
WLSDO-0034=Failure on Pod ''{0}'' in namespace ''{1}'': {2}
209
200
WLSDO-0035={0} replicas specified for cluster ''{1}'' which has a maximum cluster size of {2}
210
201
WLSDO-0036=The domain is configured with one or more auxiliary images and the mountPath ''{0}'' for auxiliary image is \
211
202
already in use.
212
203
WLSDO-0037=More than one auxiliary image under ''spec.configuration.model.auxiliaryImages'' sets a ''sourceWDTInstallHome'' value. \
213
204
The 'sourceWDTInstallHome' value must be set for only one auxiliary image.
214
205
WLSDO-0038=The wdtInstallHome ''{0}'' is invalid. The wdtInstallHome must be outside the directory for the modelHome ''{1}''
215
206
WLSDO-0039=The modelHome ''{1}'' is invalid. The modelHome must be outside the directory for the wdtInstallHome ''{0}''
216
-
WLSDO-0040=One or more server pods that are supposed to be available failed. Check the server status in the domain status, \
217
-
the server pod status and logs, and WebLogic Server logs for possible reasons."
218
-
WLSDO-0041=One or more server pods that are supposed to be available are not ready within the period of time \
207
+
WLSDO-0040=One or more server Pods that are supposed to be available failed. Check the server status in the domain status, \
208
+
the server Pod status and logs, and WebLogic Server logs for possible reasons."
209
+
WLSDO-0041=One or more server Pods that are supposed to be available are not ready within the period of time \
219
210
defined in 'serverPod.maxReadyWaitTimeSeconds' under "domain.spec', 'domain.adminServer', 'managedServer', or 'domain.cluster'. \
220
-
Check the server status in the domain status, the server pod status and logs, and WebLogic Server logs for possible reasons. \
211
+
Check the server status in the domain status, the server Pod status and logs, and WebLogic Server logs for possible reasons. \
221
212
Adjust the value of 'serverPod.maxReadyWaitTimeSeconds' setting if needed."
222
213
WLSDO-0042=Pod was evicted
223
214
WLSDO-0043=Pod spec has changed
224
-
WLSDO-0044=One or more server pods that are supposed to be available did not start within the period of time \
215
+
WLSDO-0044=One or more server Pods that are supposed to be available did not start within the period of time \
225
216
defined in 'serverPod.maxPendingWaitTimeSeconds' under "domain.spec', 'domain.adminServer', 'managedServer', or 'domain.cluster'. \
226
-
Check the server status in the domain status, the server pod status and logs, and WebLogic Server logs for possible reasons. \
217
+
Check the server status in the domain status, the server Pod status and logs, and WebLogic Server logs for possible reasons. \
227
218
One common cause of this issue is a problem pulling the WebLogicServer image. \
228
219
Adjust the value of 'serverPod.maxPendingWaitTimeSeconds' setting if needed."
229
220
WLSDO-0045=Cannot reference cluster resource ''{0}'' because it is used by ''{1}''
@@ -263,7 +254,7 @@ WLSDO-0064=When ''spec.configuration.initializeDomainOnPV'' is specified to auto
263
254
WLSDO-0065=The OPSS wallet password secret ''{0}'' is specified but the required ''walletPassword'' key is missing \
264
255
in the specified secret ''{1}''.
265
256
WLSDO-0066=Pod ''{0}'' is Unschedulable, reason: ''{1}''
266
-
WLSDO-0067=One or more pods in the domain cannot be scheduled. Please check individual pod status for details.
257
+
WLSDO-0067=One or more Pods in the domain cannot be scheduled. Please check individual Pod status for details.
267
258
268
259
oneEnvVar=variable
269
260
multipleEnvVars=variables
@@ -287,19 +278,19 @@ WLSEO-0008=Domain {0} is incomplete for one or more of the following reasons: th
287
278
there are pending server shutdowns, or not all servers expected to be running are ready \
288
279
and at their target image, auxiliary images, restart version, and introspect version.
289
280
WLSEO-0009=Domain {0} encountered some failures before, and those failures have been resolved.
290
-
WLSEO-0010=Replacing pod {0} because: {1}.
281
+
WLSEO-0010=Replacing Pod {0} because: {1}.
291
282
WLSEO-0011=Start managing namespace {0}.
292
283
WLSEO-0012=Stop managing namespace {0}.
293
284
WLSEO-0013=Started watching namespace {0}.
294
285
WLSEO-0014=Stopped watching namespace {0}.
295
286
WLSEO-0015=Start managing namespace {0} failed due to an authorization error.
296
-
WLSEO-0016=Rolling restart WebLogic server pods in domain {0} because: {1}.
287
+
WLSEO-0016=Rolling restart WebLogic server Pods in domain {0} because: {1}.
297
288
WLSEO-0017=Rolling restart of domain {0} completed.
298
289
WLSEO-0018=Domain validation error
299
290
WLSEO-0019=Domain resource and WebLogic domain configuration mismatch error
300
291
WLSEO-0020=Introspection error
301
292
WLSEO-0021=Kubernetes Api call error
302
-
WLSEO-0022=Server pod error
293
+
WLSEO-0022=Server Pod error
303
294
WLSEO-0023=Replicas too high
304
295
WLSEO-0024=Internal error
305
296
WLSEO-0025=Domain processing is aborted
@@ -314,7 +305,7 @@ WLSEO-0031=Cluster resource {0} was created.
314
305
WLSEO-0032=Cluster resource {0} was deleted.
315
306
WLSEO-0033=Cluster resource {0} was changed.
316
307
WLSEO-0034=Cluster {0} is available: a sufficient number of its servers have reached the ready state.
317
-
WLSEO-0035=Cluster {0} is complete because all of the following are true: there is no failure detected, \
308
+
WLSEO-0035=Cluster {0} is complete because all the following are true: there is no failure detected, \
318
309
there are no pending server shutdowns, and all servers expected to be running are ready \
319
310
and at their target image, auxiliary images, restart version, and introspect version.
320
311
WLSEO-0036=Cluster {0} is unavailable: an insufficient number of its servers that are expected to be running are ready.";
0 commit comments