I was doing this… https://github.com/voxpupuli/puppet-jenkins/issues/1048

Facter.add(:jenkins_plugins) do
  confine kernel: 'Linux'
  setcode do
    plugins = Puppet::Jenkins::Plugins.available
    plugins.keys.sort.map { |plugin| "#{plugin} #{plugins[plugin][:plugin_version]}" }.join(', ')
  end
end

Changed to this

Facter.add(:jenkins_plugins) do
  confine kernel: 'Linux'
  setcode do
    Puppet::Jenkins::Plugins.available
  end
end

It does add a lot of info….

"jenkins_plugins": {
    "blueocean-dashboard": {
      "manifest_version": "1.0",
      "archiver_version": "Plexus Archiver",
      "created_by": "Apache Maven",
      "built_by": "olamy",
      "build_jdk": "11.0.13",
      "extension_name": "blueocean-dashboard",
      "specification_title": "The Jenkins Plugins Parent POM Project",
      "implementation_title": "blueocean-dashboard",
      "implementation_version": "1.25.2",
      "group_id": "io.jenkins.blueocean",
      "short_name": "blueocean-dashboard",
      "long_name": "Dashboard for Blue Ocean",
      "url": "<https://github.com/jenkinsci/blueocean-plugin/blob/master/blueoce>",
      "minimum_java_version": "1.8",
      "plugin_version": "1.25.2",
      "hudson_version": "2.277.4",
      "jenkins_version": "2.277.4",
      "plugin_dependencies": "blueocean-web:1.25.2",
      "plugin_developers": "Thorsten Iberian Sumurai:scherler:,Cliff Meyers:cli",
      "support_dynamic_loading": "true",
      "plugin_license_name": "MIT License",
      "plugin_license_url": "<https://opensource.org/licenses/MIT>",
      "plugin_scmurl": "<https://github.com/jenkinsci/blueocean-plugin/blueocean>"
    },
    "blueocean-autofavorite": {
      "manifest_version": "1.0",
      "archiver_version": "Plexus Archiver",
      "created_by": "Apache Maven",
      "built_by": "gmogan",
      "build_jdk": "1.8.0_192",
      "extension_name": "blueocean-autofavorite",
      "specification_title": "Automatically favorites multibranch pipeline jobs",
      "implementation_title": "blueocean-autofavorite",
      "implementation_version": "1.2.4",
      "group_id": "org.jenkins-ci.plugins",
      "short_name": "blueocean-autofavorite",
      "long_name": "Autofavorite for Blue Ocean",
      "url": "<https://wiki.jenkins-ci.org/display/JENKINS/Blue+Ocean+Autofavori>",
      "minimum_java_version": "1.8",
      "plugin_version": "1.2.4",
      "hudson_version": "2.121.1",
      "jenkins_version": "2.121.1",
      "plugin_dependencies": "workflow-job:2.32,branch-api:2.0.11,git-client:2.",
      "plugin_developers": "James Dumay:jdumay:jdumay@cloudbees.com"
    },
    "blueocean": {
      "manifest_version": "1.0",
      "archiver_version": "Plexus Archiver",
      "created_by": "Apache Maven",
...
...

This message was deleted.

See the

puppetlabs-apache

module at https://forge.puppet.com/puppetlabs/apache?src=slack&channel=puppet

I’m trying to get a PuppetDB 7 service up and running with a backend Postgresql 11 database on another node. The service connects to the database and then get stuck in a loop that seems to involve the schema_migrations table. The attached file shows the loop, which repeats every 10 to 15 seconds. How can I fix this?

Hey guys, I’ve upgrade the puppet agent from 7.4.0 to 7.18.0 and although I have also upgrade puppetdb-termini and puppetdb itself to version 7.11, the puppetdb logs are full of

1661972148606] [0 ms] 'replace catalog' command ignored (obsolete) for <HOST>
2022-09-01T14:03:06.397Z INFO  [p.p.command] [51312254-1661972150149] [0 ms] 'replace facts' command ignored (obsolete) for <HOST>

Any idea on what’s going on? I do see that version 80 of the migration succeeded (?):

2022-09-01T13:32:31.622Z INFO  [p.p.s.migrate] Locking migrations table before migrating
2022-09-01T13:32:31.647Z INFO  [p.p.s.migrate] Applying database migration version 80
2022-09-01T13:32:31.679Z INFO  [p.p.s.migrate] Applied database migration version 80 in 32 ms
2022-09-01T13:32:31.682Z WARN  [p.p.s.migrate] DEPRECATED: The `pg_trgm` extension will be required in PDB 7.0.0
2022-09-01T13:32:31.683Z WARN  [p.p.s.migrate] PostgreSQL extension `pg_trgm` missing.  Unable to create the recommended pg_trgm indexes.
2022-09-01T13:32:31.695Z INFO  [p.p.s.migrate] Updating table statistics for: value_types, report_statuses
2022-09-01T13:48:51.059Z INFO  [p.p.s.migrate] Locking migrations table before migrating
2022-09-01T13:48:51.079Z WARN  [p.p.s.migrate] DEPRECATED: The `pg_trgm` extension will be required in PDB 7.0.0
2022-09-01T13:48:51.079Z WARN  [p.p.s.migrate] PostgreSQL extension `pg_trgm` missing.  Unable to create the recommended pg_trgm indexes.
2022-09-01T13:48:51.101Z INFO  [p.p.s.migrate] Updating table statistics for: value_types, report_statuses

@csharpsteen, wonder if you know what this might be

Hey guys, I’ve upgrade the puppet agent from 7.4.0 to 7.18.0 and although I have also upgrade puppetdb-termini and puppetdb itself to version 7.11, the puppetdb logs are full of

1661972148606] [0 ms] 'replace catalog' command ignored (obsolete) for <HOST>
2022-09-01T14:03:06.397Z INFO  [p.p.command] [51312254-1661972150149] [0 ms] 'replace facts' command ignored (obsolete) for <HOST>

Any idea on what’s going on? I do see that version 80 of the migration succeeded (?):

2022-09-01T13:32:31.622Z INFO  [p.p.s.migrate] Locking migrations table before migrating
2022-09-01T13:32:31.647Z INFO  [p.p.s.migrate] Applying database migration version 80
2022-09-01T13:32:31.679Z INFO  [p.p.s.migrate] Applied database migration version 80 in 32 ms
2022-09-01T13:32:31.682Z WARN  [p.p.s.migrate] DEPRECATED: The `pg_trgm` extension will be required in PDB 7.0.0
2022-09-01T13:32:31.683Z WARN  [p.p.s.migrate] PostgreSQL extension `pg_trgm` missing.  Unable to create the recommended pg_trgm indexes.
2022-09-01T13:32:31.695Z INFO  [p.p.s.migrate] Updating table statistics for: value_types, report_statuses
2022-09-01T13:48:51.059Z INFO  [p.p.s.migrate] Locking migrations table before migrating
2022-09-01T13:48:51.079Z WARN  [p.p.s.migrate] DEPRECATED: The `pg_trgm` extension will be required in PDB 7.0.0
2022-09-01T13:48:51.079Z WARN  [p.p.s.migrate] PostgreSQL extension `pg_trgm` missing.  Unable to create the recommended pg_trgm indexes.
2022-09-01T13:48:51.101Z INFO  [p.p.s.migrate] Updating table statistics for: value_types, report_statuses

Hey guys, I’ve upgrade the puppet agent from 7.4.0 to 7.18.0 and although I have also upgrade puppetdb-termini and puppetdb itself to version 7.11, the puppetdb logs are full of

1661972148606] [0 ms] 'replace catalog' command ignored (obsolete) for <HOST>
2022-09-01T14:03:06.397Z INFO  [p.p.command] [51312254-1661972150149] [0 ms] 'replace facts' command ignored (obsolete) for <HOST>

Any idea on what’s going on? I do see that version 80 of the migration succeeded (?):

2022-09-01T13:32:31.622Z INFO  [p.p.s.migrate] Locking migrations table before migrating
2022-09-01T13:32:31.647Z INFO  [p.p.s.migrate] Applying database migration version 80
2022-09-01T13:32:31.679Z INFO  [p.p.s.migrate] Applied database migration version 80 in 32 ms
2022-09-01T13:32:31.682Z WARN  [p.p.s.migrate] DEPRECATED: The `pg_trgm` extension will be required in PDB 7.0.0
2022-09-01T13:32:31.683Z WARN  [p.p.s.migrate] PostgreSQL extension `pg_trgm` missing.  Unable to create the recommended pg_trgm indexes.
2022-09-01T13:32:31.695Z INFO  [p.p.s.migrate] Updating table statistics for: value_types, report_statuses
2022-09-01T13:48:51.059Z INFO  [p.p.s.migrate] Locking migrations table before migrating
2022-09-01T13:48:51.079Z WARN  [p.p.s.migrate] DEPRECATED: The `pg_trgm` extension will be required in PDB 7.0.0
2022-09-01T13:48:51.079Z WARN  [p.p.s.migrate] PostgreSQL extension `pg_trgm` missing.  Unable to create the recommended pg_trgm indexes.
2022-09-01T13:48:51.101Z INFO  [p.p.s.migrate] Updating table statistics for: value_types, report_statuses

@csharpsteen, wonder if you know what this might be

It looks that restarting the puppet servers solved the problem

I’m trying to get a PuppetDB 7 service up and running with a backend Postgresql 11 database on another node. The service connects to the database and then get stuck in a loop that seems to involve the schema_migrations table. The attached file shows the loop, which repeats every 10 to 15 seconds. How can I fix this?

I believe

(obsolete)

means that a newer catalog or factset was received while that one was sitting in the command queue waiting to be processed. Since PuppetDB only stores the latest factset or catalog, newer PuppetDB versions skip over updates that were obsoleted while waiting in the queue as an optimization.

The service restart fixing it indicates that old

puppetdb-termini

were likely still loaded. The

puppetdb-termini

package doesn't own the

puppetserver

service --- so you need to ensure the service is reloaded after upgrading that package or use

refresh => Service[puppetserver]

if managing it via Puppet.

This message was deleted.

@Todd Ervin has left the channel

so what many people do is: have one huge hash in a global.yaml:

data:
  dev:
    foo: 'bar'
  prd:
    foo: 'baz'
  stg:
    foo: 'foobar'

and in your $context.yaml you do something like

real_data: "%(lookup('data.$context'))"

Which OS version are you running Puppet Server on?

This message was deleted.

Hi Everyone, I have Puppet custom function written in Ruby (calling some rest APIs) that sometimes fail not sure why, is it network connection will check this part, now is there a way to have error exception basically when that function fail to continue with rest of Puppet plans/tasks? Now when this function fail complete Plan fail with error: Run failed Plan output

{
  "msg": "ManagedObjectNotFound: The object 'vim.Task:task-256811' has already been deleted or has not been completely created",
  "kind": "bolt/plan-failure",
  "details": {
    "class": "Bolt::PAL::PALError"
  }
}

I tried to do exception in Ruby code with begin rescue

Hi Everyone, I have Puppet custom function written in Ruby in Puppet plan(calling some rest APIs) that sometimes fail not sure why, is it network connection will check this part, now is there a way to have error exception basically when that function fail to continue with rest of Puppet plans/tasks? Now when this function fail complete Plan fail with error: Run failed Plan output

{
  "msg": "ManagedObjectNotFound: The object 'vim.Task:task-256811' has already been deleted or has not been completely created",
  "kind": "bolt/plan-failure",
  "details": {
    "class": "Bolt::PAL::PALError"
  }
}

I tried to do exception in Ruby code with begin rescue => err raise ".... #{err}" end But as said it is hard to catch error because it is randomly happening, 1 time in 10 tries. Thanks

This message was deleted.

message has been deleted

message has been deleted

message has been deleted

For example:

$try_switch_distro = run_task('debian_upgrades::switch_to_new_distro', $valid_target,
      'distro'         => $distro,
      'kernel_version' => $kernel_version,
      'user'           => $user,
      '_catch_errors'  => true
    )

    $plan_result = run_plan('reboot', $try_switch_distro.ok_set.targets, {
      reconnect_timeout => 600,
      _catch_errors => true,
      fail_plan_on_errors => false,
    })

if you check on the puppetserver if this environment was deployed and if it contains your class?

did you check on the puppetserver if this environment was deployed and if it contains your class?

[root@li-prod-pe1 puppetlabs]# find / -name site-modules ... _*/etc/puppetlabs/code/environments/bragor_skolv_checktools/site-modules*_

hey @Goran Brannstrom I've experienced this issue before typically where there is some syntaxing / parsing issue with the class it won't show up in PE. Using PDK https://puppet.com/docs/pdk/2.x/pdk_overview.html is generally best to make sure modules are clean. For the second issue I would try a refresh of classes using the example command at https://puppet.com/docs/pe/2021.1/update_classes_endpoint.html on your primary puppet server

cert="$(puppet config print hostcert)"
cacert="$(puppet config print localcacert)"
key="$(puppet config print hostprivkey)"
uri="https://$(puppet config print server):4433/classifier-api/v1/update-classes?environment=production"

curl --cert "$cert" --cacert "$cacert" --key "$key" --request POST "$uri"

This message was deleted.

See the

puppetlabs-apache

module at https://forge.puppet.com/puppetlabs/apache?src=slack&channel=puppet

This message was deleted.