Bug 1554735
Summary: | RFE: customize --selinux-relabel should be the default, with --no-selinux-relabel used to opt out | ||
---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Lee Yarwood <lyarwood> |
Component: | libguestfs | Assignee: | Laszlo Ersek <lersek> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | Jiri Herrmann <jherrman> |
Priority: | medium | ||
Version: | unspecified | CC: | jherrman, kkiwi, laine, lersek, lmanasko, mjahoda, ptoscano, rjones, yoguo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
.Using `virt-customize` sometimes causes `guestfs-firstboot` to fail
After modifying a virtual machine (VM) disk image using the `virt-customize` utility, the `guestfs-firstboot` service in some cases fails due to incorrect SELinux permissions. This causes a variety of problems during VM startup, such as failing user creation or system registration.
To avoid this problem, use the `virt-customize` command with the `--selinux-relabel` option.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-05-11 03:47:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2075718 |
Description
Lee Yarwood
2018-03-13 09:11:29 UTC
Does adding --selinux-relabel fix things? There's also discussion of making that flag default to true unless the user selects ‘--no-selinux-relabel’, which would make it less of a common trap: https://gb.redhat.com/archives/libguestfs/2018-February/msg00039.html (In reply to Richard W.M. Jones from comment #1) > Does adding --selinux-relabel fix things? Yes, thanks! (In reply to Richard W.M. Jones from comment #2) > There's also discussion of making that flag default to true unless > the user selects ‘--no-selinux-relabel’, which would make it less of > a common trap: > https://gb.redhat.com/archives/libguestfs/2018-February/msg00039.html Cool, yes that would be useful. Feel free to close this bug out if you don't want to track that here. Let's recycle this bug for this purpose. Fixed up-stream in: libguestfs commit range 00b9ef239342..08c4ac90f5a3 libguestfs-common commit range 81f86a0058a9..48527b8768d7 guestfs-tools commit 19de3d1c8d4e virt-v2v commit 0c24fc6015ce |