Jira (PUP-8218) Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources

Title: Message Title

Alex P commented on

PUP-8218

Troubleshooted and resolved the issue. The problem was partially on our side in misconfiguration, partially in Puppet/Facter behaviour.

A bit more about our environment, our devs have 2 VMs assigned to each of them, named as:

DEV: hostname - dev-<username>, fqdn - <username>.dev.<domain>
QA: hostname - dev-<username>-qa, fqdn - <username>.qa.<domain>
In DNS, hostnames are linked to fqdn via CNAME's.

There are two YAML files in /etc/puppetlabs/code/environments/corporate/hieradata/nodes/ on Puppet server:

Both nodes have certname's in their puppet.conf }} as {{<username>.dev.<domain> and <username>.qa.<domain> correspondingly.

The trouble host that didn't want to sync was the DEV instance.

After checking the whole facts database, found an interesting line:

/opt/puppetlabs/server/data/puppetserver/yaml/facts/<username>.qa.<domain>.yaml:  fqdn: <username>.dev.<domain>

I.e. the QA node had DEV's fqdn!!!
Long story short, there was misconfiguration in /etc/hosts. That was our side of the problem.

A bigger, security issue on the Puppet/Facter part:

no logging of which exactly resource is duplicated
while two hosts have different DNS names, different values in certname fields and different signed certificates, a simple record in /etc/hosts on one node can deny another host in service.

Please advise.

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Reply via email to