[GCE] Don't err when the VM whose bot to manage doesn't exist

Management tasks are triggered every minute, and if necessary the
management task will trigger another task to delete the VM. Occasionally
this task is delayed and only completes after the next management task
has already been scheduled. This results in the second management task
seeing a non-existent VM entity, or a recreated VM entity with a
non-existent GCE instance. In such cases, the management task currently
errs, which is expected and correct behavior, but produces an error
message in the logs making it look unexpected or incorrect. For these
cases, don't err.

Bug: 897355
Change-Id: I276fabb0b96d1e265786334550ed0e1715c6b085
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/1583091
Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: smut <smut@google.com>
2 files changed
tree: 480909e78c83e88399f1a99c0918f939cdfbce9f
  1. .gitattributes
  2. .travis.yml
  3. AUTHORS
  4. CONTRIBUTING.md
  5. CONTRIBUTORS
  6. LICENSE
  7. OWNERS
  8. PRESUBMIT.py
  9. README.md
  10. appengine/
  11. auth/
  12. buildbucket/
  13. cipd/
  14. client/
  15. codereview.settings
  16. common/
  17. config/
  18. cq/
  19. dm/
  20. examples/
  21. gce/
  22. grpc/
  23. hardcoded/
  24. logdog/
  25. luci_notify/
  26. lucicfg/
  27. lucictx/
  28. machine-db/
  29. milo/
  30. mmutex/
  31. mp/
  32. pre-commit-go.yml
  33. scheduler/
  34. scripts/
  35. server/
  36. starlark/
  37. swarming/
  38. tokenserver/
  39. tools/
  40. tumble/
  41. vpython/
  42. web/
README.md

luci-go: LUCI services and tools in Go

GoDoc

Installing

LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:

fetch infra
cd infra/go
eval `./env.py`
cd src/go.chromium.org/luci

Contributing

Contributing uses the same flow as Chromium contributions.