voxpupuli / voxpupuli/puppet-php
Pool config not removed after configuration update
Nobody has claimed this yet.
- Dominant language
- Puppet
- Stars
- 86
- Forks
- 264
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
Recently i removed some pools from configuration (without ensure:absent, just reconfigured) and I didn't noticed that conf files are still there. Later after adding new pool with same listen address/port i got awaitable: unable to set listen address as it's already used in another pool
Is this nonremoving behavior by design? Did i miss some option? I know that I can workaround this with preservation of removed configuration with ensure:absent, but it will complicate things..
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing a configuration update that removes a pool without ensure:absent, then inspect how removed pool configuration files are handled. Use the reported listen address/port conflict to verify whether stale files remain after the update. Done means the intended removal behavior is defined and the subsequent pool addition no longer fails unexpectedly.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100