[MODULES-5195] iis : application_pool settings keep reapplying - Puppet Tickets

XML

Word

Printable

Template:
MODULES Bug Template customfield_10700 200012
Acceptance Criteria:
- Applying all iis_application_pool settings should be idempotent.
- Should be a kitchen-sink acceptance test where we apply ALL possible settings and make sure it's idempotent.
Epic Link:
IIS v4.1
Team:
Windows
Method Found:
Customer Feedback

CS Priority:
Major
CS Frequency:
3 - 25-50% of Customers
CS Severity:
4 - Major
CS Business Value:
4 - $$$$$
CS Impact:

Hide
This is a biggy, having your web server restart every 30mins because you manage it with Puppet is not ideal. Puppet should be idempotent. We need to make sure our windows features and modules are well maintained and working as expected or risk the perception that windows is not a first class citizen in our ecosystem.

Show
This is a biggy, having your web server restart every 30mins because you manage it with Puppet is not ideal. Puppet should be idempotent. We need to make sure our windows features and modules are well maintained and working as expected or risk the perception that windows is not a first class citizen in our ecosystem.

Desired Behavior:

Setting options like orphan worker process sets, but puppet keeps re-applying

Actual Behavior:

Should be idempotent.

Reason
The Get app pool code at https://github.com/puppetlabs/puppetlabs-iis/blob/master/lib/puppet/provider/templates/webadministration/_getapppools.ps1.erb does not mirror the actual location of the settings which are configured at https://github.com/puppetlabs/puppetlabs-iis/blob/master/lib/puppet/provider/iis_application_pool/webadministration.rb#L150-L212.

We should either manually update them, OR the get_appool template should dynamically generate the PowerShell based on the iis_settings variable.

is duplicated by

MODULES-5169 IIS: Application Pool parameters always result in a changed catalog

relates to

MODULES-5169 IIS: Application Pool parameters always result in a changed catalog