Details
-
Bug
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
-
Windows
-
1
-
Windows 2018-06-13
-
Customer Feedback
-
Normal
-
2 - 5-25% of Customers
-
3 - Serious
-
3 - $$$$
-
Any regression in our support modules creates an impression that they are unreliable. This issue deserves to be fixed in general, but even more so since it worked in previous versions.
-
Needs Assessment
Description
Basic Info
Module Version: 4.3.1
Puppet Version: N/A
OS Name/Version: Server 2016
When attempting to bring an application up on port 443 using the HTTPS protocol, the module will first attempt to bring it up using http, then apply the https protocol, this works fine for most ports, however IIS fobids port 443 from using http, and results in the misleading failure below"
// [0;36mDebug: STDOUT: Start-Website : Cannot create a file when that file already exists. (Exception from HRESULT: 0x800700B7)
|
|
|
At line:1 char:1 |
|
|
+ Start-Website -Name "puppet_site" -ErrorVariable errvar;if($errvar){ ... |
|
|
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
+ CategoryInfo : InvalidOperation: (:) [Start-Website], COMException
|
|
|
+ FullyQualifiedErrorId : InvalidOperation,Microsoft.IIs.PowerShell.Provider.StartWebsiteCommand
|
|
|
|
|
|
|
[0m
|
[0;36mDebug: ERRMSG: Cannot create a file when that file already exists. (Exception from HRESULT: 0x800700B7). Perhaps there is another website with this port or configuration setting |
|
Using the following code:
// iis_site { 'puppet_site':
|
ensure => 'started', |
applicationpool => 'puppet_site_pool', |
authenticationinfo => {
|
'basic' => false, |
'anonymous' => true, |
'windows' => false, |
'iisClientCertificateMapping' => false, |
'digest' => false, |
'clientCertificateMapping' => false |
},
|
enabledprotocols => 'https', |
bindings => [
|
{
|
'certificatestorename' => 'My', |
'protocol' => 'https', |
'sslflags' => 0, |
'certificatehash' => $facts['iis_thumbprint'], |
'bindinginformation' => '*:443:' |
}],
|
physicalpath => 'd:\\inetpub\\wwwroot', |
preloadenabled => false, |
|
|
}
|
also note the use of a fully qualified binding path was also attempted with no change to behaviour
dowgrading to 4.2.1 solves this issue
Desired Behavior:
the application should be started with the stated protocol immediately
Actual Behavior:
the application is brought up with http and then moved to https
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-