Resolved issues in on-premises containers

Review the defects and fixes that are resolved in the release.

November 2025 (10.0.2509.1)

Case number	Description
TS020684836	After upgrading to the October release, UtilityServiceGroup reconciliation failed due to a YAML parsing error. This issue is now resolved.

August 2025 (10.0.2506.2)

Case number	Description
TS020065289	The Sterling Intelligent Promising Operator incorrectly processes the `serverProperties` that are configured in the SIPEnvironment custom resource. This issue is resolved.

February 2025 (10.0.2409.2)

Case number	Description
TS018500115	The Sterling Intelligent Promising truststore job deployment fails due to missing necessary environment variable names and restart policy in the container specifications. This issue is resolved.

October 2024 (10.0.2409.1)

Case number Description

TS017442586

Case number	Description
TS017442586	The Audit Supplies API does not filter output based on custom attribute. This issue is resolved. To implement the fix, manually call a rollover by calling the following API. `POST audits/_rollover` This allows the index rollover process to create a new index with the updated mappings. As a result, new data aligns with the updated mappings, while existing data maintains its original structure and cannot be filtered with the updated mapping changes.

The Audit Supplies API does not filter output based on custom attribute.

This issue is resolved. To implement the fix, manually call a rollover by calling the following API.

POST audits/_rollover

This allows the index rollover process to create a new index with the updated mappings. As a result, new data aligns with the updated mappings, while existing data maintains its original structure and cannot be filtered with the updated mapping changes.

July 2024 (10.0.2406.1)

Case number	Description
TS016538654	The Xmx parameter in the JVM arguments is duplicated. This issue is now resolved.

June 2024 (10.0.2406.0)

Case number	Description
TS016408842	In SIPEnvironment custom resource, you can now define CPU and memory resources that are required for the `omsGateway`. For more information, see omsGateway parameter.
TS016300541	In Order Hub, the encoding API fails on the carrier configuration and tenant settings screens. This issue is resolved.
TS016262992	The `supplySnapshot` event is now available for containers and its details are available in the API documentation.

May 2024 (10.0.2403.2)

Case number	Description
TS016037659	The Order Hub screens can now call the v2 availability API in inventory search screens.

April 2024 (10.0.2403.1)

Case number	Description
TS015771858	The behavior of `createReservation` changes when the updated IBM® Sterling Intelligent Promising container is deployed. This issue is resolved, and the `createReservation` now functions as expected.
TS015754384	The capability to add the desired cipher through the Sterling Intelligent Promising Operator custom resource was previously not available. This issue is resolved.

January 2024 (10.0.2309.2)

Case number	Description
TS015174724	You can now call the custom attributes API in the IBM Sterling Intelligent Promising containers environment.
TS014880937	When reservation is created with a future date on `requestedReservationTs`, where availability is zero, the reservation is successful. This issue is resolved.
TS014512626	The Get Supply Sync Record and Get Supply Sync Transaction APIs return different statuses and the status for batch supply sync does not move to completed status. This issue is resolved.