Description of problem:
I'm unable to find a proper reproducer, but this occurs quite often in our automation:

#on a host:
subscription-manager register --org AIQhkL --activationkey rIHOo7GNHP --force
ERROR:  current transaction is aborted, commands ignored until end of transaction block

foreman production log reveals the problematic statement:

2017-01-06 16:44:17 [foreman-tasks/action] [E] PG::Error: ERROR:  current transaction is aborted, commands ignored until end of transaction block
 | : SELECT  "fact_names".* FROM "fact_names"  WHERE "fact_names"."type" IN ('Katello::RhsmFactName') AND "fact_names"."name" = 'dmi'  ORDER BY fact_names.name LIMIT 1 (ActiveRecord::StatementInvalid)
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `exec'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `block in exec_no_cache'
...
(will attach the foreman-debug logs)

Version-Release number of selected component (if applicable):
sat6.2.7 snap#1

How reproducible:
not clear but happens during host registration

Actual results:
SELECT  "fact_names".* FROM "fact_names"  WHERE "fact_names"."type" IN ('Katello::RhsmFactName') AND "fact_names"."name" = 'dmi'  ORDER BY fact_names.name LIMIT 1 (ActiveRecord::StatementInvalid)

Expected results:
registration just works