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
Copy file name to clipboardExpand all lines: documentation/staging/content/userguide/managing-domains/domain-events.md
+109-1Lines changed: 109 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,22 @@ The operator generates these event types in a domain namespace, which indicate t
27
27
*`DomainDeleted`: An existing domain has been deleted.
28
28
*`DomainProcessingStarting`: The operator has started to process a new domain or to update an existing domain. This event may be a result of a `DomainCreate`, `DomainChanged`, or `DomainDeleted` event, or a result of a retry after a failed attempt.
29
29
*`DomainProcessingFailed`: The operator has encountered a problem while it was processing the domain resource. The failure either could be a configuration error or a Kubernetes API error.
30
-
*`DomainProcessingRetrying`: The operator is going to retry the processing of a domain after it encountered an failure.
30
+
*`DomainProcessingRetrying`: The operator is going to retry the processing of a domain after it encountered a failure.
31
31
*`DomainProcessingCompleted`: The operator successfully completed the processing of a domain resource.
32
32
*`DomainProcessingAborted`: The operator stopped processing a domain when the operator encountered a fatal error or a failure that persisted after the specified maximum number of retries.
33
+
*`DomainRollStarting`: The operator has detected domain resource or Model in Image model
34
+
updates that require it to perform a rolling restart of the domain.
35
+
If the domain roll is due to a change to domain resource fields
`domainHome`, `includeServerOutInPodLog`, or `logHome`, then
38
+
the event message reports the field name plus its old and new values.
39
+
If the domain roll is due to other domain resource changes that cause servers to be restarted
40
+
(see [full list of fields that cause servers to be restarted]({{< relref "/userguide/managing-domains/domain-lifecycle/startup#fields-that-cause-servers-to-be-restarted" >}})),
41
+
then the event message simply reports that the domain resource has changed.
42
+
If the domain roll is due to a Model in Image model update,
43
+
then the event message reports there has been a change in the WebLogic domain configuration without the details.
44
+
*`DomainRollCompleted`: The operator has successfully completed a rolling restart of a domain.
45
+
*`PodCycleStarting`: The operator has started to replace a server pod after it detects that the current pod does not conform to the current domain resource or WebLogic domain configuration.
33
46
*`DomainValidationError`: A validation error or warning is found in a domain resource. Please refer to the event message for details.
34
47
*`NamespaceWatchingStarted`: The operator has started watching for domains in a namespace.
35
48
*`NamespaceWatchingStopped`: The operator has stopped watching for domains in a namespace. Note that the creation of this event in a domain namespace is the operator's best effort only; the event will not be generated if the required Kubernetes privilege is removed when a namespace is no longer managed by the operator.
@@ -285,3 +298,98 @@ Source:
285
298
Type: Normal
286
299
Events: <none>
287
300
```
301
+
302
+
Example of the sequence of operator generated events in a domain rolling restart after the domain resource's `image` and `logHomeEnabled` changed, which is the output of the command `kubectl get events -n sample-domain1-ns --selector=weblogic.domainUID=sample-domain1,weblogic.createdByOperator=true --sort-by=lastTimestamp'.
303
+
304
+
```
305
+
LAST SEEN TYPE REASON OBJECT MESSAGE
306
+
2m58s Normal DomainChanged domain/sample-domain1 Domain resource sample-domain1 was changed
307
+
2m58s Normal DomainProcessingStarting domain/sample-domain1 Creating or updating Kubernetes presence for WebLogic Domain with UID sample-domain1
308
+
2m58s Normal DomainRollStarting domain/sample-domain1 Rolling restart WebLogic server pods in domain sample-domain1 because: 'image' changed from 'oracle/weblogic' to 'oracle/weblogic:14.1.1.0',
309
+
'logHome' changed from 'null' to '/shared/logs/sample-domain1'
310
+
2m58s Normal PodCycleStarting domain/sample-domain1 Replacing pod sample-domain1-adminserver because: In container 'weblogic-server':
311
+
'image' changed from 'oracle/weblogic' to 'oracle/weblogic:14.1.1.0',
312
+
env 'LOG_HOME' changed from 'null' to '/shared/logs/sample-domain1'
313
+
2m7s Normal PodCycleStarting domain/sample-domain1 Replacing pod sample-domain1-managed-server1 because: In container 'weblogic-server':
314
+
'image' changed from 'oracle/weblogic' to 'oracle/weblogic:14.1.1.0',
315
+
env 'LOG_HOME' changed from 'null' to '/shared/logs/sample-domain1'
316
+
71s Normal PodCycleStarting domain/sample-domain1 Replacing pod sample-domain1-managed-server2 because: In container 'weblogic-server':
317
+
'image' changed from 'oracle/weblogic' to 'oracle/weblogic:14.1.1.0',
318
+
env 'LOG_HOME' changed from 'null' to '/shared/logs/sample-domain1'
319
+
19s Normal DomainRollCompleted domain/sample-domain1 Rolling restart of domain sample-domain1 completed
320
+
19s Normal DomainProcessingCompleted domain/sample-domain1 Successfully completed processing domain resource sample-domain1
0 commit comments