Issue #7677 has been updated by John Warburton.
Thanks Nigel. Please mark this as a duplicate Is there an open bug to track this in 2.7? ---------------------------------------- Bug #7677: catalog compilation reports success, with missing $modulepath $manifest $manifestdir https://projects.puppetlabs.com/issues/7677 Author: John Warburton Status: Accepted Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: We use environments quite a lot, and in this case is for each admin to have their own work area Puppet is compiling catalogs and reporting success, giving me a green in my dashboard, where I would **expect** failure because it cannot find anything in $modulepath $manifest $manifestdir. The ENC provides classes, parameters etc, which go into the catalog, but it cannot find any modules - which it complains about, but doesn't fail. Hence there are no resources Puppet master 2.6.6 on Solaris 10 U9, ruby 1.8.7-p249, on passenger 2.2.14, rack 1.1.0 <pre> puppet@engnadm010% less /local/puppet/etc/puppetmasterd.conf [Lmedavatt] modulepath = /u1/medavatt/svn-workspace/puppet/trunk/modules manifest = /u1/medavatt/svn-workspace/puppet/trunk/manifests/site.pp manifestdir = /u1/medavatt/svn-workspace/puppet/trunk/manifests </pre> But those directories don't exist <pre> puppet@engnadm010% ls -l /u1/medavatt/svn-workspace/puppet/trunk/manifests/site.pp /u1/medavatt/svn-workspace/puppet/trunk/modules /u1/medavatt/svn-workspace/puppet/trunk/manifests /u1/medavatt/svn-workspace/puppet/trunk/manifests/site.pp: No such file or directory /u1/medavatt/svn-workspace/puppet/trunk/modules: No such file or directory /u1/medavatt/svn-workspace/puppet/trunk/manifests: No such file or directory </pre> The ENC values are valid, and give us the environment to tell the puppet server to use above <pre> puppet@engnadm010% /local/puppet/bin/node_classifier.pl medavatt --- classes: - base - bbc_monitor_client - hpov_monitor_client - netbackup_client - puppet_client - security - software_adminopt environment: Lmedavatt parameters: client: blk homedirs: local ipmp_pair_link: vnet0:vnet1 location: ewd name_service: none veritas_version: 5.1 </pre> On a normal run, we can see the catalog being compiled against the running puppet server <pre> puppet@engnadm010% grep medavatt /var/adm/messages | tail -1 May 26 00:17:20 engnadm010 puppet-master[3379]: [ID 702911 daemon.notice] Compiled catalog for medavatt.insidelive.net in environment Lmedavatt in 0.04 seconds </pre> Which comes up as green light for 7 resources in the dashboard: <pre> Events tab: Events (expand all) Filebucket[puppet] Schedule[monthly] Schedule[never] Schedule[weekly] Schedule[puppet] Schedule[hourly] Schedule[daily] Metric tab: Metrics Events Total 0 Resources Total 7 Time Config Retrieval 1.65 seconds Filebucket 0.00 seconds Schedule 0.01 seconds Total 1.65 seconds </pre> Let's compile a catalog <pre> puppet@engnadm010% /opt/local/sbin/puppetmasterd --verbose --ignorecache --no-usecacheonfailure --config /local/puppet/etc/puppetmasterd.conf --environment Lmedavatt --compile medavatt.insidelive.net > /tmp/medavatt puppet@engnadm010% cat /tmp/medavatt info: Not using expired node for medavatt.insidelive.net from cache; expired at Wed May 25 23:47:20 -0400 2011 info: Caching node for medavatt.insidelive.net info: Could not find class base for medavatt.insidelive.net info: Could not find class bbc_monitor_client for medavatt.insidelive.net info: Could not find class hpov_monitor_client for medavatt.insidelive.net info: Could not find class netbackup_client for medavatt.insidelive.net info: Could not find class puppet_client for medavatt.insidelive.net info: Could not find class security for medavatt.insidelive.net info: Could not find class software_adminopt for medavatt.insidelive.net notice: Compiled catalog for medavatt.insidelive.net in environment Lmedavatt in 0.06 seconds { "data": { "edges": [ { "target": "Class[main]", "source": "Stage[main]" } ], "name": "medavatt.insidelive.net", "resources": [ { "exported": false, "title": "Settings", "tags": [ "class", "settings" ], "type": "Class" }, { "exported": false, "title": "main", "parameters": { "name": "main" }, "tags": [ "class" ], "type": "Class" }, { "exported": false, "title": "main", "parameters": { "name": "main" }, "tags": [ "stage" ], "type": "Stage" } ], "tags": [ "base", "bbc_monitor_client", "hpov_monitor_client", "netbackup_client", "puppet_client", "security", "software_adminopt", "settings" ], "classes": [ "base", "bbc_monitor_client", "hpov_monitor_client", "netbackup_client", "puppet_client", "security", "software_adminopt", "settings" ], "version": 1306383128 }, "metadata": { "api_version": 1 }, "document_type": "Catalog" } </pre> -- 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.
