Upgrade isn't permanent #732
Comments
|
Related to #729, fixed by 82ebcb2, merged in master. @bitwalker will you care to deploy new release please? |
pvmart
added a commit
to pvmart/uniris-node
that referenced
this issue
Feb 15, 2021
ghost
pushed a commit
to archethic-foundation/archethic-node
that referenced
this issue
Feb 15, 2021
* Cleanup config * Move Uniris.Bootstrap.NetworkInit.genesis_pools to config.exs * Split UNIRIS_P2P_PORT configuration * Use mix configs for distillery release * Fix install script arguments * Keep runtime config in release specific folder * Provide hot upgrades * Add distillery hook to copy process environment from the running node to upgrde script during release upgrade * Do compile testnet and minenet in install script * Use unpublished distillery See bitwalker/distillery#732
|
Ditto, It's quite problematic as each node on my cluster services a few hundred thousand devices and the hard restarts for minor code updates are problematic, but so are version mismatches. ^_^ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Create a release and then a new release with upgrade option. Then run the old release, perform an upgrade to the new one, stop the running system and start it again. It starts using the old version.
Linked to this, the upgrade isn't using the new
privdirectory (based on Phoenix applications this means you're still using old static files).Description of issue
The text was updated successfully, but these errors were encountered: