Description of problem: Currently clean_backend_objects removes Content Hosts that miss either pulp or candlepin counterpart. There are cases when the opposite is required, i.e. when pulp or candlepin consumer exists for non-existing Content Host. We shall have a mechanism to remove such pulp/candlepin consumers to make those DBs aligned with foreman (Content) Hosts db. It can be achieved either by extending clean_backend_objects script (preffered from user-point of view, could be problematic due to current implementation), or implementing a new one. Version-Release number of selected component (if applicable): tfm-rubygem-katello-3.0.0.144-1.el7sat.noarch How reproducible: 100% Steps to Reproduce: 1. Have some pulp or candlepin consumer without associated Content Host (i.e. (re)create a pulp/candlepin consumer manually, e.g. by 1) registering a host, 2) taking pulp and candlepin DB backups, 3) unregistering the host, 4) reverting pulp/candlepin DBs prior unregister) 2. foreman-rake katello:clean_backend_objects 3. Check if pulp/candlepin consumers match the foreman Content Hosts Actual results: extra pulp/candlepin consumer exists Expected results: no such orphaned consumer present Additional info:
Just pulp consumers can be orphaned, since Katello::Candlepin::Consumer.orphaned_consumer_ids finds the "in candlepin but not in katello" hosts and the rake script cleans them properly. The pitty is this method uses ::Katello::Resources::Candlepin::Consumer.get({}) that has no equivalent for pulp, to enhance the rake script easily.
Created redmine issue http://projects.theforeman.org/issues/21053 from this bug
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.