Bug 217535

Summary:	ofpath broken in yaboot due to missing symlinks
Product:	Red Hat Enterprise Linux 5	Reporter:	Steve Whitehouse <swhiteho>
Component:	yaboot	Assignee:	Roman Rakus <rrakus>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0	CC:	anton, rwilliam, tsmetana
Target Milestone:	---
Target Release:	---
Hardware:	ppc64
OS:	Linux
URL:	http://ozlabs.org/pipermail/linuxppc-dev/2005-May/019130.html
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-01-20 22:15:14 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:

Description Steve Whitehouse 2006-11-28 14:42:17 UTC

Description of problem:

 [root@doral etc]# ofpath /dev/sda
 ofpath: /proc/device-tree is broken

How reproducible:
Always

Steps to Reproduce:
1. As above

Expected results:

It should return the device path.

Comment 1 David Woodhouse 2008-05-05 12:30:25 UTC

What machine? What symlinks? Does the current Fedora version of ofpath work?

Comment 2 Roman Rakus 2008-05-05 13:05:45 UTC

Machine: ppc03.englab.brq.redhat.com
Trying with: yaboot-1.3.13-12.fc9.ppc.rpm

Still same problem.

Porting upstream patch should be easy...

Comment 3 RHEL Program Management 2008-06-02 20:41:44 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 9 errata-xmlrpc 2009-01-20 22:15:14 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0244.html