Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • P puppet-swh-site
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Platform
  • Infrastructure
  • Puppet
  • puppet-swh-site
  • Issues
  • #856

Running puppet agent on the puppet master results in error

Running puppet agent on the puppet master results in error.

ardumont@pergamon:~% sudo puppet agent --test
[sudo] password for ardumont:
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: A duplicate resource was found while collecting exported resources, with the type and title Icinga2::Object::Host[worker03.euwest.azure.internal.softwareheritage.org] on node pergamon.softwareheritage.org
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

I have been unable so far to understand clearly the issue.

In my peregrination, i noticed multiple warnings/critical message logs for icinga. It's relative to the db version being out of sync with its package version.

It might relate to having duplicates in data... (I'm really not sure but i think it's worth mentioning it here anyway).

Nov 23 17:24:45 pergamon icinga2[20113]: [2017-11-23 17:24:35 +0000] critical/IdoPgsqlConnection: Schema version '1.14.2' does not match the required version '1.14.3' (or newer)! Please check the upgrade documentation at https://docs.icinga.com/icinga2/latest/doc/module/icinga2/chapter/upgrading-icinga-2#upgrading-postgresql-db
Nov 23 17:24:45 pergamon icinga2[20113]: Context:
Nov 23 17:24:45 pergamon icinga2[20113]:         (0) Reconnecting to PostgreSQL IDO database 'ido-pgsql'

I'll adapt this when i see more clearly what happens (and possibly open another issue if that's not related).


Migrated from T856 (view on Phabricator)

Assignee
Assign to
Time tracking