Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-1134

Consul DNS issues on Beijing release

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Medium Medium
    • None
    • Beijing Release
    • None
    • None

      Some Consul healthchecks are failing on a Beijing deploy from latest sources (using http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_quickstart_guide.html#quick-start-label).  Deploy is done in AWS, and the instances have enough resources for a full ONAP deploy.

      Consul tries to reach "aai-elasticsearch" with a GET command to check its health, but cannot reach it using its hostname. However, it is reachable using its IP (see attached pics). In total 4 healtchecks are failing because of this DNS issue (sdnhost, appc-sdnhost, aai-elasticsearch and framework are not reachable by their hostnames). 

       

      Thank you

        1. aai_elastic_search__no_dns_entry.JPG
          aai_elastic_search__no_dns_entry.JPG
          96 kB
        2. consul_curl_to_elasticsearch.JPG
          consul_curl_to_elasticsearch.JPG
          38 kB
        3. consul_nslookup.JPG
          consul_nslookup.JPG
          80 kB
        4. consul_ping_to_elasticsearch.JPG
          consul_ping_to_elasticsearch.JPG
          56 kB
        5. consul.log
          3.13 MB
        6. jira_consul_dns_error.JPG
          jira_consul_dns_error.JPG
          32 kB

            Unassigned Unassigned
            aeg aeg
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: