Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Workspace WebSphere Liberty
Created by Guest
Created on Sep 3, 2024

Better error reporting for Liberty InstantOn

I have been working with WebSphere Liberty InstantOn in OpenShift on the X86 and Power-10 platforms. One of the most challenging aspects revolves around the error reporting of both OpenShift errors and more specifically the CRIU errors. It has been difficult getting the OpenShift SCC and SA details in alignment (as simple as it is) with the error message being a little unclear as to exactly what the error is and how to resolve. The CRIU errors have been even more difficult to resolve - the error messages are too technical and without access to the source code or a detailed understanding of CRIU, near on impossible to resolve.

This would benefit anyone trying to successfully implement WebSphere Liberty InstantOn.

I feel without clear error reporting with appropriate solutions with the error will make it very difficult to implement this great technology. Ideally the error message itself should be improved, plus possible solutions to the problem should be logged with the error itself. A further reference to a URL for more details could be handy.

Idea priority High