I'm about to skip it on test short.
I don't know why it takes so long; I haven't investigated. It does not appear to be a new thing (i.e. not caused by the recent cluster bootstrap changes - also the test is configured to run with a single range).
Perhaps it's expected to take so long...

@petermattis are you interested in taking a look?