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-1677582302967.png

 

 

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

 

Appreciate any suggestions.

 

Thanks!

 

1 ACCEPTED SOLUTION

Accepted Solutions
DawnSchrader
SAS Employee

If you've used the other 'oc adm' command to associate serviceaccounts with the SCCs, then I think the command would be similar:

oc -n name-of-namespace adm policy add-scc-to-user hostmount-anyuid -z default

 

This SCC should already exist, so you can use that command or edit the rolebinding directly, so you end up with a subjects: entry for:

- kind: ServiceAccount
  name: default
  namespace: name-of-namespace

Notice that this change means you are granting elevated permissions to any pod that uses the 'default' service account and not just the model-repository pod.

View solution in original post

6 REPLIES 6
alexal
SAS Employee

Are you sure you have the SAS Model Manager in your order?

alko13
Quartz | Level 8

Hi @alexal 

 

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

 

 

 

 

 

DawnSchrader
SAS Employee

Hi - that problem is most likely to occur if you've also enable the python-transformer.yaml in sas-bases/examples/sas-model-repository/python.

That transformer mounts an NFS location and OpenShift requires additional permissions to allow that.

There is a change planned for 2023.03 to prevent the issue. Prior to that change, as a workaround internally for testing, we have been adding the 'default' serviceaccount to a rolebinding or clusterrolebinding to associate it with the hostmount-anyuid SCC.

 

alko13
Quartz | Level 8
May I know the steps for the workaround?

Thanks in advance
DawnSchrader
SAS Employee

If you've used the other 'oc adm' command to associate serviceaccounts with the SCCs, then I think the command would be similar:

oc -n name-of-namespace adm policy add-scc-to-user hostmount-anyuid -z default

 

This SCC should already exist, so you can use that command or edit the rolebinding directly, so you end up with a subjects: entry for:

- kind: ServiceAccount
  name: default
  namespace: name-of-namespace

Notice that this change means you are granting elevated permissions to any pod that uses the 'default' service account and not just the model-repository pod.

alko13
Quartz | Level 8

@DawnSchrader 

 

Issue resolved after applying the scc.

 

Thanks a lot!

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 6 replies
  • 1358 views
  • 0 likes
  • 3 in conversation