This SAS KB article contains structured instructions for diagnosing and resolving problems in SAS Container Runtime. The information in this article will help you define the problem clearly, collect essential diagnostic data, and identify the next steps toward resolution. 

The sections below outline standard data collection practices along with key questions to help define and scope the problem effectively. Establishing a detailed and complete problem description early in the investigation process can significantly reduce time to resolution. 

Define the Problem

SAS Container Runtime problems typically fall into two categories:

• SAS Container Runtime image creation
• SAS Container Runtime execution

Use the questions below to clearly define the problem before collecting diagnostic data.

Context and Observations

• What were you doing when the problem first occurred?
• Did you create a SAS Container Runtime image or run it?

Error or Unexpected Behavior

• Was an error message displayed?
  • If yes, provide the full message and a screenshot if possible.
  • If no error was displayed, what unexpected behavior occurred?
• What occurred versus what did you expect? 

Steps to Reproduce

• What sequence of steps led to the problem?
• Can you reproduce the issue consistently?

Scope of Impact

• Does this issue occur for all SAS Container Runtime images or only specific ones?
• Does this issue affect all users or only certain users (if the issue occurs during SAS Container Runtime creation)?
• Does the issue occur after only a certain amount of concurrent user load? If so, what is the minimum user load that reproduces the issue?

History and Changes

• Has this worked previously? If so, when was it last successful?
• Were there any recent changes? (For example, deployments, updates, configuration changes, data changes, changes to the base SCR image, or Kubernetes node resources.)

Diagnostic Data to Collect

To support resolution, collect the following diagnostic data at the time that the problem occurs.

Issue: SAS Container Runtime Image Creation

• output from the get-k8s-info script (SAS KB0038941)
• logs from the sas-model-publish pod (if the get-k8s-info script output is not available):
  
  kubectl -n <namespace> logs sas-model-publish-xxxxxxxx
  
  
• description of the publishing destination
  Note: If you created the publishing destination using the sas-viya command line interface (CLI) tool, provide the command that you used.
  
  
• screenshots of observations, errors, or unexpected results

Issue: Running the SAS Container Runtime Image

• container logs:
  
  kubectl -n <namespace> logs <SCR pod name>
  
  If the container runs on Docker or another platform, fetch the logs by using the command supported by that platform. (For example, oc logs for OpenShift)
  
  
• pod description (Kubernetes only):
  
  kubectl -n <namespace> describe pod <SCR pod name>
  
  
• connectionstring used in db.secret (only if related to database access)
  Note: Remove any sensitive information before sharing
  
  
• collect the environment variables from the running SCR pod

Providing complete diagnostic data in advance can significantly reduce time to resolution. 

Next Steps: Navigate Resolution Paths

Once you clearly define the problem and collect diagnostic data, engage SAS Technical Support for further assistance. Provide the detailed and complete problem description along with the prescribed diagnostic data.