James, On Thu, 2008-11-27 at 11:38 -0800, James Fillman wrote: > Ok, I’ve imported all 14,000 fedora packages, I’ve created a kickstart > tree based on the Fedora DVD, I’ve got a kickstart profile and an > activation key set up. When I go to install a new system with the > kickstart file, once it reaches the ‘reposetup’ step, it fails with > the following error: > > Unable to read package metadata. This may be due to a missing repodata > directory. Please ensure that your install tree has been correctly > generated. I've never seen this.
> Cannot retrieve repository metadata (repomd.xml) for repository > Workstation. Please verify its path and try again. I have seen this. I have to re-provision my workstation if I get this. I've no idea what causes it as rhn_check and rhn-profile-sync both work, but "yum update" does not. > If I look at my kickstart file, I can see that spacewalk has added > these repos to the beginning of the file: These repos seem to be automagically added by spacewalk. I know of no way to remove them. I've documented everything I currently know about managing F9 systems with spacewalk here https://fedorahosted.org/spacewalk/wiki/ManagingFedoraSystems There are some things that simply don't work. The most important, from my POV, is that packages associated with an activation key don't install when the system registers (I *think* they'd have to be in your KS tree, not your repos). Furthermore, it's not currently possible to define a Stored Profile of packages and configuration and apply it to all your clients. So, from my limited experience, it's possible to use Spacewalk to provision F9 systems and push down packages to install on individual machines. I think we have to wait until 0.4 to get Stored Profiles to work. -- Aidan
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
