Project

General

Profile

Actions

Bug #14075

closed

Puppet agent on Sat6 always gives warning

Added by Marek Hulán almost 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1265742
Description of problem:
A puppet agent run on the Satellite 6 server itself always gives an depreciation warning. The recommended way by puppet to turn the warning off is not possible as there is no global site.pp that is being managed.

  1. puppet agent -t -v --noop
    Info: Retrieving plugin
    Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
    Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
    Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
    Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
    Info: Caching catalog for li-lc-1578.hag.hilti.com
    Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
    (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
    Info: Applying configuration version '1443023866'

The only fix is to include the following entry in the /etc/puppet/puppet.conf
disable_warnings = deprecations

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Create ContentView A
2. Add couple of puppet modules to ContentView A
3. Publish ContentView A
4. Assign Satellite Server to ContentView A
5. Run puppet agent -t -v on the Satellite server itself

Actual results:
The warning about allow_virtual is displayed.
The warning is also visible in the Host reports in the UI

Expected results:
No warning is generated by puppet

Additional info:

Actions

Also available in: Atom PDF