topic Cannot connect to the CAS compute context after version update Sasviya in Administration and Deployment

Cannot connect to the CAS compute context after version update Sasviya

gbl13 — Tue, 03 Jun 2025 19:41:29 GMT

Hello.
I've downloaded the deployment assets of lts 2025.03 version of Sasviya and i've deployed it using kubernetes cli, overriding sas-bases assets, kubectl build and kubectl apply.

My version changed as well, but i'm receiving a context error like:

When i check the orchestrator logs i can find:
Unique Constraint Exists Precondition: JOB_COMMAND_ARGUMENT_UK01 on JOB_COMMAND_ARGUMENT : Found multiple catalogs matching sharedservices\n\n\t

I took a look on my postgresql and i have 2 'sharedservices' databases created, but i dont know how to proceed to solve this.

Could someone help me ?

Thanks!

Re: Cannot connect to the CAS compute context after version update Sasviya

gbl13 — Wed, 04 Jun 2025 20:27:35 GMT

Additional information:

I've followed these tutorials:

SAS Help Center: Apply a Patch Update Using Kubernetes Commands
SAS Help Center: Deploy the Software

Found multiple catalogs matching sharedservices\n\n\tat com.sas.convoy.db.migra
tor.DBMigrator.migratePostgresDb(DBMigrator.java:92)\n\tat com.sas.convoy.db.migrator.DBMigratorCli.doRun(DBMigratorCli.java:81)\n\tat com.sas.convoy.db.migr
ator.DBMigratorCli.main(DBMigratorCli.java:37)\n","properties":{"logger":"sas.db.migration","thread":"main"}}
{"level":"error","version":1,"source":"sas-db-migrator","messageKey":"Error during database migration: exit status 1","properties":{"caller":"src/main.go:88"
},"timeStamp":"2025-06-04T20:20:10.237681+00:00","message":"Error during database migration: exit status 1"}

Re: Cannot connect to the CAS compute context after version update Sasviya

EyalGonen — Thu, 05 Jun 2025 04:27:57 GMT

Did you update your SAS Viya version or is this a new deployment?

If you updated, did you read and follow the Deployment Notes for each of the versions you updated? For example if you updated from Stable 2025.01 to Stable 2025.03 you need to follow the Deployment Notes of both 2025.02 and 2025.03 when updating.

I think you might want to contact Technical Support for help in resolving this.