Bug 1603211

Summary:	grub2-reboot: /usr/bin/grub2-editenv: error: cannot rename the file /boot/grub2/grubenv.new to /boot/grub2/grubenv: No such file or directory.
Product:	Red Hat Enterprise Linux 7	Reporter:	Prarit Bhargava <prarit>
Component:	grub2	Assignee:	Peter Jones <pjones>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.6	CC:	jstodola, pjanda
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-15 07:40:46 UTC	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:
Bug Blocks:	1568427, 1670353

Description Prarit Bhargava 2018-07-19 13:11:03 UTC

Description of problem: Error is output when using grub2 commands to modify boot order.


Version-Release number of selected component (if applicable):grub2-2.02-0.73.el7.x86_64


How reproducible: 100%


Steps to Reproduce:
1. grub2-reboot 0
2.
3.

Actual results: 

cat: /boot/efi/EFI/redhat/grubenv: No such file or directory
/usr/bin/grub2-editenv: error: cannot rename the file /boot/grub2/grubenv.new to /boot/grub2/grubenv: No such file or directory.
/usr/bin/grub2-editenv: error: cannot rename the file /boot/grub2/grubenv.new to /boot/grub2/grubenv: No such file or directory.

and grub2-reboot command does not work.

Expected results: grub2-reboot command should be error free and work.


Additional info:

Comment 3 Jan Stodola 2018-07-20 15:20:35 UTC

Very likely the same root cause as in bug 1602773

Comment 6 RHEL Program Management 2021-02-15 07:40:46 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.