[RHOCP 4] osp-director-operator-controller-manager pod logs aren't detailed when resources such as openstackbaremetalset are created.

Solution Verified - Updated -

Issue

  • osp-director-operator-controller-manager pod logs do not show sufficient information when it comes to adding openstackbaremetalset.

  • When the BaremetalSet controller considers potential BaremetalHost resources as candidates for a scale-up request, it does not log all instances in which it cannot use a mismatched BaremetalHost.

  • Need logs that explicitly and clearly state in all circumstances why a BaremetalHost is an invalid candidate and cannot be used.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • OpenStack Platform Director Operator
    • 1.3.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content