Bug 188927 - need to include "repodata" dir for NFS install tree
Summary: need to include "repodata" dir for NFS install tree
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: release-notes
Version: devel
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Release Notes Tracker
QA Contact: Karsten Wade
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-13 18:11 UTC by MarkA
Modified: 2007-04-18 17:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-02-10 17:16:35 UTC
Embargoed:


Attachments (Terms of Use)

Description MarkA 2006-04-13 18:11:00 UTC
Description of problem:

Problem pertains to installing FC5 on NFS server for network-based
upgrades/installations.  Instructions included in "README" file of disc1 fails
to specify that "repodata" directory must be copied to server in addition to the
"Fedora" directory and "RELEASE-NOTES*" files.  Without the "repodata"
directory, installation/upgrade will fail.

This was not an issue with FC4.  I have been informed, via IRC, that FC5
requires "repodata" because it uses "yum" during the install process, which FC4
did not.

Version-Release number of selected component (if applicable):

NA

How reproducible:

Always

Steps to Reproduce:
1. Follow instructions in README file on disc 1, or Installation Guide, to
create a directory for NFS based installation.  Instructions specify the
following command:

cp -a /mnt/cdrom/Fedora /target/directory

2.  Insure that no "repodata" directory is present under "/target/directory"
3. Attempt to use "/target/directory" for NFS-based installation.
  
Actual results:

Installation fails due to inability to find "repodata/repomd.xml" 

Expected results:

Successful installation.

Additional info:

Comment 1 Stuart Ellis 2006-05-02 22:21:31 UTC
Thanks - the Fedora Installation Guide doesn't actually document server
configuration, so I'm reassigning this so that someone can look into amending
the README.

Comment 2 Karsten Wade 2007-02-10 17:16:35 UTC
This has been fixed in the README file; thanks for the report, sorry it hung
open for so long. :)


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