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 1186655 - preupgrade-assistant-content should detect YABOOT on ppc64
Summary: preupgrade-assistant-content should detect YABOOT on ppc64
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: preupgrade-assistant-contents
Version: 6.7
Hardware: ppc64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Hracek
QA Contact: Tereza Cerna
URL:
Whiteboard:
: 1217373 (view as bug list)
Depends On:
Blocks: 1163684
TreeView+ depends on / blocked
 
Reported: 2015-01-28 09:14 UTC by Petr Hracek
Modified: 2015-08-13 08:50 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Do not document.
Clone Of:
Environment:
Last Closed: 2015-08-13 08:50:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1608 0 normal SHIPPED_LIVE preupgrade-assistant-contents bug fix update 2015-08-13 12:49:54 UTC

Description Petr Hracek 2015-01-28 09:14:14 UTC
Description of problem:
Detect whether yaboot is installed on ppc64
and report it as HIGH risk.
If yaboot is installed then upgrade fails currently.

User could create a grub.conf file and store them to specific location
defined by solution text.
Preupgrade script will check whether grub.conf exists on that location
and if it does not exist then it will fail.

How reproducible:
allways on ppc64 and yaboot

Steps to Reproduce:
1.
2.
3.

Actual results:
Upgrade on ppc64 failed in case of yaboot.

Expected results:
Upgrade is successful.

Additional info:

Comment 10 Frantisek Kluknavsky 2015-05-22 15:48:50 UTC
*** Bug 1217373 has been marked as a duplicate of this bug. ***

Comment 16 Tereza Cerna 2015-08-10 12:21:41 UTC
Bad condition in /root/preupgrade/RHEL6_7/system/yaboot/check.sh:

bad:         if  [ -f '/etc/default/grub' ]; then
have to be:  if ![ -f '/etc/default/grub' ]; then

Comment 17 Frantisek Kluknavsky 2015-08-10 13:37:23 UTC
http://brewweb.devel.redhat.com/brew/taskinfo?taskID=9664614

Comment 19 Alois Mahdal 2015-08-10 23:39:54 UTC
As terka outlined above, the preupgrade-assistant's recommendation works OK now.

However, it's worth noting that ppc64 is still considered unsupported by KB article as well and by Architecture Support, so upgrade is still not possible to do without `--force`.

Comment 21 errata-xmlrpc 2015-08-13 08:50:02 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1608.html


Note You need to log in before you can comment on or make changes to this bug.