| Summary: | /boot/grub2/grub.cfg contains invalid information about its origin | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ivo Sarak <ivo> |
| Component: | grub2 | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | dennis, mads, pjones, stanley.king |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-04-17 21:49:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
grub.cfg _is_ generated as described. grubby do however patch the file directly. The result should be very similar to what would be generated, but there are various bugs and quirks in this area. The most obvious reason for getting a substantially different grub.cfg is however that grub2 has been updated since last time grub.cfg was generated. |
Description of problem: The /boot/grub2/grub.cfg does list as: # # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # Obviously it is wrong as if to issue that given command ('grub2-mkconfig -o /boot/grub2/grub.cfg'), that command will generate substantially different grub2.cfg file as it is there by itself. What does generate that file and where are those templates it is being generated from? Version-Release number of selected component (if applicable): rpm -qa|grep grub grub2-1.99-14.fc17.x86_64 grub-efi-0.97-87.fc18.x86_64 grubby-8.8-3.fc17.x86_64 How reproducible: Always. Steps to Reproduce: 1. Install a new kernel with 'yum update'; 2. Make a backup of the /boot/grub2/grub.cfg file; 3. Issue a 'grub2-mkconfig -o /boot/grub2/grub.cfg' command; 4. Compare those files. Actual results: These files are different. For example the 'grub2-mkconfig -o /boot/grub2/grub.cfg' will add a "recovery mode" menu entry for each installed kernels, but 'yum update' does not do that. Expected results: Both files must be the same - according to the /boot/grub2/grub.cfg its origin is from 'grub2-mkconfig', so there should be no differences when it will get updated by 'yum update'. Additional info: