Cannot deploy to a tenant if the project has an account variable that is not used by the deployment process

[ryanrousseau]

Team

• [X] I've assigned a team label to this issue

Severity

Found internally - unknown if there is a workaround

Version

Earliest tried was 2022.3 build 2617-hotfix.4278

Latest Version

No response

What happened?

My project has a runbook that uses the Octopus.Azure.Account variable.

When trying to deploy a release from that project to a tenant, I get the message that the tenant is not authorized to use the account, even though the process doesn't use the account and the variable is scoped to the runbook processes specifically. The runbooks are not tenanted.

Reproduction

1. Create a project with tenanted deployments.
2. Create a non-tenanted runbook process.
3. Add an Azure account variable and scope it to the runbook process.
4. Try to deploy a release to a tenant.
5. See error message related to the unused account variable.

Error and Stacktrace

No response

More Information

No response

Workaround

No response

[garrettdass]

Another customer occurrence of this issue here: Internal Zendesk

[laurie-kepford]

I have this same issue. The only workaround was to change the account that I am NOT using in this runbook, to be tenanted. This is not ideal, because this account is supposed to be used for infrastructure only.

[AdamHollow49]

https://octopus.zendesk.com/agent/tickets/191607

Another customer is running into this issue here