Still been playing around with this and I still can't get it to work correctly. I get through the stage 2, then get the error message:
Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been correctly generated. Cannot retrieve repository metadata (repomd.xml) for repository: anaconda-base-201004270002.x86_64. Please verify its path and try again. I have been able to use this to build physical servers, so what would the difference be? Scott On Tue, Jun 7, 2011 at 10:12 AM, Mark Watts <[email protected]>wrote: > On Mon, 6 Jun 2011 14:13:59 -0700, "Kennedy, Ryan" <[email protected]> > wrote: > > Interesting... this is true but only for the hosts I have kickstarted > > since upgrading from Spacewalk 0.6 to 1.4. I wondered why they were > > showing with the white icon instead of the usual gray/blue one. > > > > Now I have a question... how do I get previously kickstarted/managed > hosts > > (all VMware guest VMs mind you) to show up as virtual systems? Not that > it > > makes much of a difference but this could prove to be a point of > confusion > > for some folks in my organization. > > > I've started at Spacewalk 1.3 so I'm not sure when this feature came in. > > I'd suspect that running a "rhn-profile-sync" would update such things. > > Mark. > > -- > Mark Watts BSc RHCE > http://www.linux-corner.info/ > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
