Quick fix for flaky integration tests. (#2325)
Quick fix for flaky integration tests. (#2325)

Until recently, no RPCs would be performed during integration tests until all
servers were up and running. In https://github.com/letsencrypt/boulder/pull/2246
we added code so that RA now calls SA.CountCertificatesRange immediately on
startup. This should be fine - the message should be queued by AMQP and get
handled when SA starts up, typically is less than 3 seconds. However, this
caused a flaky test failure in CI. It's possible in some of these cases that SA
is actually taking 3 seconds to start, or it's possible that there is a bug that
depends on start order.

This change moves the SA to start earlier, which seems to reduce flakiness but
is not a real fix to the problem.
ZCloud-Firstserver/boulder,letsencrypt/boulder,jsha/boulder,lucasallan/boulder,ibukanov/boulder,sophie-h/boulder,ibukanov/boulder,jfrazelle/boulder,letsencrypt/boulder,ZCloud-Firstserver/boulder,jfrazelle/boulder,bmw/boulder,ZCloud-Firstserver/boulder,lucasallan/boulder,lucasallan/boulder,ZCloud-Firstserver/boulder,letsencrypt/boulder,ibukanov/boulder,jsha/boulder,jfrazelle/boulder,sophie-h/boulder,bmw/boulder,jsha/boulder,jcjones/boulder,sophie-h/boulder,jcjones/boulder,jcjones/boulder,jcjones/boulder,jfrazelle/boulder,bmw/boulder