`onlynet=onion` for pruned node results in no peers #22384

onlynet=onion doesn't work for pruned node. Even after waiting for few minutes couldn't see any peers. Initially I thought it must be an issue because less onion nodes on testnet but it works fine for non-pruned node.

Expected behavior

Onion peers

Actual behavior

No peers

To reproduce

Node A (pruned) with bitcoin.conf:

testnet=1
prune=1024

onlynet=onion

Node B (non-pruned) with bitcoin.conf:

testnet=1
txindex=1

onlynet=onion

System information

<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->

• Master Branch

<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->

• Pop!_OS

<!-- Any extra information that might be useful in the debugging process. -->

Peers for Node B:

Peers for Node A:

$ bitcoin-cli getpeerinfo

[
]

Is this a bug or expected behavior and I am missing something?

Please provide the relevant excerpts from the debug log with the appropriate logging enabled.

I could finally see some peers in pruned node but it took some time.

Maybe they got connected after DNS seed query which waits for 300 seconds. So the issue is resolved I guess but still things work differently in pruned node for some reason:

debug.log for Node A(non-pruned): https://pastebin.com/1VrkvB52

debug.log for Node B(pruned): https://pastebin.com/W577CZXZ

bootstrapping is non-deterministic, so a small delay is expected when the randomly picked bootstrap peers are currently unreachable.