BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
alko13
Quartz | Level 8

Hi,

This is a new Installation of Intelligent Decisioning over Viya 4. All pods are in Completed/Running State.

However, When accessing Model Manager URL. It displays below windows only: 

 

The application is currently not serving requests at this endpoint. it may have been started or is still starting.

 

alko13_0-1677582133613.png

 

I checked the sas-model-repository pod. Seems it is missing.

 

Appreciate any suggestions.

 

Thanks!

 

1 ACCEPTED SOLUTION

Accepted Solutions
DeanTaplin
SAS Employee

@alko13 The sas-model-repository pod fails to start on OpenShift. It is necessary to perform a workaround. Please try these steps and let me know if that works.

kubectl edit clusterrolebinding system:openshift:scc:hostmount-anyuid
added kind: ServiceAccount   name: default   namespace:     (put your namespace name here)

Then scale down sas-model-repository pod and then scale back up.

View solution in original post

4 REPLIES 4
DeanTaplin
SAS Employee

Can you confirm what offerings are included in your Viya 4 order, does it include SAS Model Manager?

alko13
Quartz | Level 8

@DeanTaplin 

 

Yes, we have Model Manager in our order.

 

In our deployment, we got this sas-model-repository with 0/1

 

alko13_0-1677659632880.png

 

This is the describe output of the sas-model-repository deployment

 

alko13_1-1677659727549.png

 

 

Have describe the replicaset and it is giving this message. Got idea?

 

alko13_2-1677659751318.png

 

Btw, we are using Redhat Openshift. and we also already ran this security context and service accounts as described here https://documentation.sas.com/doc/en/itopscdc/v_031/dplyml0phy0dkr/p1h8it1wdu2iaxn1bkd8anfcuxny.htm

 

Thanks

 

 

 

 

 

DeanTaplin
SAS Employee

@alko13 The sas-model-repository pod fails to start on OpenShift. It is necessary to perform a workaround. Please try these steps and let me know if that works.

kubectl edit clusterrolebinding system:openshift:scc:hostmount-anyuid
added kind: ServiceAccount   name: default   namespace:     (put your namespace name here)

Then scale down sas-model-repository pod and then scale back up.

alko13
Quartz | Level 8

@DeanTaplin 

 

Issue resolved after applying the workaround.

 

Thanks a lot!