To improve the existing logging workflow in upgrade.

[devendra104]

There are a lot of problems faced during the upgrade and sometimes it's very hard to identify where is the problem and at which step it occurs just because of poor logging in the upgrade workflow.
In a very recent upgrade, During capsule sync operation, we get just keyboard interrupt failure(due to timed out) but didn't get the information like in which step it occurred.

Traceback (most recent call last):
  File "/home/[*******]/shiningpanda/jobs/9c28985c/virtualenvs/d41d8cd9/lib/python3.6/site-packages/nailgun/entity_mixins.py", line 100, in _poll_task
    time.sleep(poll_rate)
KeyboardInterrupt

The purpose of this issue to improve the logging in the current workflow to reduce the
the debugging effort.

[jyejare]

Great to see you are discussing and improving logging around upgrade. Its a must for a long time.

Initially, I tried as much logging as possible and that's the reason I introduced the "Highlight" logging level in upgrade and due to which we are getting upgrade highlights in Upgrade Email.

As time passed, a lot of things are updated in the upgrade, but I ack we care very less about logging and focused more on the platform to upgrade the satellite and capsule. Another reason for that is it's derived from automation-tools which lacks logging as well.

Go ahead !!