[P2P] libp2p and networking tests are failing on an ubuntu 20.04 server

[0xBigBoss]

Objective

Investigate and triage why libp2p and networking tests are failing on an ubuntu 20.04 server.

?       github.com/pokt-network/pocket/libp2p   [no test files]
{"level":"warn","time":"2023-03-14T11:11:19-04:00","message":"resolved multiple addresses but only using one. See ticket #557 for more details"}
{"level":"warn","time":"2023-03-14T11:11:22-04:00","message":"resolved multiple addresses but only using one. See ticket #557 for more details"}
--- FAIL: TestPeerMultiAddrFromServiceURL_Error (3.59s)
    --- FAIL: TestPeerMultiAddrFromServiceURL_Error/fully_qualified_domain_name_with_scheme/fqdn (0.28s)
        url_conversion_test.go:101: 
                Error Trace:    /home/bigboss/pocket-network/pocket-v1/libp2p/network/url_conversion_test.go:101
                Error:          Error "failed to parse multiaddr \"/ip4/103.120.80.111/tcp\": unexpected end of multiaddr" does not contain "resolving peer IP for hostname"
                Test:           TestPeerMultiAddrFromServiceURL_Error/fully_qualified_domain_name_with_scheme/fqdn
                Messages:       actualMultiaddr: %!s(<nil>)
    --- FAIL: TestPeerMultiAddrFromServiceURL_Error/fully_qualified_domain_name_with_scheme/ip4 (3.30s)
        url_conversion_test.go:101: 
                Error Trace:    /home/bigboss/pocket-network/pocket-v1/libp2p/network/url_conversion_test.go:101
                Error:          Error "failed to parse multiaddr \"/ip4/103.120.80.111/tcp\": unexpected end of multiaddr" does not contain "resolving peer IP for hostname"
                Test:           TestPeerMultiAddrFromServiceURL_Error/fully_qualified_domain_name_with_scheme/ip4
                Messages:       actualMultiaddr: %!s(<nil>)
    --- FAIL: TestPeerMultiAddrFromServiceURL_Error/fully_qualified_domain_name_with_scheme/ip6 (0.00s)
        url_conversion_test.go:101: 
                Error Trace:    /home/bigboss/pocket-network/pocket-v1/libp2p/network/url_conversion_test.go:101
                Error:          Error "failed to parse multiaddr \"/ip4/103.120.80.111/tcp\": unexpected end of multiaddr" does not contain "resolving peer IP for hostname"
                Test:           TestPeerMultiAddrFromServiceURL_Error/fully_qualified_domain_name_with_scheme/ip6
                Messages:       actualMultiaddr: %!s(<nil>)
FAIL
FAIL    github.com/pokt-network/pocket/libp2p/network   3.628s

Origin Document

The tests should not fail.

Goals

• Fix failure or add documentation if a lapse in config or server setup

General issue deliverables

• Update the appropriate CHANGELOG(s)
• Update any relevant local/global README(s)
• Update relevant source code tree explanations
• Add or update any relevant or supporting mermaid diagrams

Testing Methodology

• Task specific tests or benchmarks: make ...
• New tests or benchmarks: make ...
• All tests: make test_all
• LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md

---

Creator: @0xBigBoss

[bryanchriswhite]

@0xBigBoss can you confirm at what commit are you seeing this and/or provide additional details about the environment? I have not been able to reproduce this locally despite using a fresh ubuntu 20.04 docker container (as of ed83458). Those tests should be failing on DNS resolution (trying to resolve garbage, like tcp) before it has the chance to error on the multiaddr parsing.

[0xBigBoss]

@bryanchriswhite ah yes, you should account for a search domain or search list.

# /etc/resolv.conf
search xyz

What's happening on my server is thinking tcp is a shortname and is checking tcp.xyz so it resolves to that provided IP address, 103.120.80.111.

[Olshansk]

@0xBigBoss This is a pretty small bug that is specific to your dev environment. Any chance you could take it on?