Deadline Server 10.4.1.8: LimitGroups Error

Deadline
1

Hello,
after upgrading to 10.4.1.8, the Deadline Server does not seem to support multiple LimitGroups anymore in job submissions.

When submitting jobs with LimitGroups=group1,group2 I get:

Error: Object reference not set to an instance of an object. (System.NullReferenceException)

Using only one LimitGroups=group1 works without issues.
This is the same issue whether submitting through deadlinecommand in rcs or the rest api.

I’ve tried this on a brand new installation with clean configurations.

I tried it with the latest version of mongodb 6.0.24.
I reproduced it broken with Deadline 10.4.1.8 and working with 10.4.0.13.

1 Like
2

I’ve just tested this and found the same issue

image
Job seems to submit but doesn’t appear in Monitor
image

Removing a limit allows the job to be submit again
image

I wonder if this is to do with the updated UBL options now including DeadlineCloud, these can’t be mixed with Legacy MarketPlace UBL, so possibly this safeguard is breaking it
image
(neither of my limits include UBL)

3

We are getting exactly the same issue over here.

I was able to reachout AWS and they told me the engineering have just confirmed they can reproduce the issue and ticket has been raised.

That being said, the only workaround I found was to set the LimitGroups through deadline command.

deadlinecommand SetJobSetting <JOBID> LimitGroups “myLimit,myOtherLimit”

Here we didnt move our Production to 10.4 yet, we are only testing it in our Lab. So we are waiting for the fix.
But since we were using UBL for Cloud Rendering, if the issue isn’t resolved my stupid workaround would be to create an Event OnJobSubmitted that adds the limitgroups through deadlinecommand…

1 Like
4

https://docs.thinkboxsoftware.com/products/deadline/10.4/1_User%20Manual/manual/release-notes.html#deadline-release

  • Fixed a bug preventing resource limits being applied to jobs
  • Fixed a UI bug when creating resource limits
  • Fixed a bug preventing the repository settings window from opening in the Monitor
5

10.4.1.9 brings another issue related to Limits that AWS is already aware of.

They suggest to wait for .10 and ignore .9

I’m quoting what I was told:

I’m a little sad to report that after a bunch of additional testing, I was able to produce a slightly different but related limits error. We just got that fixed and I did a 3rd round of testing with this new-new fix and now, everything looks to be good. “Limits” is a rather complicated section of source code for us, not an excuse but being honest here. As a result, don’t bother testing 10.4.1.9 and we are prep’ing a newer release now. I’ll ping again once its published.

1 Like
6

Really appreciate your updates @sbissonnette0! I was already excited this morning but we’ll wait for 10.4.1.10.
Thank you

7

10.4.1.10 just came out.

We can start testing and see if this is finally resolved!

1 Like
8

Just tested and this seems to be working now!

9

YESSS! Team SSA for the win

2 Likes