Bug 112649

Summary:	Catalyst 2 raises traceback after uncleanly interrupted run
Product:	Gentoo Hosted Projects	Reporter:	Danny van Dyk (RETIRED) <kugelfang>
Component:	Catalyst	Assignee:	Gentoo Catalyst Developers <catalyst>
Status:	RESOLVED CANTFIX
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Danny van Dyk (RETIRED) gentoo-dev

2005-11-15 14:40:33 UTC

i just had a disconnect from poseidon, and had to kill my screen
afterwards. Anyway... cat2 was interrupted, and my first attempt to
rerun it produced this output:

<snip>
Checking for processes running in chroot and killing them.
/proc is still mounted; performing auto-bind-umount...
Catalyst aborting....
Traceback (most recent call last):
~  File "/usr/bin/catalyst2", line 354, in ?
~    build_target(addlargs, targetmap)
~  File "/usr/bin/catalyst2", line 197, in build_target
~    mytarget.mount_safety_check()
~  File "/usr/lib/catalyst2//modules/generic_stage_target.py", line 464,
in mount_safety_check
~    self.unbind()
~  File "/usr/lib/catalyst2//modules/generic_stage_target.py", line 684,
in unbind
~    self.snapshot_lock_object.unlock()
AttributeError: livecd_stage1_target instance has no attribute
'snapshot_lock_object'
</snip>

The second run started normally, just like expected. However, i don't
think the traceback here was intended, was it?

Comment 1 Chris Gianelloni (RETIRED) gentoo-dev

2005-12-20 09:31:41 UTC

Well, there are a *ton* more tracebacks in catalyst 2.0 to help us troubleshoot possible issues.  Since this isn't something we can really reproduce, I'm going to say this is a CANTFIX.  As for the tracebacks, I'm pretty sure that catalyst now spits one out for *any* unexpected failures.

Comment 2 Danny van Dyk (RETIRED) gentoo-dev

2005-12-22 15:09:45 UTC

*nod*

I just filed this bug because rocket asked me to do ;-)