tree 0b1f25c95d9c7ed7ccc8c61f632b9e815be2b996
parent d35c241d30bba30a1d42ebc85ef8072f283cb820
author Gunnar Mills <gmills@us.ibm.com> 1736265166 -0600
committer Gunnar Mills <gmills@us.ibm.com> 1736265443 -0600

SW: Don't log if no association

We define logging levels in DEVELOPING.md[1], an error is "Something
went wrong, and we weren't able to give the expected response. Service
is still operational. "error" should be used for unexpected conditions
that prevented bmcweb from fulfilling the request. "error" shall be used
for 5xx errors.".

This clearly isn't an error since we just ignore not having an
association and move on. Moved these traces to DEBUG. Andrew mentioned
these cluttering the journal when running CI.

[1]: https://github.com/openbmc/bmcweb/blob/master/DEVELOPING.md#logging-levels

Tested: This is changing a Logging Level only.

Change-Id: If9324ab32a1f30f446a1b6f359d8a76af899378a
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>