Updating procedure to improve image-builder user mangement #7852
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
The procedure for managing the image-builder user in the Operating Systems Management | Artifacts page contained unnecessary steps that modified the underlying OS. The goal is to add a user (image-builder) and configure the system to allow that user to run the image-builder process. That requires that the user can access /dev/kvm (which has permissions: crw-rw---- root:kvm) indicating that the user needs to either be the root user, or belong to the kvm group.
This PR was created for Issue #7846
#7846
Description of changes:
Update the user management procedure to be OS-specific.
Added additional configuraiton to add the image-builder user to the appropriate groups at creation time (sudo/wheel,kvm).
replaced "/home/$USER" with "${HOME}" throughout entire document.
removed suggestions to modify OS file permissions to /dev/kvm.
NOTE: there are essentially 2 procedure for creating an image (requires KVM: Bare Metal/Cloud Stack - the other methods do not)
Removed any steps demonstrating how to modify the OS
Updated the step to create a user to have that step include the
kvm
and "admin" group at that time (several examples provided here)If the user was created using the updated
useradd
command, then the usermod step is unnecessary. Therefore removed that stepTesting (if applicable):
The following was run on an Ubuntu 22.04
The following was run on Red Hat Enterprise Linux 8
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.