When I use grub2-mkconfig to create a new grub.cfg, the problem is resolved. So this appears to be a grubby bug, which is the only thing modifying either grub.cfg or grubenv after anaconda runs grub2-mkconfig and grub2--set-default. https://bugzilla.redhat.com/show_bug.cgi?id=1261569 -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
