Closed pgassmann closed 8 years ago
Seems to be related to #23 as it also uses the File.exists confine and even though the file does not exist, the fact is executed.
But the backtrace method error is something else to fix.
This is a trace of the application of subscription_manager. It appears to be trying to install the katello consumer CA package needed to replace the redhat-uep.pem file in /etc/rhsm/ca.
That redhat-uep file is provided by the python-rhsm package which is part of the subscription-manager plugin from RedHat.
[root@katello ~]# rpm -q --whatprovides /etc/rhsm/ca/redhat-uep.pem
python-rhsm-1.15.4-5.el7.x86_64
The error you list is from the package provider for your system trying to install Satellite or Katello's replacement package for this certificate. The path is very simple to follow:
Error: /Stage[main]/Subscription_manager::Install/Package[katello-ca-consumer-mysatellite.example.com]/ensure: change from absent to latest failed: Could not update: undefined method
backtrace' for Puppet::Error:Class``
If this is a problem with the package provider in your Puppet environment I cannot help you by changing code in subscription_manager.
The only place in subscription_manager that calls backtrace is the duplicated begin..end statements in the facts that were donated. (Those still need a refactor but I hate making Ruby code obtuse just to reduce repeating code. There's already far too much meta-for-the-sake-of-meta in Puppet's code base.)
The subscription_manager module uses strict ordered dependencies between the top-level classes. This error appears inside the install class. Since Puppet later versions have working containment this should not be causing any resource or class to float off the graph. But that does not completely preclude a random class sneaking into the order after the package ensure failure. But this install class uses Puppet transition which alters the catalog non-trivially.
Still, just in case this might be caused by something floating about the catalog, what does the dependency graph for a minimal catalog with this issue look like?
Now in the use case where
In this example, are you trying to re-subscribe a system with a registration?
I created an upstream Ticket for the Bug: https://tickets.puppetlabs.com/browse/PUP-6517
Ouch, DNS resolver bug?
There's a couple weird errors Puppet will generate if DNS is not working as expected. Puppet 4 dies in collecting facter facts with an error on 'Cannot resolve master' if the local system's hostname is not resovable from /etc/hosts, DNS or something else like NIS+.
I hope your issue gets visibility.
The file that is checked in the fact does not exist