Open tuminoid opened 1 month ago
Yeah, while some controller do log the cause, the BareMetalHost and BMCEventSubscription ones do not. I agree it's a problem.
/triage accepted /help
@dtantsur: This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help
command.
@dtantsur, @tuminoid I would like to take it up, if you could give me some pointers to look into. I saw 5 reconcile functions, does all of these requires this modification
@babugeet grep the source code for "provisioner is not ready". You'll see several instances of this phrase in different controllers. Some include the error message that caused it, some do not. Those that don't require fixing.
/assign
When debugging https://github.com/metal3-io/baremetal-operator/issues/1785 we get https://github.com/metal3-io/baremetal-operator/issues/1785#issuecomment-2167804321 once per node, and after that BMO sits in
provisioner is not ready
loop forever, without printing the root cause again. This makes issues hard to debug, as even in normal boot up of BMO / Ironic,provisioner is not ready
is printed for some time.We may even cases where there would be multiple problems and BMO would not print the other one at all, since it sits in reconcile loop.
It would hence be great, if BMO could print the error message more than once.
/kind bug
BMO version: main