Bug 1731803
Summary: | [machines] The PXE installation failed if VM is created by non-root user | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | YunmingYang <yunyang> |
Component: | cockpit-appstream | Assignee: | Katerina Koukiou <kkoukiou> |
Status: | CLOSED ERRATA | QA Contact: | YunmingYang <yunyang> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.1 | CC: | leiwang, mpitt, wshi, xchen |
Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
Target Release: | 8.1 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-11-05 20:41:55 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: |
Description
YunmingYang
2019-07-22 06:32:52 UTC
Fixed upstream with: commit 96458223e193315945eebdac528d29ff03db05fe Author: Katerina Koukiou <kkoukiou> Date: Wed Jul 24 13:07:48 2019 +0200 machines: disable pxe booting when a user selected session connection git describe 964582 198-104-g96458223e Yunming, can you please QA ack? Martin, i check the flag, it seems that i have already set the 'QA ack' flag. Did I miss something? Yunming: Ah, my bad, it was devack that was missing :) Thanks! Test Versions: cockpit-machines-197.1-1.el8.noarch libvirt-dbus-1.2.0-2.module+el8.1.0+2983+b2ae9c0a.x86_64 Test Steps: 1. Login cockpit with a non-root user 2. Open the VM creation dialog 3. Change the Connection to 'QEMU/KVM User connection', then check 'Installation Source Type' Test Results: When Connection is set to 'QEMU/KVM User connection', 'Netwrok Boot(PXE)' in 'Installation Source Type' can not be selected. According to the results, move the status to VERIFIED. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3325 |