populateSack was causing a kernel panic, believe it or not.
---
pyanaconda/packaging/yumpayload.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/pyanaconda/packaging/yumpayload.py b/pyanaconda/packaging/yumpayload.py
index d3625c5..5b30578 100644
--- a/pyanaconda/packaging/yumpayload.py
+++ b/pyanaconda/packaging/yumpayload.py
@@ -257,7 +257,7 @@ reposdir=%s
self._yum.preconf.releasever = releasever

self._yumCacheDirHack()
- self._yum.repos.populateSack(which='enabled', mdtype='all')
+ self.gatherRepoMetadata()

# trigger setup of self._yum.config
log.debug("installation yum config repos: %s"
--
1.7.7.6

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

> populateSack was causing a kernel panic, believe it or not.

OOM?

- Chris

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

On Wed, 2012-05-02 at 15:59 -0400, Chris Lumens wrote:
> > populateSack was causing a kernel panic, believe it or not.
>
> OOM?

That was my first and only guess. I saw that there were several hundred
megabytes of memory free immediately before calling populateSack, but
the kernel didn't tell anything when it panicked.

>
> - Chris
>
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@redhat.com
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list


_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list