Give mailman3 more fedmsg endpoints.

inventory/group_vars/mailman

@@ -6,7 +6,11 @@ num_cpus: 4
 # for systems that do not match the above - specify the same parameter in
 # the host_vars/$hostname file
 
-tcp_ports: [ 25, 80, 443, 3000, 3001 ]
+tcp_ports: [
+    25, 80, 443,
+    # For outgoing fedmsg
+    3000, 3001, 3002, 3003,
+]
 
 fas_client_groups: sysadmin-tools,sysadmin-main
 

inventory/group_vars/mailman-stg

@@ -6,7 +6,11 @@ num_cpus: 2
 # for systems that do not match the above - specify the same parameter in
 # the host_vars/$hostname file
 
-tcp_ports: [ 25, 80, 443, 3000, 3001 ]
+tcp_ports: [
+    25, 80, 443,
+    # For outbound fedmsg
+    3000, 3001, 3002, 3003,
+]
 fas_client_groups: sysadmin-tools,sysadmin-main
 
 # These are consumed by a task in roles/fedmsg/base/main.yml

roles/fedmsg/base/templates/endpoints-mailman.py.j2

@@ -11,6 +11,17 @@ config = dict(
         "mailman.mailman01": [
             "tcp://mailman01.%s:3000" % suffix,
             "tcp://mailman01.%s:3001" % suffix,
+
+            # On Nov 19th, we started getting tracebacks that mailman3 had run
+            # out of endpoints.  We're not sure what changed that required
+            # additional entries here, but we're adding them to try and make the
+            # error go away.
+            # One idea is that the mailman REST server grew the ability to list
+            # the archivers.  Postorius calls that, and it (under the hood)
+            # tries to initialize all the archivers, which would inadvertently
+            # try to force our fedmsg plugin to establish a socket.
+            "tcp://mailman01.%s:3002" % suffix,
+            "tcp://mailman01.%s:3003" % suffix,
         ],
     },
 )