signet: unable to fund channel with peer until I run listpeers

[jamesdorfman]

Issue and Steps to Reproduce

I've encountered the following issue when running CLN on top of bitcoin signet.

I have two nodes running on the same system: l1 and l2. I've aliased their lightning-cli calls in my terminal with l1-cli and l2-cli.

I was able to connect l1 to l2 as follows:

$ l2-cli getinfo
{
   "id": "03fbac8d9dff83acb31a640d016dae3c4bfae3f94f33f9418bb0891cbed937994b",
   "alias": "YELLOWBOUNCE",
   "color": "03fbac",
   "num_peers": 0,
   "num_pending_channels": 0,
   "num_active_channels": 0,
   "num_inactive_channels": 0,
   "address": [],
   "binding": [
      {
         "type": "ipv4",
         "address": "0.0.0.0",
         "port": 39376
      }
   ],
   "version": "v23.08.1",
   "blockheight": 169727,
   "network": "signet",
   ...
}

$ l1-cli connect 03fbac8d9dff83acb31a640d016dae3c4bfae3f94f33f9418bb0891cbed937994b@0.0.0.0:39376
{
   "id": "03fbac8d9dff83acb31a640d016dae3c4bfae3f94f33f9418bb0891cbed937994b",
   "features": "08a0000a0269a2",
   "direction": "out",
   "address": {
      "type": "ipv4",
      "address": "0.0.0.0",
      "port": 39376
   }
}

However, when I try to fund a channel from l1 to l2 I get the following error output:

$ l1-cli fundchannel 03fbac8d9dff83acb31a640d016dae3c4bfae3f94f33f9418bb0891cbed937994b 12000
{
   "code": 400,
   "message": "Unable to connect, no address known for peer",
   "data": {
      "id": "03fbac8d9dff83acb31a640d016dae3c4bfae3f94f33f9418bb0891cbed937994b",
      "method": "connect"
   }
}

And that kept happening until I ran listpeers:

$ l1-cli listpeers
{
   "peers": [
      {
         "id": "03fbac8d9dff83acb31a640d016dae3c4bfae3f94f33f9418bb0891cbed937994b",
         "connected": true,
         "num_channels": 0,
         "netaddr": [
            "0.0.0.0:39376"
         ],
         "features": "08a0000a0269a2",
         "channels": []
      }
   ]
}

Then, my channel funded perfectly

$ l1-cli fundchannel 03fbac8d9dff83acb31a640d016dae3c4bfae3f94f33f9418bb0891cbed937994b 12000
{
   "tx": ...,
   "txid": ...,
   "channel_id": ...,
   "outnum": 0
}

I'm not sure if this was a one-time thing, or if this a general case for running on signet. I don't think I should need to run listpeers before being able to connect to my peer. That seems like it could be some sort of bug.

Please let me know if you need any more information from me in order to reproduce this. Thanks.