Provider silently re-registers

[jeffmccune]

The rhnreg_ks type's force_check parameter behaves unexpectedly. If the registration URL changes, the registration results in no messages and no changes showing up in the report even though the system is re-registered. The behavior I and my large enterprise client expects is the re-registration change shows up in the Puppet report.

The reason for this unexpected behavior is that the registration happens as part of the exists? method, here:

puppet-rhnreg_ks/lib/puppet/provider/rhn_register/rhnreg_ks.rb

Line 72 in 3a413aa

register

The expected behavior is that the resource is flagged as out-of-sync and the registration happens as part of the normal provider property management.