Impact of defaults in Warewulf Upgrades
Introduction
When upgrading nodes in Warewulf using the wwctl upgrade nodes
command, the --add-defaults
flag plays a critical role in ensuring that default profiles and configurations are added. However, this can lead to issues in environments where no defaults were previously configured, potentially causing conflicts with existing setups. This article explains the behavior of the --add-defaults
flag, its impact, and how to resolve related issues.
Problem
Using the --add-defaults
flag during wwctl upgrade nodes
adds default profiles and configurations. In environments without pre-existing defaults, this can introduce settings that conflict with the current network or system configuration, leading to potential issues.
Resolution
If you encounter issues after using the --add-defaults
flag, follow these steps to resolve them:
Step 1: Review added overlays
Inspect the overlays added by the upgrade process. These may include network-related overlays like:
ifcfg
NetworkManager
debian.interfaces
wicked
Run the following command to list the overlays:
wwctl overlay list
Step 2: Customize the default profile
Modify the default profile to align with your environment by removing or adjusting problematic overlays.
Step 3: Test and Validate
After making changes, test the configuration to ensure nodes operate as expected.
Notes
The --add-defaults
flag is mandatory for the wwctl upgrade nodes command, ensuring that essential configurations are added during the upgrade process. While the flag does not directly add network device configurations, conflicts may arise from how the new overlays interact with existing setups. Always back up your configuration files before performing upgrades.