Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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

This was fixed in Satellite 6.1 - we just need to move to a more recent compose to see the fix.