Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1331190

Summary: system/grubby's postupgrade.sh cannot access boot/grub/grub.conf
Product: Red Hat Enterprise Linux 6 Reporter: Alois Mahdal <amahdal>
Component: preupgrade-assistant-el6toel7Assignee: Petr Stodulka <pstodulk>
Status: CLOSED NOTABUG QA Contact: Alois Mahdal <amahdal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.8CC: jmazanek
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-28 00:22:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alois Mahdal 2016-04-28 00:05:15 UTC
Description of problem
======================

preupgrade.sh from xccdf_preupg_rule_system_grubby_check produces
following error:

    ./postupgrade.sh: line 42: /boot/grub/grub.conf: No such file or directory

on both ppc64 and x86_64:

    https://beaker.engineering.redhat.com/jobs/1321635


Version-Release number of selected component
============================================

preupgrade-assistant-2.1.6-3.el6
preupgrade-assistant-el6toel7-0.6.46-1.el6
preupgrade-assistant-el6toel7-data-0.20160406-1.el6
redhat-upgrade-tool-0.7.43-1.el6


How reproducible
================

Not sure, see Additional info below


Steps to Reproduce
==================

Schedule /CoreOS/preupgrade-assistant/6to7/upgrade/mysql-sanity using
upgrade ("wrap") workflow.


Actual results
==============

Rule result is "fixed", postupgrade.sh is deployed and ran during upgrade.
Error is generated.


Expected results
================

No errors.  Result may be 'notapplicabble' for some architectures.


Additional info
===============

System boots just fine and upgrade test reports pass (save for one known issue.)

For s390x, result is 'notapplicabble' already.  We're not sure if it
should be also for ppc64; if yes, another bug should be filed for that
and this one will not be relevant to ppc64.  At any rate, the module
should work correctly for x86_64.

Reproducibility is not known;  I'm almost sure I've searched recent test
logs and did not see this so it may be matter of different machine setup.
Look for kickstatt and install logs in the beaker job.

Comment 1 Alois Mahdal 2016-04-28 00:22:30 UTC
Umm, my bad, I have misread my logs:  this happens only for ppc64, where it's sort of expected (2nd paragraph in Additional Info).

x86_64 is fine.