Found this when reviewing my code changes in 7.2.0.
When a CT publisher with direct publishing enabled is used, and a certificate is renewed, it will send the certificate chain in database (i.e. with the previous certificate) to the CT log.
In this situation, we should submit the just renewed certificate.
This is a "regression" in 7.2.0. In earlier versions, you would get a NullPointerExcepiont in this case.