Upgrade deletes class parameters from PE Master (other groups too?) #130
Comments
reidmv
added a commit
that referenced
this issue
Nov 2, 2020
Users may have their own config data specified for the PE Master group. This commit ensures that when peadm enforces node group configuration including config data on the PE Master group, it merges required config into existing user data to avoid configuration loss.
reidmv
added a commit
that referenced
this issue
Nov 2, 2020
Users may have their own config data specified for the PE Master group. This commit ensures that when peadm enforces node group configuration including config data on the PE Master group, it merges required config into existing user data to avoid configuration loss.
reidmv
added a commit
that referenced
this issue
Nov 2, 2020
Users may have their own config data specified for the PE Master group. This commit ensures that when peadm enforces node group configuration including config data on the PE Master group, it merges required config into existing user data to avoid configuration loss.
reidmv
added a commit
that referenced
this issue
Nov 2, 2020
GH-130 Fix overwrite of user config data
reidmv
added a commit
that referenced
this issue
Nov 2, 2020
At least for the configuration data attribute. A long-term solution is going to need to be modifying WhatsARanjit/node_manager to support a `purge` parameter to control this behavior on various different attributes.
reidmv
added a commit
that referenced
this issue
Jan 28, 2021
Use node_manager's new purge_behavior parameter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
When running peadm::upgrade, any class parameter configuration added by the user to PE Master, such as
code_manager_auto_configure=true, will be deleted.Expected Behavior
User configuration of class parameters in PE Master and other built-in groups should be preserved by peadm::upgrade.
The text was updated successfully, but these errors were encountered: