What does "Duplicate variable" mean in the verbose output when deploying a package?

I was trying to track down an problem with variables so turned on Verbose output. The first messages for the package are:

Octopus Server version: 3.2.20+Branch.master.Sha.3ba3880bd0e212cf37dbf019d6def796f3a1710a
09:53:44Info
Deploying package ‘C:\Octopus\Files\FreightHub.Online.1.0.12.nupkg-f7719d69-ba59-48bb-9d35-8af865bd52d1’ to machine 'https://54.79.109.67:10933/'
09:53:44Verbose
You have a duplicate variable ‘IIS.BindingIPAddress’ between the Step Template used in the ‘Deploy FreightHub.Online’ step and your Project or Variable Sets in use. Be aware that the latter will prevail over the values entered on the step.
09:53:44Verbose
You have a duplicate variable ‘IIS.InstallFolder’ between the Step Template used in the ‘Deploy FreightHub.Online’ step and your Project or Variable Sets in use. Be aware that the latter will prevail over the values entered on the step.

What does this actually mean? I can’t find any help on it and want to know if I have a problem with my project.
Thanks.
Rick.

Hi Rick,

Thanks for reaching out!

When you create a step template with parameters, these parameters are in the background Octopus and Powershell variables. If you have a variable with that exact same name in your project, you’ll get this warning and during the deployment the project variable value will prevail.

See attached screenshots for visual reference.

Hope that helps,
Dalmiro

Hi Dalmiro, thanks for your response. That makes sense except that I don’t have any step templates (see attached).
I did copy this project from another one so maybe it has something to do with that?
Thanks again.
Rick.

Hi Rick,

Hmm you shouldn’t be getting that message if you are not using Step Templates. Would you please follow the below steps to provide a verbose log? I’d like to see what’s going on during that deployment in more depth

1) Add these 2 variables to your project http://docs.octopusdeploy.com/display/OD/Debug+problems+with+Octopus+variables

2) Create a new release (so the new variables take effect) and deploy it. If possible skip as many steps as you can and only leave step we are troubleshooting in order to avoid the noise in the log.

3) Send us the raw log of that deployment http://docs.octopusdeploy.com/display/OD/Get+the+raw+output+from+a+task

Also please let me know the exact version of Octopus that you are running.

Best regards,
Dalmiro