What happened?

Steps to reproduce

1. Pull a FusionAuth image via Docker but do not start it yet.
2. Restrict outbound connectivity with a tool like iptables. NOTE that, in the most common case where this occurs, your system must allow outbound DNS traffic to a DNS server that resolves Internet hostnames, but block everything else. If your system does not resolve Internet hostnames (e.g. completely isolated network), this is not likely to affect you due to the nature of this race condition.
3. Prepare a kickstart file with an air gapped license.
4. Start FusionAuth.

Expected result

After seeing the kickstart HTTP requests executed in the logs, FusionAuth activates the license, the license is persisted to the database, and licensed features continue to work.

Actual result

A race condition occurs, the license does not remain in the database, and after some time (up to 10 minutes), licensed features quit working

The same behavior occurs when activating a license in the Reactor GUI or via the Reactor API.

Version

1.57.1

Affects Versions

No response

Alternatives / Workarounds

After activation is complete, do a database UPDATE on the instance table, and set the license column to your "license text" from the FusionAuth account site, and the license_id column to the "license key" from the FusionAuth account site, and restart FusionAuth. (Modifying the database directly is unsupported but provided here for clearer debugging/troubleshooting.)