lightning community – funding_tx from lncli openchannel doesn’t present anyplace

I setup 6 lnd nodes(lnd-0, lnd-1 ~ lnd-5) within the native community, every of them anchoring to bitcoin node.
I attempted a number of occasions following steps: (from lnd-0 for instance)

1. begin lnd
2. lncli create
3. lncli join {identity_pubkey of lnd-1}@{lnd-1 ip addr}:9735
4. lncli openchannel {identity_pubkey of lnd-1} 100000

now I get ‘funding tx’ from the 4th command however ‘lncli listchannels’ doesn’t present something nevertheless it reveals in ‘lncli pendingchannels’. I can not discover the funding tx by both ‘bitcoin-cli getmempoolentry {funding_tx}’ nor within the block explorer.
Looks like there’s been some misconfiguration with the lnd. however the results of ‘lncli getinfo’ simply appears to be superb.

    "synced_to_chain":  true,
    "synced_to_graph":  true,
    "testnet":  false,
    "chains":  [
        {
            "chain":  "bitcoin",
            "network":  "mainnet"
        }
    ],
    "uris":  [],
    "options":  {
        "0":  {
            "identify":  "data-loss-protect",
            "is_required":  true,
            "is_known":  true
        },
        "5":  {
            "identify":  "upfront-shutdown-script",
            "is_required":  false,
            "is_known":  true
        },
        "7":  {
            "identify":  "gossip-queries",
            "is_required":  false,
            "is_known":  true
        },
        "8":  {
            "identify":  "tlv-onion",
            "is_required":  true,
            "is_known":  true
        },
        "12":  {
            "identify":  "static-remote-key",
            "is_required":  true,
            "is_known":  true
        },
        "14":  {
            "identify":  "payment-addr",
            "is_required":  true,
            "is_known":  true
        },
        "17":  {
            "identify":  "multi-path-payments",
            "is_required":  false,
            "is_known":  true
        },
        "23":  {
            "identify":  "anchors-zero-fee-htlc-tx",
            "is_required":  false,
            "is_known":  true
        },
        "25":  {
            "identify":  "route-blinding",
            "is_required":  false,
            "is_known":  true
        },
        "27":  {
            "identify":  "shutdown-any-segwit",
            "is_required":  false,
            "is_known":  true
        },
        "30":  {
            "identify":  "amp",
            "is_required":  true,
            "is_known":  true
        },
        "31":  {
            "identify":  "amp",
            "is_required":  false,
            "is_known":  true
        },
        "45":  {
            "identify":  "explicit-commitment-type",
            "is_required":  false,
            "is_known":  true
        },
        "2023":  {
            "identify":  "script-enforced-lease",
            "is_required":  false,
            "is_known":  true
        }
    },
    "require_htlc_interceptor":  false,
    "store_final_htlc_resolutions":  false

What do I must look into to get any trace to resolve this drawback?