[RHOCP 4] osp-director-operator-controller-manager pod logs aren't detailed when resources such as openstackbaremetalset are created.
Issue
-
osp-director-operator-controller-managerpod logs do not show sufficient information when it comes to addingopenstackbaremetalset. -
When the
BaremetalSet controllerconsiders potentialBaremetalHostresources as candidates for a scale-up request, it does not log all instances in which it cannot use amismatched BaremetalHost. -
Need logs that explicitly and clearly state in all circumstances why a
BaremetalHostis aninvalid candidateand 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.