Event Endpoint Management continues to be enhanced

Event Endpoint Management continues to be available and enhanced as part of IBM's integration platforms.

End of Marketing announcement for IBM Event Automation

Event Streams and Event Processing are deprecated and no enhancements will be provided. Support and security fixes will be provided in line with published support lifecycle policies. Future event-driven solutions that make use of Apache Kafka and Flink will be delivered by IBM Confluent Platform.

For more information, see the support lifecycle transition and software ordering completion announcement.

Attention: This version of Event Streams has reached End of Support. For more information about supported versions, see the support matrix.

Event Streams installation reports failed status

Symptoms

When installing a new instance of Event Streams on an OpenShift Container Platform cluster that has not previously had an installation of IBM Cloud Pak foundational services, the status of the Event Streams instance is reported as Failed.

The following condition message is displayed in the status of the instance:

An unexpected exception was encountered: Common Services must be Ready.

Causes

If not present at the time of installing an instance of Event Streams, the operator installs IBM Cloud Pak foundational services first. The Event Streams operator waits for the foundational services installation to complete before continuing.

The installation of foundational services can take several minutes, but in some cases the Event Streams operator does not wait long enough for the process to complete, and incorrectly reports that the installation failed when it is still in progress.

Resolving the problem

No user action is required.

When the IBM Cloud Pak foundational services installation completes, the Event Streams operator automatically resumes the installation of the Event Streams instance. The status of the instance changes to Ready when the process is complete.

Note: This only applies to new installations on clusters where IBM Cloud Pak foundational services has not previously been installed.