Error log when upgrading app is actually expected

[Thiago Paiva Brito]

Brief Description
-----------------
During the app upgrade process we noticed that there is a time span in which the old and the new version of the app is supposed to be on the DB. This LOG.exception() message is too flashy and can lead to wrong conclusions during debug.

Severity
--------
Minor: System/Feature is usable with minor issue

Steps to Reproduce
------------------
Upgrade any app and check the logs

Expected Behavior
------------------
Logs help to find errors

Actual Behavior
----------------
Log for exception is actually the expected behavior

Reproducibility
---------------
3/3

System Configuration
--------------------
All configurations

Test Activity
-------------
Developer Testing

Workaround
----------
N/A

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/config/+/833630
Committed: https://opendev.org/starlingx/config/commit/a87285fbd2470ad9f146fc447bdda99ecce1ad7b
Submitter: "Zuul (22348)"
Branch: master

commit a87285fbd2470ad9f146fc447bdda99ecce1ad7b
Author: Thiago Brito <email address hidden>
Date: Mon Mar 14 11:11:18 2022 -0300

    Demote log when multiple entries of app is found

    During the app upgrade process we noticed that there is a time span in
    which the old and the new version of the app is supposed to be on the
    DB. This LOG.exception() here is too flashy and can lead to wrong
    conclusions during debug, so I'm moving demoting it to debug and adding
    a less impacting info log.

    Closes-Bug: 1978861

    Signed-off-by: Thiago Brito <email address hidden>
    Change-Id: I65b1ba62ac34b5e2389e52d4f1532855eade019c