x/packstack
Code Issues Proposed changes

teach packstack about "could not autoload" errors

Browse Source 
If a Puppet custom type/provder/etc fails to load because of missing
dependencies, Puppet will log an error of the form:

Could not autoload <thing>: Could not autoload </path/to/module.rb>: no such file to load -- rubygems at
</path/to/manifest.pp>:<linenumber> on node <hostname>

This change teaches packstack to recognize any messages starting with
'Could not autoload' as errors.

Change-Id: I3e0cb7f5e8871cfdc122dfea3adcb2bb7a8d31d1
Closes-bug: 1312224
This commit is contained in:
Lars Kellogg-Stedman 2014-04-24 10:59:44 -04:00
parent f43d0869c7
commit ccbb52d537
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
packstack/modules/puppet.py
View File

@ -16,6 +16,7 @@ re_error = re.compile(
'^No matching value for selector param|^Parameter name failed:|Error:|'
'^Invalid parameter|^Duplicate declaration:|^Could not find resource|'
'^Could not parse for|^/usr/bin/puppet:\d+: .+|.+\(LoadError\)|'
'^Could not autoload|'
'^\/usr\/bin\/env\: jruby\: No such file or directory'
)
re_ignore = re.compile(