hashi-ui

hashi-ui copied to clipboard

Hey jippi,

We've noticed that sometimes (and unpredictably), a Nomad job that registers with Consul won't get a checkmark in the "Consul" column on the allocations view. Instead, the column is blank.

The problem is that I haven't been able to reproduce it (one version of a Nomad job will show the checkmark for all allocations, the next version of the job won't, the next will...).

One interesting thing about at least one of the jobs is that it has two service entries, only one of which has a check:

    task "notification-scheduling-service" {
      driver = "docker"

      config {
        image = "pagerduty-docker.jfrog.io/notification_scheduling_service:[[.DEPLOY_SUB___VERSION]]"

        port_map {
          http      = 4300,
          admin_ui  = 8090
        }
      }

      service {
        name = "notification-scheduling-service"
        tags = [ "lt-notification-scheduling-service" ]
        port = "http"

        check {
          type      = "http"
          port      = "http"
          protocol  = "http"
          path      = "/health"
          interval  = "10s"
          timeout   = "5s"
        }
      }

      # Separate service stanza for the Admin UI
      service {
        name = "notification-scheduling-service-admin"
        tags = [ "load-test" ]
        port = "admin_ui"
      }
      [...]
    }

but at this point I'm not sure if that's relevant or not.

We're running hashi-ui 0.26.1 against Nomad 0.8.4 and Consul 0.7.5.

How should I go about troubleshooting this?

Nomad changes how these checks are computed, making it really hard to match the logic outside the nomad core - its a known issue that my implementation is not 100% reliable in finding the service ids :(

@jippi With nomad 0.9 we can relook at it?