Use the fedmsg vars I setup for this instead of trying to overwrite them with a file.

inventory/group_vars/resultsdb-prod

@@ -39,6 +39,9 @@ external_hostname: taskotron.fedoraproject.org
 allowed_hosts:
     - 10.5.124
 
+fedmsg_active: True
+fedmsg_cert_prefix: resultsdb
+
 fedmsg_certs:
 - service: shell
   owner: root

inventory/group_vars/resultsdb-stg

@@ -53,6 +53,9 @@ execdb_secret_key: "{{ stg_execdb_secret_key }}"
 # fedmsg details
 ############################################################
 
+fedmsg_active: True
+fedmsg_cert_prefix: resultsdb
+
 fedmsg_certs:
 - service: shell
   owner: root

roles/taskotron/resultsdb-fedmsg/files/resultsdb.py

@@ -1,10 +0,0 @@
-config = {
-    # This should switch fedmsg from passive mode to active mode
-    # which instructs it to connect out to the fedmsg-relay instance described
-    # in /etc/fedmsg.d/relay.py instead of binding to ports and waiting for
-    # listeners.  We need this so that we can push our messages on to the
-    # fedora-infra proper bus from over in the QA network.
-    'active': True,
-    'name': 'relay_inbound',
-    'cert_prefix': 'resultsdb',
-}

roles/taskotron/resultsdb-fedmsg/tasks/main.yml

@@ -1,6 +1,2 @@
-- copy: src=resultsdb.py dest=/etc/fedmsg.d/resultsdb.py
-  notify:
-    - restart httpd
-
 - name: ensure selinux lets httpd talk to the fedmsg-relay
   seboolean: name=httpd_can_network_connect persistent=yes state=yes