Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-14266

TargetIP being ignored and assumed to be same as engine IP's.


    • Type: Bug
    • Status: Resolved
    • Priority: Not specified
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.0.0
    • Component/s: Regression Test Engine
    • Labels:


      Some tests (soapcall_multihttpheader.ecl and httpcall_multiheader.ecl) need to know the name of the soap service they talk to (Esp in this case).

      This is achieved via a stored parameter that can be set at runtime.

      Most store variables are configurable via the ecl-test command line, or on a per query basis, or globally in ecl-test.jscon.

      However TargetIP is automagically configured based on the ip of the target engine in the "IpAddress" in ecl-test.json.

      This is incorrect, the engines are not normally on the same box as the service (e.g. esp)

      Any TargetIP setting on a per query basis is ignored as is a definition on the command line.

      As far as I can see TargetIP should be treated like any other parameter (it should not vary per engine as it currently does).
      ecl-test does not need to define it in a vanilla installation in a box setup, the query default is correct in that case.
      In a multi-node cluster, it will need setting up correctly in ecl-test.json.




            • Assignee:
              attilavamos Attila Vamos
              jakesmith Jake Smith
            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created: