[DISPATCH-910] Inter-router connections with dir 'in' have no host name

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.1.0
• Component/s: Management Agent
• Assignee: Ganesh Murthy
• Reporter: Ernest Allen
• Created: 12/Jan/18 20:03
• Updated: 11/Jun/18 19:25
• Resolved: 24/Jan/18 21:33

Description

There is no host name reported for inter-router connections with dir of 'in'

• start a 2 or more router network
  router { mode: interior id: A }

  listener

  { host: 0.0.0.0 saslMechanisms: ANONYMOUS port: 5672 }

1. listener for connectors from B
   listener { host: 0.0.0.0 role: inter-router saslMechanisms: ANONYMOUS port: 2000 }

   -----------
   router

   { mode: interior id: B }

   listener

   { host: 0.0.0.0 saslMechanisms: ANONYMOUS port: 22001 }

1. connect to A
   connector { host: 0.0.0.0 role: inter-router saslMechanisms: ANONYMOUS port: 2000 }

• qdstat -c
  $ qdstat -c
  Connections
  id host container role dir security authentication tenant
  =======================================================================
  1 B inter-router in no-security anonymous-user
  2 175fa6eb-b616-4c1c-9af9-a8ac121d76a0 normal in no-security no-auth

Connection #2 is from qdstat.
Connection 1 is from Router B. The host should not be blank, but it is.

The host is correct for dir 'out' connections.
$ qdstat -b 0.0.0.0:22001 -c
Connections
id host container role dir security authentication tenant
======================================================================
1 0.0.0.0:2000 A inter-router out no-security anonymous-user
2 a5c4c524-53de-4b4f-896e-1bf15c30f993 normal in no-security no-auth

Issue Links

• relates to: DISPATCH-912 system_tests_user_id_proxy and system_tests_policy failing