Server Error: no parameter named 'provider'

[Sergio Pelissari]

Hello I'm trying to test the puppet module but I'm getting some issues

root@puppet:/etc/puppetlabs/code/environments/production# gem list | grep goo

google-api-client (0.19.2)

googleauth (0.6.2)

root@puppet:/etc/puppetlabs/code/environments/production# puppet module list

/etc/puppetlabs/code/environments/production/modules

├── google-cloud (v0.2.2)

├── google-gauth (v0.2.0)

├── google-gcompute (v0.2.1)

├── google-gcontainer (v0.2.0)

├── google-gdns (v0.1.1)

├── google-glogging (v0.1.1)

├── google-gpubsub (v0.1.0)

├── google-gspanner (v0.1.0)

├── google-gsql (v0.2.0)

├── google-gstorage (v0.2.0)

├── puppetlabs-apt (v4.4.1)

└── puppetlabs-stdlib (v4.24.0)

And also I generated a json via gcloud sdk tool

node default {

  gauth_credential { 'engine-only':

  provider => defaultuseraccount,

  path     => '/root/.config/gcloud/application_default_credentials.json',

  scopes   => ['https://www.googleapis.com/auth/cloud-platform'],

  }

}

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'provider' at /etc/puppetlabs/code/environments/production/manifests/site.pp:3 on Gauth_credential[engine-only] at /etc/puppetlabs/code/environments/production/manifests/site.pp:3 on node puppet

Warning: Not using cache on failed catalog

Error: Could not retrieve catalog; skipping run

##Provider commented

node default {

  gauth_credential { 'engine-only':

  #provider => defaultuseraccount,

  path     => '/root/.config/gcloud/application_default_credentials.json',

  scopes   => ['https://www.googleapis.com/auth/cloud-platform'],

  }

}

root@puppet:/etc/puppet/

root@puppet:/etc/puppetlabs/code/environments/production# puppet agent -t

Info: Using configured environment 'production'

Info: Retrieving pluginfacts

Info: Retrieving plugin

Info: Loading facts

Info: Caching catalog for puppet

Info: Applying configuration version '1515976474'

Error: Failed to apply catalog: gauth_credential[engine-only] does not have a provider

I think that I'm walking in circles 

[Sergio Pelissari]

Forgot to mention my system:

root@puppet:/etc/puppetlabs/code/environments/production# cat /etc/debian_version

8.7

[Nelson Araujo]

Hi Sergio,

Thanks for reporting this to us. Please allow me to investigate and get back to you.

Best regards,

-- Nelson

[Nelson Araujo]

Hi Sergio,

It seems there's an issue with using the google-gauth module from within a Puppet Master. It currently works properly on a non-master though. I filed an issue in GitHub to track this and we're currently working on a fix. You may want to follow the issue development at the link below:

https://github.com/GoogleCloudPlatform/puppet-google-auth/issues/2

I hope to get this resolved soon.

Regards,

-- Nelson

[Cody Herriges]

Sergio,

Thank you again for bringing the issue to our attention and I apologize for the delay in providing an update. There are two issues at work here. The first is that the documented gems need to be installed differently when using the Puppet Server, https://puppet.com/docs/puppetserver/5.1/gems.html#installing-and-removing-gems. The second issue is that the default JRuby version bundled in the Puppet Server is compatible with Ruby 1.9 and there are libraries used by the Google modules that require Ruby 2.0.

I and Nelson will have to dig a bit further and see if there is a workaround and/or when Puppet Server is slated to move to JRuby 9k. I'll post here again when I have another update.

[Cody Herriges]

The work around I was able to get from our Puppet Server team here at Puppet was that we ship the server with the optional ability to enable jRuby 9k. That documentation can be found here https://puppet.com/docs/puppetserver/5.1/configuration.html#enabling-jruby-9k. I've validated that doing this does allow the installation of the required Google gems and so results in a successfully compiled catalog using gauth. Feedback from engineering was jRuby 9k support is still a WIP so mileage may vary. They're also quite interested in your experience with 9k if you choose to do the route of using it.

[Sergio Pelissari]

Great, i will check this documentation and let you know about my tests. 

[Cody Herriges]

 Sergio,

Something you might wish to follow given you're now in the thick of Puppet's JRuby 9k implementation.

This is the epic that encapsulates all the ongoing work: https://tickets.puppetlabs.com/browse/SERVER-1789