Bug 1265742 - Puppet agent on Sat6 always gives warning
Puppet agent on Sat6 always gives warning
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management (Show other bugs)
6.1.2
Unspecified Unspecified
unspecified Severity low (vote)
: GA
: --
Assigned To: Marek Hulan
aruzicka
http://projects.theforeman.org/issues...
: Triaged
Depends On:
Blocks: 1122832
  Show dependency treegraph
 
Reported: 2015-09-23 12:04 EDT by Peter Vreman
Modified: 2016-07-27 05:19 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-27 05:19:21 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 1314253 None None None 2016-03-07 07:48 EST
Foreman Issue Tracker 14075 None None None 2016-04-26 13:08 EDT

  None (edit)
Description Peter Vreman 2015-09-23 12:04:20 EDT
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.

# 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:
Comment 2 Marek Hulan 2016-03-07 07:19:02 EST
Created redmine issue http://projects.theforeman.org/issues/14075 from this bug
Comment 3 Marek Hulan 2016-03-07 07:23:11 EST
Capsule module does not expose additional settings option of puppet module to users. But since puppet version is under installer control we can enforce this quite safely.
Comment 4 Bryan Kearney 2016-03-07 08:07:55 EST
Upstream bug component is Content Management
Comment 5 Bryan Kearney 2016-03-08 14:07:17 EST
Moving to POST since upstream bug http://projects.theforeman.org/issues/14075 has been closed
-------------
Marek Hulán
I don't have permissions to update the category and the PR (which does not seem to be linked), could someone pls move it to Ready for testing and add link to https://github.com/Katello/puppet-capsule/pull/75
-------------
Anonymous
Applied in changeset commit:puppet-capsule|cb5577a2cecd51cccfda238cb2db8fd542afdf36.
Comment 7 aruzicka 2016-06-13 07:51:26 EDT
VERIFIED.
@Sat6.2.0-Snap15.2

Followed steps to reproduce from #0, no warnings shown, /etc/puppet/puppet.conf contains
disable_warnings = deprecations
Comment 9 errata-xmlrpc 2016-07-27 05:19:21 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501

Note You need to log in before you can comment on or make changes to this bug.