Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1412951 - Blacklist kms driver to prevent kexec issues
Blacklist kms driver to prevent kexec issues
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Discovery Image (Show other bugs)
6.2.5
Unspecified Unspecified
high Severity high (vote)
: 6.2.9
: Unused
Assigned To: Lukas Zapletal
Roman Plevka
http://projects.theforeman.org/issues...
: Reopened, Triaged
: 1334477 (view as bug list)
Depends On:
Blocks: 1417109
  Show dependency treegraph
 
Reported: 2017-01-13 03:49 EST by Lukas Zapletal
Modified: 2017-05-01 10:29 EDT (History)
12 users (show)

See Also:
Fixed In Version: foreman-discovery-image-3.1.1-20
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1417109 (view as bug list)
Environment:
Last Closed: 2017-03-06 03:37:01 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 15144 None None None 2017-01-13 04:06 EST
Red Hat Product Errata RHBA-2017:0447 normal SHIPPED_LIVE Satellite 6.2.8 Async Bug Release 2017-03-06 08:23:41 EST

  None (edit)
Description Lukas Zapletal 2017-01-13 03:49:51 EST
We found an issue in kexec when terminal is frozen due to graphics driver stack, this is a request to backport two lines into FDI for 6.2 to prevent these errors. We have seen this multiple times already, some cases were attached to 6.3 bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1334477

We've seen this with both virtualized and bare-metal environments.

*HIGH IMPACT*, *LOW RISK*, *LOW EFFORT*.
Comment 2 pm-sat@redhat.com 2017-01-13 06:17:15 EST
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15144 has been resolved.
Comment 4 Lukas Zapletal 2017-02-20 08:52:34 EST
Verification steps:

Verify that DRI drivers are not present on the FDI image:

rm -rf /lib/modules/*/kernel/drivers/gpu/drm /lib/firmware/{amdgpu,radeon}

Extra verification:

KExec VM in all possible QEMU video drivers (QXL, Cirrus, KVM): http://libvirt.org/formatdomain.html#elementsVideo and all should work fine.
Comment 5 Roman Plevka 2017-02-22 11:38:09 EST
I was unable to replicate the issue on sat6.2.7 (foreman-discovery-image-3.1.1-16.iso).

I've created generic hosts where each used a different driver:
-cirrus
-qxl
-vga

(the other 3 options - virtio, vmvga and xen were not working for me at all - vmvga+xen gave me the blank screen)

I booted up FDI, sent the facts out to the satellite and then provisioned them from satellite.
All console sessions made it through the kexec phase just fine.
Comment 6 Lukas Zapletal 2017-02-23 03:35:13 EST
*** Bug 1334477 has been marked as a duplicate of this bug. ***
Comment 7 Roman Plevka 2017-02-23 07:17:09 EST
VERIFIED
sat6.2.8 snap#3
foreman-discovery-image-3.1.1-20.iso
Comment 9 errata-xmlrpc 2017-03-06 03:37:01 EST
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-2017:0447
Comment 13 Lukas Zapletal 2017-03-23 06:05:57 EDT
QA NOTES:

Boot the image and verify these does NOT exist:

/lib/modules/*/kernel/drivers/gpu/drm /lib/firmware/{amdgpu,radeon}
Comment 21 Roman Plevka 2017-04-20 04:08:46 EDT
verified for snap3
(both rhel6 and rhel7 repos now contain -22 version of FDI package)
Comment 22 Bryan Kearney 2017-05-01 10:29:19 EDT
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-2017:1191
Comment 23 Bryan Kearney 2017-05-01 10:29:22 EDT
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-2017:1191

Note You need to log in before you can comment on or make changes to this bug.