Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-34769

Server detects wrong FQDN when running Windows on AWS

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 3.6.4
    • Component/s: Networking
    • None
    • ALL
    • Hide

      Launch a Windows host of type windows-64-vs2015-small. Download and install MongoDB onto the VM and start a MongoDB process. From the Mongo shell, run the following command:

      db.runCommand({ serverStatus: 1, advisoryHostFQDNs: 1 })

      The advisoryHostFQDNs field in the resulting document will contain the incorrect hostname.

      Show
      Launch a Windows host of type windows-64-vs2015-small. Download and install MongoDB onto the VM and start a MongoDB process. From the Mongo shell, run the following command: db.runCommand({ serverStatus: 1, advisoryHostFQDNs: 1 }) The advisoryHostFQDNs field in the resulting document will contain the incorrect hostname.

      When running on a Windows box on AWS, the server will detect an FQDN of the form WIN-T1NSTPV2UDM.ec2.internal, which is not correct. The correct hostnames for such an AWS box are WIN-T1NSTPV2UDM and ip-10-122-16-56.ec2.internal.

      This bug is blocking us from being able to run our E2E tests on Windows on Evergreen, so please prioritize.

      CC justin.moses mark.benvenuto

            Assignee:
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Reporter:
            david.golub@mongodb.com David Golub
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: