Add logs when an on-fly migration is performing

[robert-zaremba]

Summary

Migration can take a long time, and we don't have much feedback

Goals

• Add log whenever we start a new module migration
• Add more cosmovisor logs

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

[alexanderbez]

I think @ValarDragon created a similar issue and even addressed it? Not sure. I would try to dig it up.

[ValarDragon]

I wrote these commits to fix the problems for Osmosis in our v5 upgrade: osmosis-labs@26abd7f osmosis-labs@f421dcb

^- I think those should be integrated into the mainline SDK

I had written this issue before for the cosmovisor side: #9672

[yaruwangway]

cool! @ValarDragon please integrate to mainline.
thank you!

[ValarDragon]

Do you have capacity to upstream them @yaruwangway ? I'd vastly prefer that.

I've found that upstreaming small commits on average takes 9x more of my time than writing the update in checking in for review, small nits, updating changelogs as we wait for it to get merged post-everyone-approving etc.

[yaruwangway]

hi @ValarDragon , ok, I can do it ! I actually need these logs for gaia next upgrade which depends on sdk0.45, I might either need to make a branch based off sdk 0.45 with logs or ask sdk do a backport with these logs.

[ValarDragon]

Awesome thanks! You should be able to backport the change to SDK v0.45, it doesn't break anything, and validators (and myself) really appreciated these logs during the Osmosis upgrade to v0.44

[yaruwangway]

it seems someone already added the log

[yaruwangway]

Hi @robert-zaremba , the migration logs are already added in sdk 0.46-alpha, shall we do a backport release of 0.45.1 with adding logs ? because next gaia release is likely to use sdk 0.45, I can make a pr and test the logs with gaia before the backport release.

[robert-zaremba]

Yes, I will add a backport. We want to release tomorrow 0.45.1, so let's merge