Project

General

Profile

Actions

Bug #7935

open

Foreman seems to always re-import some classes

Added by Anthony Lapenna over 9 years ago. Updated over 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Puppet integration
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

It seems that Foreman detects changes on some Puppet classes even if there was no change since the last import.

For an example: try to use the module puppetlabs/apt from the Puppet Forge.

I'm using the Foreman API to import my modules and for every import I see the following output:

{
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:04 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:05 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:06 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:07 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:08 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:09 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:10 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:11 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:12 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:13 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:14 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:15 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:16 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:17 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:18 --:--:--     0100   564    0   564    0     0     29      0 --:--:--  0:00:18 --:--:--   116100   564    0   564    0     0     29      0 --:--:--  0:00:18 --:--:--   146
  "message": "Successfully updated environment and puppetclasses from the on-disk puppet installation",
  "environments_with_new_puppetclasses": 0,
  "environments_updated_puppetclasses": 3,
  "environments_obsolete": 0,
  "results": [{"actions":["updated"],"updated_puppetclasses":["nfs::client"],"name":"development"},{"actions":["updated"],"updated_puppetclasses":["apt::unattended_upgrades","apt::backports"],"name":"production"},{"actions":["updated"],"updated_puppetclasses":["apt::unattended_upgrades","apt::backports"],"name":"staging"}]
}

As you can see, for every import triggered, the classes apt::backports and apt::unattended_upgrades are always reimported.

Actions #1

Updated by Anthony Lapenna over 9 years ago

Note: I've been looking at the Audit section in Foreman and seen the following:

Smart Variable
Il y a 7 minutes
 api (IP) updated Smart Variable: apt::unattended_upgrades::origins / apt::unattended_upgrades

Smart Variable
Il y a 7 minutes
 api (IP) updated Smart Variable: apt::backports::location / apt::backports

 Smart Variable
Il y a 7 minutes
 api (IP) updated Smart Variable: nfs::client::package_ensure / nfs::client

And if I check the change for example of apt::backports::location / apt::backports:

Item    Old    New
Default value    ${$apt::params::backports_location}    ${$::apt::params::backports_location}
Actions

Also available in: Atom PDF