Poll binds to wrong exchange in v3.01

[andreleblanc11]

We've installed v3.01.00 on the DDSR operational nodes this week and we've noticed a new problem in poll configs. The binding to the queue are now being set wrong.

This is one of the configurations where we've noticed the problem.

# The config : poll/airnow_http_poll.conf

  vip my-vip
  
  post_broker amqp://AIRNOW@my-broker/
  post_exchange xs_AIRNOW_http_poll
  
  queueName q_${POST_BROKER_USER}_${PROGRAM}.${CONFIG}.${HOSTNAME}
  
  fileEvents +create,modify
  # Download station files to user_cache directory
  # PROBLEM: unknown do_poll poll_airnow_http, manual conversion required.
  callback poll.airnow
  
  nodupe_fileAgeMax 6h
  nodupe_ttl        7h
  
  #destination http://files.airnowtech.org/?prefix=airnow/today/
  pollUrl https://s3-us-west-1.amazonaws.com//files.airnowtech.org/airnow/today
  source AIRNOW
  
  # ACDC 22203 , ANL - Increase sleep time as we're getting max retry errors
  scheduled_interval 900
  
  #to DDSR.CMC,DDI.CMC,DDSR.SCIENCE,DDI.SCIENCE
  
  logLevel debug
  accept .*.dat
  acceptUnmatched False

# When we look at the `subscriptions.json` file, it shows the wrong exchange being a part of the subscriptions.

  [
      {
          "baseDir": null,
          "bindings": [
              {
                  "exchange": "xs_AIRNOW",
                  "prefix": [
                      "v02",
                      "post"
                  ],
                  "sub": [
                      "#"
                  ]
              }
          ],
          "broker": "amqp://AIRNOW@my-broker",
          "queue": {
              "auto_delete": false,
              "bind": true,
              "cleanup_needed": null,
              "declare": true,
              "durable": true,
              "expire": 604800.0,
              "name": "q_AIRNOW_poll.airnow_http_poll.my-server",
              "prefetch": 25,
              "template": "q_${POST_BROKER_USER}_${PROGRAM}.${CONFIG}.${HOSTNAME}",
              "tlsRigour": "normal"
          }
      }
  ]

# The exchange should be xs_AIRNOW_http_poll and not xs_AIRNOW

We know this is related to the release of v3.01.00 of sr3, because the DDSR nodes that had the new version of sr3 were getting assigned the wrong exchanges when sr3 came back up.

Work around

Adding exchange my-exchange to the poll config works around the issue.
We're applying this patch on all of the operational DDSR polls.