[warn] We don't have a consensus, so we can't perform v2 rendezvous operations.

Start your Tor, and while it's bootstrapping, make an onion service request. (In my case I started 'apt-get update' which uses the apt-transport trick to make it use my Tor.)

Now I have in my logs:

Jul 30 20:27:11.890 [notice] Bootstrapped 25%: Loading networkstatus consensus
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.285 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.286 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:27:21.286 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.379 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.379 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.384 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.384 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.385 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:21.385 [warn] We don't have a consensus, so we can't perform v2 rendezvous operations.
Jul 30 20:29:58.498 [notice] Bootstrapped 45%: Asking for relay descriptors

I think maybe it shouldn't warn like that if it hasn't bootstrapped yet? Or, is there some specific value to warning there?