This project is mirrored from https://gitee.com/mirrors/nomad.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 06 Nov, 2021 1 commit
  2. 29 Oct, 2021 3 commits
  3. 28 Oct, 2021 1 commit
  4. 27 Oct, 2021 9 commits
    • Dave May's avatar
      debug: update default node-id and docs (#11398) · f46b97b2
      Dave May authored
      * debug: default node-id to all
      * debug: align cli help and website documentation
      f46b97b2
    • Mahmood Ali's avatar
      logging: Log the cause behind agent startup failure (#11353) · 3ce89b75
      Mahmood Ali authored
      Log the failure error when the agent fails to start. Previously, the
      agent startup failure error would be emitted to the command UI but not
      logged. So it doesn't get emitted to syslog or `log_file` if they are
      set, and it makes debugging much harder. Also, logging the error again
      before exit makes the error more visible: previously, the operator
      needed to scroll to the top to find the error.
      
      On a sample failure, the output will look like:
      ```
      ==> WARNING: Bootstrap mode enabled! Potentially unsafe operation.
      ==> Loaded configuration from sample-configs/config-bad
      ==> Starting Nomad agent...
      ==> Error starting agent: setting up server node ID failed: mkdir /path-without-permission: read-only file system
          2021-10-20T14:38:51.179-0400 [WARN]  agent.plugin_loader: skipping external plugins since plugin_dir doesn't exist: plugin_dir=/path-without-permission/plugins
          2021-10-20T14:38:51.181-0400 [DEBUG] agent.plugin_loader.docker: using client connection initialized from environment: plugin_dir=/path-without-permission/plugins
          2021-10-20T14:38:51.181-0400 [DEBUG] agent.plugin_loader.docker: using client connection initialized from environment: plugin_dir=/path-without-permission/plugins
          2021-10-20T14:38:51.181-0400 [INFO]  agent: detected plugin: name=java type=driver plugin_version=0.1.0
          2021-10-20T14:38:51.181-0400 [INFO]  agent: detected plugin: name=docker type=driver plugin_version=0.1.0
          2021-10-20T14:38:51.181-0400 [INFO]  agent: detected plugin: name=mock_driver type=driver plugin_version=0.1.0
          2021-10-20T14:38:51.181-0400 [INFO]  agent: detected plugin: name=raw_exec type=driver plugin_version=0.1.0
          2021-10-20T14:38:51.181-0400 [INFO]  agent: detected plugin: name=exec type=driver plugin_version=0.1.0
          2021-10-20T14:38:51.181-0400 [INFO]  agent: detected plugin: name=qemu type=driver plugin_version=0.1.0
          2021-10-20T14:38:51.181-0400 [ERROR] agent: error starting agent: error="setting up server node ID failed: mkdir /path-without-permission: read-only file system"
      ```
      
      This change adds the final `ERROR` message. It's easy to miss the `==>
      Error starting agent` above.
      3ce89b75
    • Mike Nomitch's avatar
      3025ae60
    • Mahmood Ali's avatar
      vault: set JobID in Vault metadata (#11397) · 54ca97fe
      Mahmood Ali authored
      Closes: #11395 .
      54ca97fe
    • Mahmood Ali's avatar
      scheduler: stop allocs in unrelated nodes (#11391) · 56a7cc61
      Mahmood Ali authored
      The system scheduler should leave allocs on draining nodes as-is, but
      stop node stop allocs on nodes that are no longer part of the job
      datacenters.
      
      Previously, the scheduler did not make the distinction and left system
      job allocs intact if they are already running.
      
      I've added a failing test first, which you can see in https://app.circleci.com/jobs/github/hashicorp/nomad/179661 .
      
      Fixes https://github.com/hashicorp/nomad/issues/11373
      56a7cc61
    • Mahmood Ali's avatar
      Fix arm64 panics by updating google/snappy library to latest, 0.0.4 (#11396) · 5f6ad87c
      Mahmood Ali authored
      Pick up https://github.com/golang/snappy/pull/56 to handle arm64 architectures to fix panics. tldr; Golang 1.16 changed `memmove` implementation for arm64 requiring additional cpu registers that snappy wasn't preserving in its assembly implementation.
      
      Other projects have experienced this issue as well, searching for `encode_arm64.s:666` on your favorite search engine will reveal some.  Vault updated the dependency earlier this August: https://github.com/hashicorp/vault/pull/12371 .
      
      I believe this issue affects Nomad 1.2.x and 1.1.x. Nomad 1.0.x use Golang 1.15 and isn't affected. However, backporting the change to 1.0.x should be harmless.
      
      Fixed https://github.com/hashicorp/nomad/issues/11385 .
      5f6ad87c
    • James Rasell's avatar
    • Luiz Aoqui's avatar
    • Luiz Aoqui's avatar
  5. 26 Oct, 2021 1 commit
  6. 25 Oct, 2021 2 commits
  7. 22 Oct, 2021 6 commits
  8. 21 Oct, 2021 6 commits
  9. 20 Oct, 2021 5 commits
  10. 19 Oct, 2021 3 commits
  11. 18 Oct, 2021 2 commits
  12. 15 Oct, 2021 1 commit