This issue has happened on March 3rd (and we had users complain that their logging infrastructure was bombarded with those logs. To circumvent overloading, we had them apply exclusion rules. Those who weren't aware (and had these logs written the the logging infrastructure have seen a big increase in their logs and hence the bills). We are trying to understand if any changes were made to crio on that date to make this message be written to the logs.

I had checked the change log, and the only change around this was to drop ImageStatus message with this change

Can you please see the attached log file and shed any light as to why these messages started appearing on March 3rd?

crio_msg.log