Bug 22536

Summary: Removing multiple kernels does not fully update grub2
Product: Mageia Reporter: Thomas Andrews <andrewsfarm>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: Normal CC: zen25000
Version: 6   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Thomas Andrews 2018-02-06 22:36:34 CET 
Description of problem:
This morning I updated a computer to 64-bit kernel-desktop 4.14.16-1. There were two kernels already on the system, kernel-desktop 4.14.13 and 4.9.56. After satisfying myself that the new kernel was operating correctly, I used drakrpm to remove the two old kernels. But, when I rebooted, using the "advanced" choice in grub2, the list that was presented still had entries for kernel 4.14.13 on it. Only the entries for 4.9.56 had been removed.

After booting into kernel 4.14.16, I checked with drakrpm and kernel 4.14.13 had indeed been removed from the system. Grub2 had not been properly updated. I know that running update-grub will take care of the situation, but it shouldn't have to be that way. 

This may or may not be related to Bug #16268. While the descriptions are different, they are close enough to make me think that's possible. Perhaps this is the result of whatever was done to address that bug.


How reproducible: I'm not sure at this point, but I suspect always.


Steps to Reproduce:
1. Remove more than one kernel in one operation, using drakrpm.
2. Check the "Advanced" grub2 menu.
3.
Comment 1 Barry Jackson 2018-02-07 01:38:04 CET 
(In reply to Thomas Andrews from comment #0)
> 
> This may or may not be related to Bug #16268. While the descriptions are
> different, they are close enough to make me think that's possible. Perhaps
> this is the result of whatever was done to address that bug.
> 

Yes this is a duplicate of Bug #16268 which is still open, so closing as duplicate - please add any further comments in that bug.

Thanks for taking the time to report this.

*** This bug has been marked as a duplicate of bug 16286 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
CC: (none) => zen25000

Comment 2 David Walser 2018-02-07 02:08:06 CET 

*** This bug has been marked as a duplicate of bug 16268 ***