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

2019-03-28 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper commented on  PUP-8218  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources   
 

  
 
 
 
 

 
 It seems possible to print both resources that participate in the collision. I don't think puppet can say which one is the "right" one, just that there's a conflict.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


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

2018-01-09 Thread Alex P (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex P commented on  PUP-8218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 
 
to add the my comment above, if you do that additional line on Host B, then the Puppet Server log message will say: 
 
 
 
 
 
 
Server Error: A duplicate resource was found while collecting exported resources, with the type and title Host[host-a.domain.com] on node host-a.domain.com
 
 
 
 
 
 
 
So, it'll be pointing to and blaming Host A, but not the other one.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


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

2018-01-09 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-8218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 
 
Sounds like this could be related to PDB-3734. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


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

2018-01-09 Thread Alex P (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex P commented on  PUP-8218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 
 
Eric Sorenson, it's quite easy to reproduce, you have the following: 
 

Host A, fqdn - host_a.domain.com, IP - 10.0.0.10
 

Host B, fqdn - host_b.domain.com, IP - 10.0.0.20
 

Puppet Server
 
 
Add a line on 

Host B
 in /etc/hosts: 
 
 
 
 
 
 
10.0.0.20 host_a.domain.com   host_a
 
 
 
 
 
 
 
The Puppet Server will continue to serve Host B but NOT Host A. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving 

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

2018-01-08 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  PUP-8218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 
 
Going to close this as "cannot reproduce" since it relies on local system misconfiguration. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


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

2018-01-08 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  PUP-8218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 
 
Hi Alex P - first thank you for filing this, and I'm glad you figured out the problem! 
The log message says: 
 
 
 
 
 
 
Server Error: A duplicate resource was found while collecting exported resources, with the type and title Host[__PUPPETNODE__] on node __PUPPETNODE__
 
 
 
 
 
 
 
so it does show the type and title of the resource (a "host") resource. As far as the security issue, it requires both a hosts entry and your particular setup with the hosts file being managed by exported resources. So I don't think this is something Puppet can guard against inherently.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


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

2018-01-08 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8218 
 
 
 
  Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Team:
 
 Platform Core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


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

2018-01-08 Thread Craig Gomes (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Craig Gomes updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8218 
 
 
 
  Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 

Change By:
 
 Craig Gomes 
 
 
 

Priority:
 
 Major Normal 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


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

2018-01-08 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8218 
 
 
 
  Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Sorenson 
 
 
 

Priority:
 
 Blocker Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


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

2017-12-07 Thread Alex P (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex P commented on  PUP-8218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 
 
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-, fqdn - .dev.
 

QA: hostname - dev--qa, fqdn - .qa. 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: 
 

.dev..yaml
 

.qa..yaml
 
 
Both nodes have certname's in their puppet.conf }} as {{.dev. and .qa. 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/.qa..yaml:  fqdn: .dev.
 
 
 
 
 
 
 
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. 
 
 
 
 
 
 
 
 
   

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

2017-11-29 Thread Alex P (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex P commented on  PUP-8218 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 
 
btw, agent's puppet.conf is very simple: 
 
 
 
 
 
 
[main] 
 
 
 
 
certname = __PUPPETNODE__ 
 
 
 
 
server = __PUPPETMASTER__ 
 
 
 
 
runinterval = 1h 
 
 
 
 
environment = corporate
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) 
 
 
 
 
  
 
 
 
  

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

2017-11-29 Thread Alex P (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex P updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8218 
 
 
 
  Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 

Change By:
 
 Alex P 
 
 
 
 
 
 
 
 
 
 First of all, our Puppet installation has been around for at least two year or so. The subject node has been part of it since the beginning. Everything worked fine until some upgrade (hard to trace, as we have them on semi-automatic mode).Since about a month or so ago receiving the following error:{code}> sudo puppet agent -tInfo: Using configured environment 'corporate'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsError: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources, with the type and title Host[ svetoshkin.dev.wpninc.com __PUPPETNODE__ ] on node  svetoshkin.dev.wpninc.com  __PUPPETNODE__ Warning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run{code}All settings are described via Hiera. Its hierarchy as follows:{code}hierarchy:  - name: "Nodes"path: "nodes/%{::trusted.certname}.yaml"  - name: "Role 1"path: "roles/%{::role_1}.yaml"  - name: "Role 2"path: "roles/%{::role_2}.yaml"  - name: "Role 3"path: "roles/%{::role_3}.yaml"  - name: "Role 4"path: "roles/%{::role_4}.yaml"  - name: "Groups"path: "groups/%{::group}.yaml"# compatibility  - name: "Roles"path: "roles/%{::role}.yaml"  - name: "Virtual"path: "virtual_%{::is_virtual}.yaml"  - name: "OS"path: "os_%{::operatingsystem}.yaml"  - name: "OS Realese"path: "os_%{::operatingsystem}_%{::operatingsystemmajrelease}.yaml"  - name: "Environment"path: "env_%{environment}.yaml"  - name: "Common Defaults"path: "common.yaml"{code}The subject node falls under the following environment:- ::trusted.certname - __PUPPETNODE__- ::role_[1-4] - not set- ::group - _dev_vm_- ::is_virtual - true- ::operatingsystem - Debian- ::operatingsystemmajrelease - 8- environment - corporate__PUPPETNODE__.yaml practically contains just 5 lines:{code}dev_username: "first_lastname"sudo::configs:  'teamlead':  'content' : "teamlead ALL=(ALL:ALL) NOPASSWD: ALL, !SU, !SHELLS, !SUDO"  'ensure'  : 'present'bacula::client::password: '...'nslcd::ldap_search_bases:  - OU=..samba::server::netbios_name: 'DEV-USERNAME'{code}There 10+ other nodes that fall under _dev_vm_ category and which ARE working fine. The same template node YAML configuration files.A debug log (attached) doesn't show anything extraordinary.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
   

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

2017-11-29 Thread Alex P (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex P created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-8218 
 
 
 
  Error 500 on SERVER: Server Error: A duplicate resource was found while collecting exported resources  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 5.3.3 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Attachments:
 

 puppetserver-20171129-debug.log 
 
 
 

Created:
 

 2017/11/29 12:26 PM 
 
 
 

Environment:
 
 
Agent: Debian GNU/Linux 8.9 (jessie) puppet-agent 5.3.3-1jessie 
Server: Debian GNU/Linux 9.2 (stretch) 
 
 
 
 
 
 
> dpkg -l | grep pupp 
 
 
 
 
ii  puppet-agent 5.3.3-1stretch 
 
 
 
 
ii  puppetdb 5.1.3-1stretch  
 
 
 
 
ii  puppetdb-termini 5.1.3-1stretch