Description of problem: Ansible inventory script/Ansible Tower is getting an HTTP 500 error when attempting to synchronize inventory with Red Hat Satellite 6.6. Without filters we are able to sync the inventory without any issue. Satellite role/Filter:- ----|---------------|------------------------------------------------------------|------------|-----------|-------|---------------- ID | RESOURCE TYPE | SEARCH | UNLIMITED? | OVERRIDE? | ROLE | PERMISSIONS ----|---------------|------------------------------------------------------------|------------|-----------|-------|---------------- 301 | Host | registered_at > "200 minutes ago" and installed_at = Today | no | no | tower | view_hosts 302 | Hostgroup | none | no | no | tower | view_hostgroups 303 | FactValue | none | no | no | tower | view_facts ----|---------------|------------------------------------------------------------|------------|-----------|-------|---------------- Error:- 2019-11-13T18:19:53 [W|app|838e3f9c] Action failed 2019-11-13T18:19:53 [D|app|838e3f9c] Backtrace for 'Action failed' error (ActiveRecord::ConfigurationError): Can't join 'Host::Base' to association named 'subscription_facet'; perhaps you misspelled it? /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/associations/join_dependency.rb:188:in `find_reflection' /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/associations/join_dependency.rb:193:in `block in build' /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/associations/join_dependency.rb:192:in `each' /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/associations/join_dependency.rb:192:in `map' /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/associations/join_dependency.rb:192:in `build' /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/associations/join_dependency.rb:201:in `block in build' /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/associations/join_dependency.rb:192:in `each' /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/associations/join_dependency.rb:192:in `map' /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/associations/join_dependency.rb:192:in `build' /opt/theforeman/tfm-ror52/root/usr/share/gems/gems/activerecord-5.2.1/lib/active_record/associations/join_dependency.rb:72:in `initialize' Version-Release number of selected component (if applicable): Satellite 6.6 How reproducible: Steps to Reproduce: 1. Create the role/filters as mentioned above. 2. Create a ansible user and associate the role. 3. Provision a new host then check whether you are able to list using ansible inventory script or tower. Curl command is also failing with 500 error:- # curl -k -v -u ansible:redhat -H "Content-Type: application/json" https://satellite/api/v2/hosts/12/facts?per_page=250&page=1 Output:- { "error": {"message":"Can't join 'Host::Base' to association named 'subscription_facet'; perhaps you misspelled it?"} } Actual results: Getting below error:- error": {"message":"Can't join 'Host::Base' to association named 'subscription_facet'; perhaps you misspelled it?"} Expected results: We should be able to sync the inventory without any issue. Additional info:
This seems as something wrong in the database, instances of Host::Base shouldn't exist. Could you please try to verify, what does the following query return on production database? SELECT "hosts".* FROM "hosts" WHERE (type = 'Host::Base') or if that's easier, run foreman-rake console and execute Host::Base.where "type = 'Host::Base'" the upload the result here please.
Upstream bug assigned to oezr
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30555 has been resolved.
Fix is in Satellite 6.9 SNAP 1 with foreman-2.3.0-0.7.rc1.el7sat.noarch
After discussion with developer we decided to put this to FailedQA. I was able to reproduce the problem with 6.8.5 snap 1. New role with filter on host view (with enough permissions to run ansible playbook), new user with assigned role, content host was registered by admin, Ansible playbook was ran from new user on new host. (no ansible tower was used) Did the same steps with 6.9 snap 17. New user no longer sees the error in 6.9, but is also unable to read facts, so the problem persist.