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.
Superficially similar to #5792, but we are running Foreman and proxy at 1.5.0.
Clicking 'import classes from puppetmaster' or 'import environments from puppetmaster' results in the 406 error, and the foreman proxy logs show:
<pre>
I, [2014-05-21T11:41:30.462997 #20033] INFO -- : Initializing from Puppet config file: /etc/puppet/puppet.conf
I, [2014-05-21T11:41:30.590418 #20033] INFO -- : Initializing from Puppet config file: /etc/puppet/puppet.conf
I, [2014-05-21T11:41:30.720226 #20033] INFO -- : Initializing from Puppet config file: /etc/puppet/puppet.conf
I, [2014-05-21T11:41:30.785593 #20033] INFO -- : Initializing from Puppet config file: /etc/puppet/puppet.conf
E, [2014-05-21T11:41:30.892108 #20033] ERROR -- : Failed to show puppet classes: no 'environments' in {:root_environment=>#<Puppet::Node::Environment:0x7f4427990d28 @config_version=nil, @name=:"*root*", @manifest="/etc/foreman-proxy", @modulepath=[], @watching=true>, :current_environment=>#<Puppet::Node::Environment:0x7f4427990d28 @config_version=nil, @name=:"*root*", @manifest="/etc/foreman-proxy", @modulepath=[], @watching=true>} at top of []
# rpm -qa \*foreman\*
foreman-compute-1.5.0-1.el6.noarch
foreman-proxy-1.5.0-1.el6.noarch
foreman-release-1.5.0-1.el6.noarch
foreman-postgresql-1.5.0-1.el6.noarch
rubygem-foreman_api-0.1.11-1.el6.noarch
foreman-selinux-1.5.0-1.el6.noarch
foreman-vmware-1.5.0-1.el6.noarch
foreman-installer-1.5.0-1.el6.noarch
rubygem-hammer_cli_foreman-0.1.0-1.el6.noarch
foreman-1.5.0-1.el6.noarch
# rpm -qa \*puppet\*
puppet-3.6.0-1.el6.noarch
mcollective-puppet-common-1.7.2-1.el6.noarch
mcollective-puppet-client-1.7.2-1.el6.noarch
puppetlabs-release-6-10.noarch
mcollective-puppet-agent-1.7.2-1.el6.noarch
puppetdb-2.0.0-1.el6.noarch
puppet-server-3.6.0-1.el6.noarch
puppetdb-terminus-2.0.0-1.el6.noarch
ruby193-puppet-3.1.1-6.el6.noarch
</pre>
To verify:
1. Check puppet and puppet-server are 3.6.0 or higher
2. Upload a Puppet module into a Puppet repo, add to a content view and publish the first version
3. Configure > Puppet classes, check that the module is now listed
Superficially similar to #5792, but we are running Foreman and proxy at 1.5.0. Clicking 'import classes from puppetmaster' or 'import environments from puppetmaster' results in the 406 error, and the foreman proxy logs show: <pre> I, [2014-05-21T11:41:30.462997 #20033] INFO -- : Initializing from Puppet config file: /etc/puppet/puppet.conf I, [2014-05-21T11:41:30.590418 #20033] INFO -- : Initializing from Puppet config file: /etc/puppet/puppet.conf I, [2014-05-21T11:41:30.720226 #20033] INFO -- : Initializing from Puppet config file: /etc/puppet/puppet.conf I, [2014-05-21T11:41:30.785593 #20033] INFO -- : Initializing from Puppet config file: /etc/puppet/puppet.conf E, [2014-05-21T11:41:30.892108 #20033] ERROR -- : Failed to show puppet classes: no 'environments' in {:root_environment=>#<Puppet::Node::Environment:0x7f4427990d28 @config_version=nil, @name=:"*root*", @manifest="/etc/foreman-proxy", @modulepath=[], @watching=true>, :current_environment=>#<Puppet::Node::Environment:0x7f4427990d28 @config_version=nil, @name=:"*root*", @manifest="/etc/foreman-proxy", @modulepath=[], @watching=true>} at top of [] # rpm -qa \*foreman\* foreman-compute-1.5.0-1.el6.noarch foreman-proxy-1.5.0-1.el6.noarch foreman-release-1.5.0-1.el6.noarch foreman-postgresql-1.5.0-1.el6.noarch rubygem-foreman_api-0.1.11-1.el6.noarch foreman-selinux-1.5.0-1.el6.noarch foreman-vmware-1.5.0-1.el6.noarch foreman-installer-1.5.0-1.el6.noarch rubygem-hammer_cli_foreman-0.1.0-1.el6.noarch foreman-1.5.0-1.el6.noarch # rpm -qa \*puppet\* puppet-3.6.0-1.el6.noarch mcollective-puppet-common-1.7.2-1.el6.noarch mcollective-puppet-client-1.7.2-1.el6.noarch puppetlabs-release-6-10.noarch mcollective-puppet-agent-1.7.2-1.el6.noarch puppetdb-2.0.0-1.el6.noarch puppet-server-3.6.0-1.el6.noarch puppetdb-terminus-2.0.0-1.el6.noarch ruby193-puppet-3.1.1-6.el6.noarch </pre>