Closed EmersonPrado closed 8 months ago
was this in before, or did i break it while migratin' it to vox?
was this in before, or did i break it while migratin' it to vox?
It already happened (long) before.
Several attempts to reproduce the issue, with CentOS/Rock/RHEL 7 to 9 and Puppet 5 to 7, in different overall situations, all failed miserably. I'll take it as a failure not related to the module itself, but some misuse in my environment, and close this. I'll reopen if ever I can find a setup which throws the error.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce
This happened when trying to replace the server groups with wildfly service active. This requires one call to
wildfly::host::server_config
to remove default groups, and another to create a replacement group. Simplified code excerpt:What are you seeing
First Puppet agent run fails with:
What behaviour did you expect instead
Module should remove and add groups normally.
Any additional information you'd like to impart
All calls to
wildfly_resource
inwildfly::host::server_config
use the same title:/host=${hostname}/server-config=${server_name}
andwildfly_resource
type uses this path as namevar. My suggested fix is to use title/name as namevar inwildfly_resource
type and create unique titles in its calls inwildfly::host::server_config
.