Uploaded image for project: 'Modules'
  1. Modules
  2. MODULES-6637

iis : Port conflicts if only hostname is different in binding

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: iis, windows
    • Labels:
    • Template:
      MODULES Bug Template
    • Acceptance Criteria:
      Hide

      Two sites on the same node listening on the same port should not fail to create if the virtual host name is properly specified as different in the bindinginformation property of the manifest.

      Unit test passing in CI

      Show
      Two sites on the same node listening on the same port should not fail to create if the virtual host name is properly specified as different in the bindinginformation property of the manifest. Unit test passing in CI
    • Epic Link:
    • Team:
      Windows
    • Sprint:
      DevInfraOps 2020-12-23
    • Method Found:
      Customer Feedback
    • QA Risk Assessment:
      Needs Assessment

      Description

      Module Version: 4.3.0
      *Puppet Version: **
      *OS Name/Version: Windows **

      If two websites exist on a node and the only difference between those sites' binding information is the hostname, then the modules call to New-Website, passing the port number from the bindinginformation property, will still fail to create the web site. This is because only the port number is currently passed into the cmdlet, not the host name portion of the bindinginformation. Since another site already exists on that port number, and since Puppet immediately tries to start the site, the entire create operation will fail once the port collision error occurs.

      Desired Behavior:

      When a manifest specified two websites on the same port but with different virtual host names, both sites should be created and should start successfully.

      This can be achieved by using IIS PR #150 as a template for adding the hostheader information to the params hash passed to New-Website. The fix just needs to look at the bindinginginformation string provided by the user and set the -hostheader parameter value to the value provided by the user in the manifest.

       

      Actual Behavior:

      When a manifest specifies two web sites on the same node, listening on the same port, but with different virtual host names specified in the bindinginformation property, at least one of the sites will fail to be created because of the port collision. The virtual host name difference is not taken into account by the module.

        Attachments

          Activity

            People

            Assignee:
            william.hurt William Hurt
            Reporter:
            william.hurt William Hurt
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support