Attempts to upgrade VML projects fail or never end with "the project upgrade is taking longer than expected..."


After you upgrade your SAS Viya, some projects might need to be updated. 

When you proceed with the update, the procedure might not finish, or the following message might be displayed:

"The project upgrade is taking longer than expected. The upgrade will continue in the background. You can open the project after the upgrade completes."

Workaround

If the issue is caused by an inconsistent value of the "projectStatus" parameter related to the project, complete the following steps to circumvent the problem:

  1. Direct call to the project involved with the following URL: <<hostname>>/analyticsGateway/projects/<<project ID>>

  2. Find "Status". If the status is "projectStatus":"upgrading", complete the following UPDATE query into Postgres DB:
    UPDATE analytics_projects.project SET status_txt = 'NEEDS_UPGRADE' WHERE project_id = '<INSERT_PROJECT_ID_HERE>';

  3. After you make this update, the project involved is available to be opened.

Note: Here the instructions to connect to internal Postgres DB.

Connect to the cluster where the namespace is with the Postgres service. Then, use the CLUSTER admin account and as follows:

  1. Exec into the pod:
    kubectl exec -it $(kubectl get pods --no-headers -l postgres-operator.crunchydata.com/role=master -o custom-columns=:metadata.name) -c database - - bash2)

  2. Then, enter the following: 

psql
\c SharedServices

Here is an example of the above steps:

[user@trck63 ~]$ kubectl exec -it $(kubectl get pods --no-headers -l postgres-operator.crunchydata.com/role=master -o custom-columns=:metadata.name) -c database -- bash


bash-4.4$ psql
psql (12.18)
Type "help" for help.

postgres=# \c SharedServices
You are now connected to database "SharedServices" as user "postgres".


SharedServices=#