Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • N Nomad
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • 小 白蛋
  • Nomad
  • Repository
Switch branch/tag
  • nomad
  • scheduler
  • reconcile.go
Find file BlameHistoryPermalink
  • Mahmood Ali's avatar
    Revert the `requireCanary` check introduced in... · 64175dcc
    Mahmood Ali authored Sep 10, 2020
    Revert the `requireCanary` check introduced in https://github.com/hashicorp/nomad/pull/8691/files#diff-1801138ac4d10f2064ba6f2e434ac9b4L430-R431 .
    
    The change was intended to fix a case where a canary alloc may fail to
    be rescheduled if all the other allocs fail as well (e.g. if all allocs
    happen to be placed on a node that died).  However, it introduced some
    unintended side-effects.
    
    Reverting the change for now and will investigate further.
    64175dcc

免费DevSecOps平台,让您的项目体验完整的DevSecOps流程,让项目更安全