id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
1171	Nebulous issues with missing files	eugene	eugene	"I had some trouble dealing with files that were on ipp027, but were lost when the raid was rebuilt.  Most files had been replicated, but a handful of the detrend images (from detRegisteredImfile) were missed.  I tried to re-build these by removing their detRegisteredImfile entries and resetting the detRun state to 'run'.  This re-triggered the analysis used to build those files, but caught a problem with the interaction with nebulous.  As far as I can tell, the following was happening:

* there was already an output file with the corresponding ext_id in nebulous (eg, gpc1/flatcorr.20081107/GPC1.FLAT.86/GPC1.FLAT.86.XY23.co.fits).  

* in addition, the nebulous object had a single associated instance on ipp027.  

* if ipp027 was marked available (but not 'allocate'), nebulous attempted to supply that instance to the calling program. it did not exist, so this operation failed. 

* when I disabled 'available' for ipp027, nebulous now reported 'no instance available'.

This seems like the right behavior IF I had been requesting a file for 'read', but since I was trying to create a new file, this does not seem right.  In the end, I had to delete (in sql, since I was a little nervous about neb-rm) the nebulous entry for the file."	enhancement	new	high		Nebulous	unspecified	minor