Bug 1213880 - config_version deprecation warning when running puppet
Summary: config_version deprecation warning when running puppet
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: rhci-common-installer
TreeView+ depends on / blocked
 
Reported: 2015-04-21 13:28 UTC by Jason Montleon
Modified: 2017-02-23 20:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-15 16:35:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jason Montleon 2015-04-21 13:28:01 UTC
Description of problem:
Warning: Setting config_version is deprecated in puppet.conf. See
http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/share/ruby/vendor_ruby/puppet/settings.rb:1095:in `block in
   issue_deprecations')

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

How reproducible:
Always, every puppet run

Actual results:
Get deprecation warning on puppet runs

Expected results:
no deprecation warnings

Additional info:
https://github.com/theforeman/puppet-puppet/commit/97b6a6f1bd0e18c19fe52a92232914debafbb4ef is supposed to fix this

It looks like it was pulled into katello-installer in https://github.com/Katello/katello-installer/commit/d8081a28d3b23f7a6156993113d4b0bbefb90edb

Comment 2 Brad Buckingham 2015-04-24 11:42:55 UTC
I ran a katello-installer test and did not observe the warning message.  In the scenario above, was it katello-installer or fusor-installer that was run?  

It may be that the warning only occurs when running katello installer through fusor.


Packages

   katello-installer-2.3.5-1.el7sat.noarch
   ruby193-rubygem-katello-2.2.0.35-1.el7sat.noarch

katello-installer output:

  Success!
  * Katello is running at https://sat61.test
      Initial credentials are admin / BDrHwFiPD4A8SiAW
  * Capsule is running at https://sat61.test:9090
  * To install additional capsule on separate machine continue by running:"

      capsule-certs-generate --capsule-fqdn "$CAPSULE" --certs-tar "~/$CAPSULE-certs.tar"

  The full log is at /var/log/katello-installer/katello-installer.log

Comment 3 Jason Montleon 2015-06-05 19:07:49 UTC
This was fixed in Satellite 6.1 - we just need to move to a more recent compose to see the fix.


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