Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace PowerVC
Created by Guest
Created on Nov 5, 2015

PowerVC verbose EGO mesages during startup

PowerVC startup generates a number of errors related to EGO as required services are not yet started
nova-ibm-ego-ha-service: 2015-10-23 13:55:
58.612 1406 ERROR [-] Platform
Resource Scheduler could not connect to EGO due to (EGO error code: 25,
EGO error message: The cluster is not responding). Start up EGO if EGO
is not running, otherwise wait one or two minutes to allow EGO to start

Ideally PowerVC would not report these errors during startup when EGO will ALWAYS need to wait OR design a pause into EGO startup to allow required services to start

Idea priority Low
  • Guest
    Jan 25, 2017

    Thanks. The PowerVC services are designed to work in a distributed fashion. In this case, EGO is another service outside of the standard OpenStack services and we don't want to hold up the system on EGO initializing. And we don't want to suppress the messages for the case where perhaps EGO really is down. I understand the concern, but on the flip side, you can see that the connection was initialized shortly thereafter and I think this will help isolate *real* problems. Ultimately this is a concern just at application restart time and doesn't have any actual ill side effects and can be quickly eliminated as cause for concern when you see that the connection is established. Thanks!

  • Guest
    Nov 6, 2015

    Creating a new RFE based on Community RFE #79368 in product PowerVC.