You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My organization has been using this module for several years. Thank you for it.
We have observed that when host registration fails, the rhsm_register resource returns successfully. This can cause problems for other resources that depend on our rhsm_register resource, and it is confusing trying to identify where the problem is when reading Puppet reports.
For example, if we provide a fake activation key, on the command line we get:
The command returns unusual return values so a blanket catch was used.
On some of the older branches there are some attempts to process these return codes but they never resulted in workable solutions in the field.
If you have a working implemtnation of handling the return data from subscription-manager, please do submit a patch. I would be very interested in testing it.
My organization has been using this module for several years. Thank you for it.
We have observed that when host registration fails, the
rhsm_register
resource returns successfully. This can cause problems for other resources that depend on ourrhsm_register
resource, and it is confusing trying to identify where the problem is when reading Puppet reports.For example, if we provide a fake activation key, on the command line we get:
And providing the same fake activation key to the
rhsm_resource
, we get:When turning on the
--debug
option, we see the detailed error message, but the resource is still considered to have returned successfully:I believe this is because the
subscription-manager
command failure is caught and not re-raised at https://github.com/waveclaw/puppet-subscription_manager/blob/master/lib/puppet/provider/rhsm_register/subscription_manager.rb#L55. Is there a reason for this? I'm happy to submit a patch if this is something that should be corrected.Thanks.
The text was updated successfully, but these errors were encountered: