://groups.google.com/d/msgid/puppet-users/87fc30ff-bbcf-4c20-b2a4-602703f9f6af%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/87fc30ff-bbcf-4c20-b2a4-602703f9f6af%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://group
gt; from remote server: Error 500 on SERVER: Server Error: Evaluation Error:
> Error while evaluating a Resource Statement, Could not autoload
> puppet/type/ios_config: no such file to load -- puppet/resource_api
> (file: /etc/puppetlabs/code/environments/production/manifests/site.pp,
&
06 PM UTC, amateo wrote:
>
> El 5/12/18 a las 12:11, Will Meek escribió:
> > Hi Angel,
> >
> > Thank you for the detail so far!
> >
> > The only way I can reproduce this on my setup is with having
> > puppetlabs-cisco_ios 0.5.0 installed in the produ
Hi Angel,
Thank you for the detail so far!
The only way I can reproduce this on my setup is with having
puppetlabs-cisco_ios 0.5.0 installed in the production environment, whereby
puppet tries to pick up the old 'ios' provider rather than the >0.6.0
'cisco_ios' provider.
puppet device --verbo
Hi Angel,
I'm having a look at this now.
The manifest you supplied looks to be device_manager setup, which is
executed either by an agent (if set in an environment) or 'puppet apply'
rather than 'puppet device'.
This sets up the device.conf ready for puppet device.
Can you tell me if you get
