Hide Forgot
Description of problem: During RHEL 7.2 installation, after installing the DUD image containing updated megaraid_sas kmod drivers, inbox driver is still being used. The new driver is not getting loaded even after installing the DUD. This can be confirmed by getting to anaconda shell and checking /sys/module/megaraid_sas/version. Although modinfo shows the latest version. This is a regression from RHEL 7.1 where DUD installation used to unload older inbox driver and new module was getting loaded as expected. Version-Release number of selected component (if applicable): Anaconda version: 21.48.22.56-1 How reproducible: Always Steps to Reproduce: 1. Make a new RHEL 7.2 installation with the megaraid_sas DUD 2. After installing the DUD, go to anaconda shell 3. Check megaraid_sas module version loaded with "cat /sys/module/megaraid_sas/version" Expected results: Version of megaraid_sas should show out of box driver: 06.810.10.00 Actual results: Version shows the inbox driver: 06.807.10.00-rh1 Additional info: Looking at the anaconda code, driver updates script does not seem to unloading the older modules before trying to load the new driver file. This might be causing the issue.
Created attachment 1192858 [details] megaraid_sas RHEL 7.2 DUD image for reproducing the issue megaraid_sas DUD image for RHEL 7.2 which will help to recreate the issue. NOTE: This issue is only seen if there is a MegaRAID card connected to the host. If the card is not present, then since the inbox driver is not loaded, anaconda is able to load the new drivers.
Created attachment 1192862 [details] megaraid_sas RHEL 7.1 DUD image which is working.
Tomas, Can you get this routed to right contact? Thanks, Sumit
Hello, We are aware of this issue (tracked under bz1101653). The problem only occurs if the pci ids supported by the DUD are already supported by the in-box driver, and the hardware is connected to the system. Therefore I don't think this is a regression since rhel-7.1, more likely the megaraid_sas device pci ids are not supported by the rhel-7.1 in-box driver, is that correct? Setting Depends-on bz1101653. This bug is already assigned to the right component/contact. Thanks!
As a workaround, you can boot the installation kernel with following option: modprobe.blacklist=megaraid_sas This will cause the in-box driver not to be loaded automatically, but will not prevent the DUP package to load the modules later.
(In reply to Stanislav Kozina from comment #6) > As a workaround, you can boot the installation kernel with following option: > > modprobe.blacklist=megaraid_sas > > This will cause the in-box driver not to be loaded automatically, but will > not prevent the DUP package to load the modules later. Thanks for quick response. Currently we are removing driver(rmmod megaraid_sas) and then loading DUD driver- modprobe megaraid_sas. I can have the workaround provided by you documented in our README. Will this be fixed in RHEL7.3? If yes, I would be happy to test the same on RHEL7.3 beta/RC OS. Thanks, Sumit
(In reply to Stanislav Kozina from comment #5) > Hello, > We are aware of this issue (tracked under bz1101653). The problem only > occurs if the pci ids supported by the DUD are already supported by the > in-box driver, and the hardware is connected to the system. Therefore I > don't think this is a regression since rhel-7.1, more likely the > megaraid_sas device pci ids are not supported by the rhel-7.1 in-box driver, > is that correct? > Setting Depends-on bz1101653. This bug is already assigned to the right > component/contact. Thanks! Hi, Thanks for the update. The RHEL 7.1 in-box megaraid_sas driver actually supports the PCI ids of the card. We see the in-box driver loaded during installation and it recognizes the card and drives as well (if the DUD package was not provided). And if the DUD package is provided, then the new driver gets loaded as expected. So this issue is not seen in RHEL 7.1. It seems like in 7.1, the anaconda installer first unloads the in-box driver and then load the new modules. Whereas in 7.2, it does not unload the module before trying to load. Regards, Shivasharan
Clearing need-info from comment#4