I was just playing around with resubmitting a job from the monitor, but since my job uses a custom plugin location, Deadline is unable to locate the plugin:
2014-06-10 09:13:21: Traceback (most recent call last):
2014-06-10 09:13:21: File "DeadlineUI\UI\Commands\JobCommands.py", line 2049, in InnerExecute
2014-06-10 09:13:21: DeadlineSubmissionException: plugin name specified by job, "LumaJob", is not a known plugin name.
2014-06-10 09:13:21: at Deadline.Controllers.DataController.SubmitJob (Deadline.Jobs.Job job, FranticX.Collections.Specialized.StringCollection2 auxiliarySubmissionFileNames, Boolean resetJobDefaults, Deadline.Jobs.TaskCollection taskCollectionOverride) [0x00000] in <filename unknown>:0
2014-06-10 09:13:21: at Deadline.Controllers.DataController.ResubmitJob (Deadline.Jobs.Job job, System.String frameList, Int32 chunkSize, Boolean submitSuspended, Boolean maintenanceJob, Int32 maintenanceJobStartFrame, Int32 maintenanceJobEndFrame) [0x00000] in <filename unknown>:0
2014-06-10 09:13:21: at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
2014-06-10 09:13:21: at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
Seems like resubmission should use the plugin from the same location as the job that is being resubmitted.
I am trying to reproduce this error. Did you submit the job with custom plugin location specified, or did you edit the Job after submission to use the custom plugin location?
It would appear this is an issue that affects both normal submission and resubmission. Our submission logic assumes that the plugin specified by the job exists in the repository, even if the job has specified an alternate location. So when Ryan and I (yes, there are two Ryans) were initially debugging this, we couldn’t even get the initial job to submit until we also a copy of our custom plugin in the repository. We just wanted to make sure this was the same behavior you were seeing.
Ideally, we should fix this so that if a job has a custom plugin path specified, the submission process would also check that folder during submission to make sure the plugin is valid.
Ah, OK. I had an entry point for the plugin in the repository initially, but then decided I didn’t want to use that approach due to issues with the slow and steady pollution of the slave’s Python environment, so I edited the job while it was on the farm to point to the custom plugin location and then removed the plugin loader from the repository.
That’s unfortunate, as that’s the way I would like to manage custom plugins here. Is there any way we could see a fix for this in a 6.2 patch release?
You could just stick an empty folder in the plugins folder in the repository with the appropriate name as a workaround. There currently aren’t any plans to release patches for 6.2, but the good news is that the issue has already been resolved for Deadline 7.