FYI: This happened because katello-installer nightlies were failing.
foreman-installer and katello-installer get out of sync resulting in
broken caches. The workaround is to install yard and puppet-strings:

/opt/puppetlabs/puppet/bin/gem install yard
/opt/puppetlabs/puppet/bin/gem install puppet-strings

Nightlies were fixed so this shouldn't happen anymore.

On Fri, May 05, 2017 at 03:58:39PM -0400, Tom McKay wrote:
> Specifically, using koji repos in boxes.yaml:
> 
> cmd: foreman-installer -v --scenario "katello-devel"
> --foreman-proxy-tftp=true --disable-system-checks
> --katello-devel-github-username thomasmckay
> 
> start: 2017-05-05 19:52:26.544551
> 
> end: 2017-05-05 19:52:27.828586
> 
> delta: 0:00:01.284035
> 
> stderr: /usr/share/gems/gems/kafo-2.0.1/lib/kafo/puppet_module.rb:69:in
> `parse': No Puppet module parser is installed and no cache of the file
> /usr/share/katello-installer-base/modules/katello_devel/manifests/init.pp
> is available. Please check debug logs and install optional dependencies for
> the parser. (Kafo::ParserError)
>     from /usr/share/gems/gems/kafo-2.0.1/lib/kafo/configuration.rb:97:in
> `block in modules'
>     from /usr/share/gems/gems/kafo-2.0.1/lib/kafo/configuration.rb:97:in
> `map'
>     from /usr/share/gems/gems/kafo-2.0.1/lib/kafo/configuration.rb:97:in
> `modules'
>     from /usr/share/gems/gems/kafo-2.0.1/lib/kafo/configuration.rb:207:in
> `params'
>     from /usr/share/gems/gems/kafo-2.0.1/lib/kafo/configuration.rb:217:in
> `preset_defaults_from_puppet'
>     from /usr/share/gems/gems/kafo-2.0.1/lib/kafo/kafo_configure.rb:285:in
> `set_parameters'
>     from /usr/share/gems/gems/kafo-2.0.1/lib/kafo/kafo_configure.rb:100:in
> `initialize'
>     from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in `new'
>     from /usr/share/gems/gems/clamp-1.0.0/lib/clamp/command.rb:133:in `run'
>     from /usr/share/gems/gems/kafo-2.0.1/lib/kafo/kafo_configure.rb:163:in
> `run'
>     from /sbin/foreman-installer:8:in `<main>'
>     to retry, use: --limit
> @/home/thomasmckay/.ansible/retry-files/devel.retry
> 
> 
> On Fri, May 5, 2017 at 3:54 PM, Tom McKay <[email protected]> wrote:
> 
> > Are there specific redmine issues tracking the failing forklift devel
> > failure? This is impacting closing out work for releases.
> >
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.

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

Reply via email to