Hello, I am trying to run MSSQL + Octopus in kubernetes, specifically in Openshift.
I have created MSSQL Service and mounted PVC to
I have also created Octopus Service and mounted 3 PVCs to
When MSSQL pod was up, I scalled Octopus. The database was created and I was given a Master Key. And then with following command I verified it:
/Octopus/Octopus.Server show-master-key --console --instance OctopusServer
After that, I have updated ENV variable MASTER_KEY=“PASTED_24_CHAR_MASTER_KEY”
Unfortunatelly, at the end I got following message and due to that pod restarts again and again:
Failed to decrypt the Octopus Server certificate. This usually indicates the wrong master key is being used to read encrypted data.
Here is part of the log:
======== Writing Configuration File =======
find: ‘/run/secrets/rhsm’: Permission denied
error: attempting to run rootless dockerd but missing ‘rootlesskit’ (perhaps the ‘docker:dind-rootless’ image variant is intended?)
Creating empty configuration file: /home/octopus/.octopus/OctopusServer/Server/Server.linux.config
Saving instance: OctopusServer
Setting home directory to: /home/octopus/.octopus/OctopusServer/Server
Setting server node name to ‘octopus’.
======== Initializing DB ========
Using supplied Master Key
Setting master key
Setting database connection string to: server=…MY_CONNECTION_STRING…
========== SQL Database Connection Details ========
SQL Server: CLUSTER_IP,1433
SQL Database: OctopusDeploy
Authentication Type: SQL Server Credentials
Testing connection to the ‘master’ database…
Successfully connected to ‘master’ database!
Database ‘OctopusDeploy’ already exists on SQL Server at ‘CLUSTER_IP,1433’, no need to create it.
Checking the Octopus Master Key has been configured.
Making sure it’s safe to upgrade the database schema…
Ensuring pre-conditions for upgrading the database are satisfied…
Searching for indexes that might upset the database upgrade process…
- PASS: All columns use the default collation.
- PASS: Your Octopus Server will be compliant with your license after upgrading.
- PASS: We’ve done our best to remove any unexpected database indexes.
- PASS: The version of your SQL Server satisfies Octopus Server installation requirements.
Executing always run pre scripts…
Executing TSQL Database Server script ‘Octopus.Core.UpgradeScriptsAlwaysPre.Script0000 - Set highest available compatibility level.sql’
Current COMPATIBILITY_LEVEL for OctopusDeploy is set to 140
Ensuring COMPATIBILITY_LEVEL for OctopusDeploy is set to 140
COMPATIBILITY_LEVEL for OctopusDeploy is already 140 or higher
Checking to see if database schema upgrade is required…
Database already has the expected schema. No changes are required.
Executing always run post scripts…
Executing TSQL Database Server script ‘Octopus.Core.UpgradeScriptsAlwaysPost.Script0000 - Refresh Views.sql’
Refreshing view dbo.Dashboard
Refreshing view dbo.IdsInUse
Refreshing view dbo.MultiTenancyDashboard
Refreshing view dbo.Release_WithDeploymentProcess
Refreshing view dbo.RunbookSnapshot_WithRunbookProcess
Refreshing view dbo.TenantProject
Process reader took 806ms in transaction ‘ThrowIfOctopusServerHasBeenDowngraded’: SELECT TOP 1 *
WHERE ([Version] is not null)
ORDER BY [Installed] DESC
Process reader took 499ms in transaction ‘BuiltInTeamInitializer’: SELECT TOP 1 * FROM [dbo].[UserRole] WHERE [Id] = @Id
Update took 395ms in transaction ‘BuiltInTeamInitializer’: UPDATE [dbo].[UserRole] SET [Name] = @Name, [JSON] = @JSON WHERE [Id] = @Id
Process reader took 697ms in transaction ‘BuiltInTeamInitializer’: SELECT TOP 1 * FROM [dbo].[Team] WHERE [Id] = @Id
Failed to decrypt the Octopus Server certificate. This usually indicates the wrong master key is being used to read encrypted data.`