psick: CI role doesn't work out of the box
I have an EC2 instance connecting to my new FOSS smaster. I’m using the CI role as an example, and I get:
root@puppetagent:/home/ubuntu# FACTER_role=ci puppet agent --test
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Value for key 'psick::profiles::linux_classes', returned from lookup_key function 'eyaml_lookup_key', when using location '/etc/puppetlabs/code/environments/production/hieradata/role/ci.yaml', has wrong type, expects Puppet::LookupValue, got Hash[Enum['gitlab', 'jenkins'], Runtime[ruby, 'Symbol'], 2, 2] on node puppetagent.sandbox.MUNGED.com
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
Any clues?
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 25 (15 by maintainers)
Commits related to this issue
- Fix for #198 — committed to example42/psick by alvagante 7 years ago
- Fix for #198 — committed to graduway/psick by alvagante 7 years ago
- Fix for #198 — committed to graduway/psick by alvagante 7 years ago
- Removed trailing ::in tp defines https://github.com/example42/psick/issues/198 — committed to example42/pdk-module-template-psick-tp-profile by alvagante 7 years ago
- Fix for #198 — committed to graduway/psick by alvagante 7 years ago
- Fix for #198 — committed to example42/psick by alvagante 7 years ago
- Align data to puppet-psick branch/198 Works for #198 — committed to example42/psick by alvagante 7 years ago
- Foss Puppet server setup improvements (#205) * Added jenkins role data * Fix for #203 * Align data to puppet-psick branch/198 Works for #198 * Updated FOSS setup docs #203 — committed to example42/psick by alvagante 7 years ago
- Foss Puppet server setup improvements (#205) * Added jenkins role data * Fix for #203 * Align data to puppet-psick branch/198 Works for #198 * Updated FOSS setup docs #203 — committed to example42/psick by alvagante 7 years ago
Brand new, and I’ve brought up a few masters today. 😉 I did rebase our fork’s production branch to remove a few of my commits, in light of fixes that you’ve done upstream. Perhaps there was a gremlin in there. We’re now on upstream production, apart from the postgres module fix.
The referenced commit fixes the problem. Going to be merged to production branch soon.