The `mv` command is typically used to rename files in a Linux
environment, so keep that convention here for container rename.
Signed-off-by: Jonathon Anderson <janderson@ciq.com>
Renaming a container causes its images to be abandoned in the previous
name. This causes those images to be removed after a successful rename.
New images can be rebuilt during the rename using the `--build`
argument.
Signed-off-by: Jonathon Anderson <janderson@ciq.com>
The original implementation presented a warning if more than two
arguments were presented, and didn't handle the case where fewer than
two arguments were provided. This change requires precisely two
arguments and returns an error otherwise.
Signed-off-by: Jonathon Anderson <janderson@ciq.com>
If a node contains several profiles and these profiles have
overlays attached, these profiles are now merged. Overlays
can't be excluded as this can not be displayed to the user
Signed-off-by: Christian Goll <cgoll@suse.com>
Since grub support no longer depends on a default container, no longer
automatically set default container on import.
Signed-off-by: Jonathon Anderson <janderson@ciq.com>
Also the boot method is now configured globaly as this is
the only way to make sure that unkonwn nodes get the right
stuff
Signed-off-by: Christian Goll <cgoll@suse.com>
With eth0 specified as the default interface device, all interfaces by default
were attempted to be renamed to eth0. This didn't break before because device
renaming wasn't working for multiple interfaces in general; but now that it's
fixed, we should no longer be setting a default interface name.
Signed-off-by: Jonathon Anderson <janderson@ciq.com>
IPXESOURCE is pointing to /usr/share/ipxe/ by default, so the `ipxe/`
directory should not be included in the compiled-in relative defaults.
Fixes a bug in #1010
Signed-off-by: Jonathon Anderson <janderson@ciq.com>
setting the ConfigFile (location of nodes.conf) in init()
led to the situation that a configured Paths.Sysconfdir is ignored.
Signed-off-by: Christian Goll <cgoll@suse.com>
Writing absolute file names in testenv breaks safety that files in the
test environment are written to the designated temporary path. Adjusted
the relevant tests to use testenv.WriteFile.
Signed-off-by: Jonathon Anderson <janderson@ciq.com>
