SAS Risk Cirrus Pods errors

luis_ruizg — Fri, 09 Aug 2024 04:35:07 GMT

Hello,

I have been doing update tasks getting from 2023.03 to 2023.10 on my viya environment and most of it seems to be correct except for a few pods related to something I haven't seen before and that I can't find any related information.

sas-risk-cirrus-core-XXXXXX

sas-risk-cirrus-rm-XXXXX

Those are getting on crashLoopBackOff state and

sas-risk-data-XXXX

gets stucked on Init:3/4 state

I get the followng error on logs:

sas-risk-cirrus-core

{"level":"error","version":1,"source":"sas-bootstrap-tool","messageKey":"sonder-log-icu.bootstrap.request.failed.detail.log","messageParameters":{"details":"{\"version\":2,\"httpStatusCode\":400,\"message\":\"The body member \\\"items.0.metadata.mediaType\\\" has an invalid value. (The specified value is \\\"application/vnd.sas.configuration.config.sas.workflow.client.riskcirrusbusinessobjectsservice+json;version=2\\\".)\",\"details\":[\"path: /configuration/configurations\",\"correlator: 848697af-e8f7-445e-bc55-984253778aab\"]}","errorCode":"400","request":"POST /configuration/configurations"},"properties":{"logger":"commons/bootstrap","caller":"bootstrap/bootstrap.go:656"},"timeStamp":"2024-08-09T04:12:42.624410+00:00","message":"sonder-log-icu.bootstrap.request.failed.detail.log [details:{\"version\":2,\"httpStatusCode\":400,\"message\":\"The body member \\\"items.0.metadata.mediaType\\\" has an invalid value. (The specified value is \\\"application/vnd.sas.configuration.config.sas.workflow.client.riskcirrusbusinessobjectsservice+json;version=2\\\".)\",\"details\":[\"path: /configuration/configurations\",\"correlator: 848697af-e8f7-445e-bc55-984253778aab\"]} errorCode:400 request:POST /configuration/configurations]"}
{"level":"error","version":1,"source":"sas-bootstrap-tool","messageKey":"Error bootstrapping resources: Bad Request","properties":{"logger":"tools/bootstrap","caller":"impl/tooling.go:125"},"timeStamp":"2024-08-09T04:12:42.624487+00:00","message":"Error bootstrapping resources: Bad Request"}
{"level":"error","version":1,"source":"sas-run-tool","messageKey":"Error executing sas-bootstrap-tool: exit status 1","properties":{"logger":"tools/run","caller":"impl/executor.go:174"},"timeStamp":"2024-08-09T04:12:42.626361+00:00","message":"Error executing sas-bootstrap-tool: exit status 1"}
{"level":"error","version":1,"source":"sas-run-tool","messageKey":"Tool executor failed running tools: exit status 1","properties":{"logger":"tools/run","caller":"impl/executor.go:63"},"timeStamp":"2024-08-09T04:12:42.626384+00:00","message":"Tool executor failed running tools: exit status 1"}
{"level":"fatal","version":1,"source":"sas-run-tool","messageKey":"Service executor failed to execute successfully: exit status 1","properties":{"logger":"tools/run","caller":"impl/tooling.go:132"},"timeStamp":"2024-08-09T04:12:42.626397+00:00","message":"Service executor failed to execute successfully: exit status 1"}

sas-risk.cirrus-rm

{"level":"warn","version":1,"source":"Risk Cirrus Deployer","timeStamp":"2024-08-09T04:27:30.988281+00:00","message": " SAS_RISK_CIRRUS_SOLUTION_BUILDER_REPO_USER environment variable is undefined", "properties": {"caller":"deploy-solution.sh:207"}}
{"level":"warn","version":1,"source":"Risk Cirrus Deployer","timeStamp":"2024-08-09T04:27:31.092710+00:00","message": " SAS_RISK_CIRRUS_SOLUTION_BUILDER_REPO_TOKEN environment variable is undefined", "properties": {"caller":"deploy-solution.sh:213"}}
{"level":"warn","version":1,"source":"Risk Cirrus Deployer","timeStamp":"2024-08-09T04:27:31.196645+00:00","message": " SAS_RISK_CIRRUS_SOLUTION_BUILDER_REPO_HOST environment variable is undefined", "properties": {"caller":"deploy-solution.sh:219"}}
{"level":"warn","version":1,"source":"Risk Cirrus Deployer","timeStamp":"2024-08-09T04:27:31.305300+00:00","message": " SAS_RISK_CIRRUS_SOLUTION_GIT_REPO_FULL_URL environment variable is undefined", "properties": {"caller":"deploy-solution.sh:231"}}
{"level":"error","version":1,"source":"Risk Cirrus Deployer","timeStamp":"2024-08-09T04:27:31.411798+00:00","message": "Failed to deploy due to missing SAS_RISK_CIRRUS_SOLUTION_BUILDER_REPO_* variables.", "properties": {"caller":"deploy-solution.sh:238"}}
{"level":"error","version":1,"source":"Risk Cirrus Deployer","timeStamp":"2024-08-09T04:27:31.515712+00:00","message": "Check deployment kustomizaton to ensure parameters are provided.", "properties": {"caller":"deploy-solution.sh:239"}}
{"level":"error","version":1,"source":"sas-run-tool","messageKey":"Tool executor failed starting service: exit status 1","properties":{"logger":"tools/run","caller":"impl/executor.go:67"},"timeStamp":"2024-08-09T04:27:31.600401+00:00","message":"Tool executor failed starting service: exit status 1"}
{"level":"fatal","version":1,"source":"sas-run-tool","messageKey":"Service executor failed to execute successfully: exit status 1","properties":{"logger":"tools/run","caller":"impl/tooling.go:132"},"timeStamp":"2024-08-09T04:27:31.600423+00:00","message":"Service executor failed to execute successfully: exit status 1"}

sas-risk-data

Defaulted container "sas-risk-data" out of: sas-risk-data, sas-start-sequencer (init), sas-certframe (init), hydrator (init), sas-db-migrator (init)
Error from server (BadRequest): container "sas-risk-data" in pod "sas-risk-data-b5fd8fc87-m9bxt" is waiting to start: PodInitializing

Any idea on what could be causing this?

Re: SAS Risk Cirrus Pods errors

sasefj — Fri, 09 Aug 2024 17:43:01 GMT

Please see if the info at this link is helpful: https://go.documentation.sas.com/doc/en/itopscdc/v_045/itopswn/n0irzuo0igfm1jn168t8pbgsj5b5.htm (Changes to SAS Risk Modeling Requirements LTS 2024.10 What's New topic).

Re: SAS Risk Cirrus Pods errors

luis_ruizg — Fri, 09 Aug 2024 19:03:23 GMT

Yes, I have followed all the steps mentioned on that documentation and on deploy/sas-bases/docs/preparing_and_configuring_risk_cirrus_core_for_deployment.htm with no luck

Re: SAS Risk Cirrus Pods errors

ahmedaldorr — Sun, 13 Oct 2024 09:20:39 GMT

I have the same issue, have you identified a solution?

Re: SAS Risk Cirrus Pods errors

luis_ruizg — Mon, 14 Oct 2024 18:09:43 GMT

In my case I wasn't able to identify exactly what happened. What I noticed was that it seemed that I needed another stateful node, because I only had one. This change plus many other things lead me to the correct pod initialization. Hope this help a bit.

topic Re: SAS Risk Cirrus Pods errors in Administration and Deployment

SAS Risk Cirrus Pods errors

Re: SAS Risk Cirrus Pods errors

Re: SAS Risk Cirrus Pods errors

Re: SAS Risk Cirrus Pods errors

Re: SAS Risk Cirrus Pods errors