Issue #5231 has been updated by Nigel Kersten. Status changed from Unreviewed to Accepted
---------------------------------------- Bug #5231: Ambiguous "Could not run Puppet configuration client: A section with name updates already exists.." https://projects.puppetlabs.com/issues/5231 Author: Dan Trainor Status: Accepted Priority: Normal Assignee: Category: Target version: 2.6.x Affected Puppet version: 2.6.2 Keywords: A section with name, already exists Branch: Hi - This comes from a yum repo, but I believe that its more widespread, i.e. the error generated during a conflict is constructed in the same manner, and does not provide any additional information. <pre> Nov 8 12:01:09 checkmember01 puppet-agent[2954]: Could not run Puppet configuration client: A section with name updates already exists </pre> There was, indeed, a repo in a separate file (/etc/yum.repos.d/updates.repo) with a repo defined named 'updates'. Puppet was also trying to make a file called CentOS-Updates.repo, which, too, had a section called 'updates'. Although this does correctly generate as an error, as expected, the extent to which the error is disclosed is not sufficient. At the very least, I believe an indicator of which class, which resource, and exactly which file is/are affected by this conflict. This would save a considerable amount of time in trying to track down figure conflicts similar to this. -- 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.
