Challenges in Deploying SAS Viya 4 on OpenShift vSphere

[etrock]

I am currently facing significant challenges while attempting to deploy SAS Viya on an OpenShift vSphere environment. As a newcomer to this ecosystem, I am finding it difficult to advance due to several problems that I will outline below. The most pressing issue is that the deployment status does not progress beyond BLANK STATE.

[root@masterocp ~]# oc -n sas-viya get sasdeployment
NAME       STATE   CADENCENAME   CADENCEVERSION   CADENCERELEASE   AGE
sas-viya           lts           2023.10                           7h13m

Environment and Configuration

To provide some context, I have not made any modifications to the standard requirements for the OpenShift installation. Consequently, my setup consists of a three nodes that works as a masters and workers. 

[root@masterocp ~]# oc get nodes
NAME    STATUS   ROLES                         AGE   VERSION
nodo1   Ready    control-plane,master,worker   9d    v1.25.16+5c97f5b
nodo2   Ready    control-plane,master,worker   9d    v1.25.16+5c97f5b
nodo3   Ready    control-plane,master,worker   9d    v1.25.16+5c97f5b

[root@masterocp ~]# oc adm top nodes
NAME    CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%   
nodo1   446m         5%     5615Mi          29%       
nodo2   1149m        15%    10611Mi         56%       
nodo3   1311m        17%    14231Mi         75% 

Problem Description

1. Deployment Status Stuck at BLANK:

   • The deployment status remains stuck at BLANK, indicating that the deployment process is not advancing as expected. This is a critical roadblock that prevents further progress.

2. Logs Provide Limited Insight:

   • The logs generated by the deployment operator do not offer much information that could help diagnose the issue. The lack of detailed error messages or warnings makes it challenging to identify the root cause of the problem.

[root@masterocp ~]# kubectl logs -n sasoperator sas-deployment-operator-7865978cdd-vkk47

{"level":"info","version":1,"source":"sas-orchestration","messageKey":"sas-orchestration.command.started","messageParameters":{"name":"reconcile"},"properties":{"logger":"internal/apihelpers","caller":"apihelpers/apihelpers.go:44"},"timeStamp":"2024-06-14T14:45:52.934297+00:00","message":"The reconcile command started"}
{"level":"info","version":1,"source":"sas-orchestration","messageKey":"sas-orchestration.command.started","messageParameters":{"name":"reconcile"},"properties":{"logger":"internal/cmd/reconcile","caller":"reconcile/reconcile.go:30"},"timeStamp":"2024-06-14T14:45:52.934429+00:00","message":"The reconcile command started"}
{"level":"info","version":1,"source":"sas-orchestration","messageKey":"sas-orchestration.version.version","messageParameters":{"version":"1.109.0"},"properties":{"logger":"pkg/globalflags/version","caller":"version/version.go:56"},"timeStamp":"2024-06-14T14:45:52.934457+00:00","message":"version     : 1.109.0"}
{"level":"info","version":1,"source":"sas-orchestration","messageKey":"sas-orchestration.version.buildDate","messageParameters":{"buildDate":"20231016.1697466963821"},"properties":{"logger":"pkg/globalflags/version","caller":"version/version.go:57"},"timeStamp":"2024-06-14T14:45:52.934466+00:00","message":"build date  : 20231016.1697466963821"}
{"level":"info","version":1,"source":"sas-orchestration","messageKey":"sas-orchestration.version.commitHash","messageParameters":{"commitHash":"fbcd110fc8a10884e8c9778f6f79965ce78adb5f"},"properties":{"logger":"pkg/globalflags/version","caller":"version/version.go:58"},"timeStamp":"2024-06-14T14:45:52.934475+00:00","message":"commit hash : fbcd110fc8a10884e8c9778f6f79965ce78adb5f"}
{"level":"info","version":1,"source":"sas-orchestration","messageKey":"sas-orchestration.version.goVersion","messageParameters":{"goVersion":"go1.21.3 X:boringcrypto"},"properties":{"logger":"pkg/globalflags/version","caller":"version/version.go:59"},"timeStamp":"2024-06-14T14:45:52.934483+00:00","message":"go version  : go1.21.3 X:boringcrypto"}
{"level":"info","version":1,"source":"sas-orchestration","messageKey":"sas-orchestration.version.goComplier","messageParameters":{"goCompiler":"gc"},"properties":{"logger":"pkg/globalflags/version","caller":"version/version.go:60"},"timeStamp":"2024-06-14T14:45:52.934490+00:00","message":"go compiler : gc"}
{"level":"info","version":1,"source":"sas-orchestration","messageKey":"sas-orchestration.version.goPlatform","messageParameters":{"goArch":"amd64","goOs":"linux"},"properties":{"logger":"pkg/globalflags/version","caller":"version/version.go:61"},"timeStamp":"2024-06-14T14:45:52.934505+00:00","message":"platform    : linux/amd64"}
I0614 14:45:53.985580       1 request.go:665] Waited for 1.043389733s due to client-side throttling, not priority and fairness, request: GET:https://172.40.0.1:443/apis/cloudcredential.openshift.io/v1?timeout=32s
I0614 14:45:55.291449       1 leaderelection.go:248] attempting to acquire leader lease sasoperator/sas-deployment-operator...
I0614 14:46:11.974259       1 leaderelection.go:258] successfully acquired lease sasoperator/sas-deployment-operator

I would appreciate some feedback to resolve this problem.

Thanks in advance.

[SASKiwi]

If you haven't done so yet, I'd advise opening a Tech Support track. AFAIK there are very few users on the Community with the specialist knowledge you require. By all means update your post so we can all learn from it.

[gwootton · Accepted solution]

I looks like your operator does not know that the sasdeployment object is there.

As your operator is in a different namespace than your sasdeployment object, did you deploy the SAS Deployment Operator in cluster-wide mode?

Deploy the SAS Viya Deployment Operator - Edit kustomization.yaml for Cluster-Wide Mode
https://go.documentation.sas.com/doc/en/sasadmincdc/v_045/dplyml0phy0dkr/n137b56hwogd7in1onzys95awxq...

[etrock]

Thank you very much @gwootton . That was the error of the deployment.  Now the state shows PENDING.