Installed Octopus 2020.1

(Raf) #1

Hi, we downloaded and installed Octopus 2020.1 and some deployments are failing. We’d like to downgrade without risking the healthy deployments.

Cheers

(Justin Walsh) #3

Hi @raf1

Thanks for reaching out, and sorry to hear you’re having issues post-upgrade. Are you able to shed any light on what deployments are failing? We fixed a bug with azure deployments earlier today, in 2020.1.5, which may lessen the need for a rollback.

Rolling back your upgrade is possible, either from your pre-installation backup, or by rolling back to 2019.13.6. If you roll back to 2019.13.6, you may need to make some manual database tweaks. Obviously, before making any changes/performing a rollback, please be sure to ensure you have working backups of your database, master key, and filesystem.

Remove the 2020.1 row in dbo.OctopusServerInstallationHistory
Drop the following tables:

Script0239ScopedUserRole
Script0239Team
Script0239User
Script0239UserRole

I hope this helps.

(Raf) #4

Hi yes, this is the error message, it’s now asking for bash.exe:

Deploying package:    C:\Octopus\OctopusServer\PackageCache\feeds-teamcity-packages\OURPACKAGE@uid@puid.nupkg 
March 20th 2020 09:46:35Error
Unable to execute C:\Windows\system32\bash.exe, please ensure that C:\Windows\system32\bash.exe is installed and is in the PATH. 
March 20th 2020 09:46:35Error
System.Exception: Error when attempting to execute C:\Windows\system32\bash.exe: The system cannot find the file specified ---> System.ComponentModel.Win32Exception: The system cannot find the file specified 
March 20th 2020 09:46:35Error
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) 
March 20th 2020 09:46:35Error
   at Calamari.Integration.Processes.SilentProcessRunner.ExecuteCommand(String executable, String arguments, String workingDirectory, Dictionary`2 environmentVars, String userName, SecureString password, Action`1 output, Action`1 error) 
March 20th 2020 09:46:35Error
   --- End of inner exception stack trace --- 
March 20th 2020 09:46:35Error
   at Calamari.Integration.Processes.SilentProcessRunner.ExecuteCommand(String executable, String arguments, String workingDirectory, Dictionary`2 environmentVars, String userName, SecureString password, Action`1 output, Action`1 error) 
March 20th 2020 09:46:35Error
   at Calamari.Integration.Processes.CommandLineRunner.Execute(CommandLineInvocation invocation) 
March 20th 2020 09:46:35Error
The command that caused the exception was: "C:\Windows\system32\bash.exe" "Bootstrap.c38-4167-9240-2a493e90c5e1.Octopus.AzureContext.sh" "7FDC3E6CCF25E4F8624A63AEE8D6A939" 
March 20th 2020 09:46:35Error
Script 'C:\Octopus\Work\20200319204621-122846-12\staging\deploy.sh' returned non-zero exit code: -1. Deployment terminated. 
March 20th 2020 09:46:35Error
Running rollback conventions... 
March 20th 2020 09:46:35Error
Script 'C:\Octopus\Work\20200319204621-122846-12\staging\deploy.sh' returned non-zero exit code: -1. Deployment terminated. 
March 20th 2020 09:46:38Fatal
The remote script failed with exit code 1 
March 20th 2020 09:46:38Fatal
The action Deploy OURPACKAGE on OURAPP Azure Web App failed 

(Justin Walsh) #5

Hi @Raf1,

Thanks for getting back to me, this definitely sounds like a bug. I’ll bring this up with our team, and get this sorted out for you ASAP.

I’ll circle back around with you when I have any further updates.

(Justin Walsh) #6

Hi @raf1

Just a quick update here that we’ve got an issue for this, and we’ve committed to better handle the script extension priority order based on the OS being deployed to.

(Raf) #7

Thank you Justin,

I had a post deployment script in the Azure WebApp that was in bash, I converted to PowerShell and it started working again.