Bug

The changes introduced in #2158 results in ignition failing when it tries to handle an existing group. Not sure if this is an ignition issue or openSUSE MicroOS issue.

Operating System Version

openSUSE MicroOS

Ignition Version

Ignition 25.1

Environment

What hardware/cloud provider/hypervisor is being used to run Ignition?

It is running on x64 bare metal.

Expected Behavior

Group handling behavior should be idempotent. Ignition should not fail if a group already exists on the system.

Actual Behavior

Ignition fails with

files: ensureGroups: op(1): [started] modifying group GROUP_NAME
files: ensureGroups: op(1): executing: "groupmod" "--root" "/sysroot" GROUP_NAME
files failed 
files: ensureGroups: op(1): [failed] modifying group GROUP_NAME: exec "groupmod": executable file not found in $PATH: Cmd: "groupmod" "--root" "/sysroot" GROUP_NAME Stdout: "" Stderr: ""

Reproduction Steps

1. Install OpenSUSE MicroOS and configure with ignition.
2. Remove /etc/machine-id to trigger ignition in the next boot.
3. Reboot the machine.