3.17.3 broke deployments

Legacy Execution
1

We upgraded to 3.17.3 and could no longer deploy to a tenant. Rolling back to 3.17.2 fixed the problem. Here is the deployment log:

Task ID:        ServerTasks-48143
Task status:    Failed
Task queued:    Tuesday, October 3, 2017 9:06 AM
Task started:   Tuesday, October 3, 2017 9:06 AM
Task duration:  less than a second
Server version: 3.17.3+Branch.master.Sha.6b3c769781795c5e8091d139bf14823c71abec72
Server node:    OCTOPUSDEPLOY3

                    | == Failed: Deploy Galileo - Next release 2.13.0-v213-6582a to Galileo - QA for QA - Unstable ==
09:06:41   Verbose  |   Step 2: E2E - Restore Database does not apply to the current tenant due to missing tenant tags and will not be executed
09:06:41   Verbose  |   Step 6: Stop Build Service on Inactive App Node does not apply to the current tenant due to missing tenant tags and will not be executed
09:06:41   Verbose  |   Step 8: E2E - Run Tests does not apply to the current tenant due to missing tenant tags and will not be executed
09:06:41   Fatal    |   Exception occured while executing a reader for `SELECT * FROM dbo.[TagSet] ORDER BY [Id]`
                    |   The ConnectionString property has not been initialized.
                    | 
                    |   == Pending: Acquire packages ==
                    |   
                    |   == Pending: Step 1: Deploy Galileo ==
2

HI,

Thanks for reaching out. We found this bug earlier today and had to pull this build out of rotation because of it. The recommended workaround is to rollback to 3.17.2 just like you did.

We already have a github issue logged for it which you can track over here: https://github.com/OctopusDeploy/Issues/issues/3838

Deep apologies for the inconveniences caused by this.

Best regards,
Dalmiro