Issue #7434 has been reported by Nick Fagerlund.
----------------------------------------
Bug #7434: Mangled stringification of regexes causes bogus node titles and
conflicts
https://projects.puppetlabs.com/issues/7434
Author: Nick Fagerlund
Status: Unreviewed
Priority: Normal
Assignee:
Category:
Target version:
Affected Puppet version:
Keywords:
Branch:
When using regex nodes, we determine the title of the resulting node construct
by:
* Stringifying the regex.
* Deleting all instances of characters that are on a secret list.
(See issue #7423.)
If you have two regex nodes whose regexen match a disjunct set of requests but
yield identical strings post-munging, they'll show up as a duplicate node
definition and all compilation requests will fail.
node /\wa[ve]s/ {
# matches strings like havs, baes, cavs, javs, daes
}
node /w[ave]s/ {
# matches either was, wvs, or wes
}
On agent:
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Node 'waves' is already defined at /etc/puppet/manifests/site.pp:28; cannot
redefine at /etc/puppet/manifests/site.pp:32 on node hawkmaster.magpie.lan
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Dan Bode tells me this also presents a problem for introspection, as the actual
titles of the node definitions can't be reconstructed by their names in the
graph. (Lossy text compression, yay.)
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
