Bug 1417109

Summary: Blacklist kms driver to prevent kexec issues
Product: Red Hat Satellite Reporter: Satellite Program <pm-sat>
Component: Discovery ImageAssignee: Lukas Zapletal <lzap>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.5CC: bbuckingham, bkearney, jcallaha, lhellebr, lzap, omaciel
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/15144
Whiteboard:
Fixed In Version: foreman-discovery-image-3.4.1-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1412951 Environment:
Last Closed: Type: ---
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: 1412951    
Bug Blocks:    

Comment 2 Lukáš Hellebrandt 2017-10-24 13:41:09 UTC
Verified with Sat6.3 snap 20.

1) Setup PXE provisioning, auto provisioning [1]
2) On a machine within Capsule's subnet, boot from PXE, going into Foreman Discovery Image
3) Press Enter before it sends facts, set own fact: "kexec = true"
4) Send the facts
5) Start sshd, connect to it, verify that files /lib/modules/*/kernel/drivers/gpu/drm and /lib/firmware/{amdgpu,radeon} do not exist
6) From Satellite WebUI, autoprovision this discovered host (Hosts -> Discovered Hosts -> Auto Provision All)
7) If it kexecs and survives until system installation, the bug is fixed

^ Tried with Cirrus, QXL, VGA video drivers.



[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/host_configuration_guide/sect-red_hat_satellite-host_configuration_guide-discovering_bare_metal_hosts_on_satellite-provisioning_discovered_hosts

Comment 3 Bryan Kearney 2018-02-21 17:33:44 UTC
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/RHSA-2018:0336

Comment 4 Bryan Kearney 2018-02-21 17:33:55 UTC
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/RHSA-2018:0336