Re: PATCH: depsolve-kill fix for plague-0.5.0
On Tue, 2006-10-31 at 07:39 -0500, Joe Todaro wrote:
Dan Williams <dcbw(a)redhat.com> wrote on 10/30/2006 03:53:13 PM:
> On Fri, 2006-10-27 at 02:01 -0400, Joe Todaro wrote:
> >
> > Hi,
> >
> > Has anyone ever seen a yum/depsolve-related error like this before
in
> > their *plague-0.5.0* build environment, and then tried *killing*
the
> > job that had caused it? This was problem three of three which I
had
> > mentioned in my previous posts. And it too had surfaced last
week
> > while we started stress-testing our buildsystem. Actually, the
error
> > you see below in itself was *not* the problem (we knew how to fix
> > that) -- rather, it was the fact that we were *unable* to kill the
job
> > (plague-client kill 204) that was responsible for causing the
error.
>
> Can you tell me a few things about your plague server?
>
> 1) What version of yum is it running?
yum-2.4.2-2
> 2) What version of yum-utils if any?
yum-utils-0.5-1.c4
> 3) the output of:
>
> rpm -qf /usr/lib/python2.3/site-packages/repomd/mdErrors.py
yum-2.4.2-2
> rpm -qf /usr/lib/python2.4/site-packages/repomd/mdErrors.py
error: file /usr/lib/python2.4/site-packages/repomd/mdErrors.py: No
such file or directory
>
> 4) Next, can you try:
>
> python
> >>> import repomd.mdErrors
> >>> repomd.mdErrors.PackageSackError
Python 2.3.4 (#1, Feb 6 2006, 10:38:45)
[GCC 3.4.5 20051201 (Red Hat 3.4.5-2)] on linux2
Type "help", "copyright", "credits" or "license"
for more
information.
>>> import repomd.mdErrors
>>> repomd.mdErrors.PackageSackError
<class repomd.mdErrors.PackageSackError at 0x2a955e80b0>
>>>
>
> 5) Then try:
>
> python
> >>> import yum
> >>> yum.Errors.PackageSackError
Python 2.3.4 (#1, Feb 6 2006, 10:38:45)
[GCC 3.4.5 20051201 (Red Hat 3.4.5-2)] on linux2
Type "help", "copyright", "credits" or "license"
for more
information.
>>> import yum
>>> yum.Errors.PackageSackError
Traceback (most recent call last):
File "<stdin>", line 1, in ?
AttributeError: 'module' object has no attribute 'PackageSackError'
>>>
Ok, that tells me what I need to know. I think we need to
conditionalize the except statements from around the line in which you
were having the error. I'll see what I can do.
Dan
>
>
> I think this is an issue of the yum depsolve stuff moving from
yum-utils
> to yum itself, we just need to figure out what the permutations are
and
> then work around them in the source.
>
>
> Thanks,
> Dan
Thank You,
Joe
>
> > ====== THE ERROR ======
> > 204 (fuse-sshfs): Starting tag 'fuse-sshfs-1_6-4_ocrhel4' on
target
> > 'oc-rhel4-pre'
> > 204 (fuse-sshfs): Requesting depsolve...
> > 204 (fuse-sshfs): Starting depsolve for arches: ['x86_64',
'i386',
> > 'i686'].
> > Exception in thread PackageJob: 204/fuse-sshfs:
> > Traceback (most recent call last):
> > File "/usr/lib64/python2.3/threading.py", line 436, in
__bootstrap
> > self.run()
> > File "/usr/share/plague/server/PackageJob.py", line 86, in run
> > self._pkg_job.process()
> > File "/usr/share/plague/server/PackageJob.py", line 753, in
process
> > if func():
> > File "/usr/share/plague/server/PackageJob.py", line 618, in
> > _stage_depsolve
> > if self._arch_deps_solved(arch) == False:
> > File "/usr/share/plague/server/PackageJob.py", line 562, in
> > _arch_deps_solved
> > except yum.Errors.PackageSackError, exc:
> > AttributeError: 'module' object has no attribute
'PackageSackError'
> >
> > ====== OUR FIX ======
> > We updated line 680 in the *die* method of the
> > */usr/share/plague/server/PackageJob.py * module. Here's the
patch:
> >
> >
> > Again, can someone please review the fix.. We just want to make
sure
> > that it won't come back to *haunt* us later on / or possibly even
be
> > *masking* another problem. Thank you.
> >
> > -Joe
> > --
> > Fedora-buildsys-list mailing list
> > Fedora-buildsys-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
>