v2 app shows previous region is status after migration

Questions / Help
1

After migration to v2 fly app using migrate-to-v2, flyctl status still shows previous region (fra), while in fly.toml I have primary_region = “waw”. Is it expected behaviour?

# fly.toml app configuration file generated for different-api on 2023-05-03T17:07:58+03:00
#
# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
#

app = "different-api"
primary_region = "waw"
kill_signal = "SIGINT"
kill_timeout = "5s"

[experimental]
  auto_rollback = true

[build]
  builder = "heroku/buildpacks:20"

[env]
  PORT = "8080"

[[services]]
  protocol = "tcp"
  internal_port = 8080
  processes = ["app"]

  [[services.ports]]
    port = 80
    handlers = ["http"]
    force_https = true

  [[services.ports]]
    port = 443
    handlers = ["tls", "http"]
  [services.concurrency]
    type = "connections"
    hard_limit = 25
    soft_limit = 20

  [[services.tcp_checks]]
    interval = "15s"
    timeout = "2s"
    grace_period = "1s"
    restart_limit = 0
2

Hey @lishtvan, AFAIK migrate-to-v2 doesn’t change the regions of your existing instances. If your Nomad VM(s) were all running in fra before the migration, then migrate-to-v2 would replace them with an equal number of machines also running in fra, even if you’ve changed the primary_region. You can use fly scale count <n> --region <region> to adjust the number of machines per region after-the-fact, though.

3

Thank you!

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.