Globus Connect Server Endpoint Migration Status

Name

globus-connect-server endpoint migration-status - Show domain migration progress and verify each step

Synopsis

globus-connect-server endpoint migration-status [OPTIONS]…

Description

The globus-connect-server endpoint migration-status command reports the progress of the endpoint’s migration to its gaccess.io domain. It checks each step of Phase 1 (allocating the new domain, which is automatic) and Phase 2 (retiring the old domain, which is started with globus-connect-server endpoint migrate-domain), and works at any point before, between, or after the phases.

This command must be run as root on a node of the endpoint.

The report begins with a header showing the endpoint ID, the old and new domains, whether the endpoint has an OIDC server, and the environment. Each step is then listed with one of the following statuses:

OK: The step is complete.
PENDING: The step has not completed yet.
SKIP: The step does not apply to this endpoint.
FAIL: The step failed and will not complete without intervention.
UNKNOWN: The state of the step could not be determined.

The last line of the report is one of the following results:

IN PROGRESS: Phase 1 is not yet complete. The pending steps are listed.
PHASE 1 COMPLETE: Phase 1 is done and the endpoint is waiting for Phase 2 to be started.
FULLY MIGRATED: Both phases are complete.
NEVER NEEDED: The endpoint’s domain is already under gaccess.io and no migration is recorded for it. No action is required.
BLOCKED: The endpoint cannot be migrated yet, or the DNS service could not allocate a new domain for it. The reason is displayed.

The Domain Migration guide describes each result and how to respond to it.

Options

-h, --help: Show help message and exit.
--version: Show the version and exit.

Example

In this example, an endpoint has completed Phase 1 and is waiting for Phase 2:

sudo globus-connect-server endpoint migration-status
GCS Domain Migration Status
============================================================
Endpoint:   00000000-1111-2222-3333-444444444444
Old Domain: a1b2c.data.globus.org
New Domain: a1b2c.9f8e.gaccess.io
OIDC:       no
Env:        production

PHASE 1 — Allocate the new domain (Automatic)
  [OK     ] DNS: new name allocated
  [OK     ] Auth: redirect URIs — new added  — 3 old / 3 new
  [OK     ] Auth: scopes updated  — 2 scope(s) carry new domain
  [OK     ] DNS: new name resolves  — all 2 node(s) resolve
  [OK     ] AppSync: new domain config written  — a1b2c.9f8e.gaccess.io
  [OK     ] Cert: SANs cover both names  — covers both old and new domains
  [OK     ] Vhosts: new domain added  — 12 of 12 updated

PHASE 2 — Retire the old domain (admin-initiated)
  [PENDING] Transfer: endpoint domain updated  — endpoint hostname not migrated; 12 of 12 collection(s) not migrated
  [PENDING] Auth: old redirect URIs deleted  — 3 old-domain URI(s) still present
  [PENDING] DNS: old name deleted  — old domain still active (A)
  [PENDING] AppSync: final config written  — still using old domain
  [PENDING] info.json: domain_name updated  — still shows 'a1b2c.data.globus.org', expected 'a1b2c.9f8e.gaccess.io'
  [PENDING] Vhosts: old domain removed  — 0 of 12 cleaned up

PHASE 1 COMPLETE — awaiting Phase 2 (retire the old domain).
  Pending: Transfer: endpoint domain updated, Auth: old redirect URIs deleted, DNS: old name deleted, AppSync: final config written, info.json: domain_name updated, Vhosts: old domain removed