deadline 5 install anomaly

Deadline
1

We were upgrading to deadline 5 today and wanted to inquire about an anomaly we noticed.

when we installed deadline 5 client on our render nodes we noticed it would only run the slave as deadline 4.1 even though we had removed 4.1
we had to change our old repository to not automatically update in order for deadline 5 to stay installed on the nodes.
we wanted to leave the old repository present until the new one was up and running in at least a test state to ensure we had a setup to fallback on if the upgrade failed.

I just wanted to let people know our experience as the reversion from 5 to 4.1 was only indicated by a very brief flash in the system tray notifying us of the “automatic update”

let me know if you would like further details about this and I will provide what I can.

thanks

2

When you installed the Deadline 5 client, did you change the repository path to point to your v5 repository, or were they still pointing to the old v4.1 repository? If it’s the latter, then it would make sense that the slaves would “upgrade” themselves back to 4.1 if automatic updates was enabled. The automatic update feature checks the bin folder in the repository, and if it contains a different set of binaries, the update will be invoked.

I should note that having different versions of clients connecting to a repository is not supported, especially in the case of 4.x and 5.0. This is because of the changes made to the job folder structure for 5.0.

Cheers,

  • Ryan