delete realm nodes in depth-first order to workaround augeas segfault #111
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DavidS
added a commit
that referenced
this pull request
Dec 2, 2015
delete realm nodes in depth-first order to workaround augeas segfault
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Several reports have come in from customers experiencing segfaults from augeas during puppet runs when using the tomcat module.
Modules ticket: https://tickets.puppetlabs.com/browse/MODULES-1721
I've captured a full description of the problem with agueas over at hercules-team/augeas#319 but fixing this properly is going to involve a new release of the augeas library and therefore a new puppet-agent release.
This PR fixes the segfault by performing a depth-first deletion of all
Realmelements.