more specific parsing of "netstat" output in proxy sharding tests

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0, 8.0.10, 8.1.2, 7.0.22
    • Affects Version/s: None
    • Component/s: None
    • None
    • Networking & Observability
    • Fully Compatible
    • ALL
    • v8.1, v8.0, v7.0
    • Hide

      Run the jstests/sharding/proxy_protocol_connect.js test on a platform that does not have the "ss" command line tool available, such as Red Hat's UBI8.

      The test will fail to find the correct serverPort(), instead finding the client port of a defunct TIME_WAIT connection, because it is listed first in the output of netstat.

      Show
      Run the jstests/sharding/proxy_protocol_connect.js test on a platform that does not have the "ss" command line tool available, such as Red Hat's UBI8. The test will fail to find the correct serverPort(), instead finding the client port of a defunct TIME_WAIT connection, because it is listed first in the output of netstat.
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The issue in <https://jira.mongodb.org/browse/BF-37432> is that netstat will produce multiple lines of output. The first line that matches the desired regular expression might refer to a defunct connection from a previous client. When using netstat to find the reverse proxy's upstream ephemeral port (the "server port"), we need to further require "ESTABLISHED" in the output.

            Assignee:
            David Goffredo
            Reporter:
            David Goffredo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: