Viya 4 Model Manager URL The application is currently not serving requests at this endpoint. it may

[alko13]

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.

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

Appreciate any suggestions.

Thanks!

[alexal]

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

[alko13]

Hi @alexal 

Yes, we have Model Manager in our order.

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

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

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

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]

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]

May I know the steps for the workaround?

Thanks in advance

[DawnSchrader · Accepted solution]

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]

@DawnSchrader 

Issue resolved after applying the scc.

Thanks a lot!