@val_nikolajevs @ravikumar901 I believe this behavior was fixed with an update. ... View more

In addition to logging in (authentication), you must also provide Viya with a list of users (identity provisioning). Your authentication provider can be an LDAP server, OIDC, SAML or Kerberos. Your identity provider can either be LDAP or SCIM. The account identifier must match between your authentication and identity providers exactly. The error message saying the system could not obtain group memberships means authentication was successful, but when SAS Logon Manager called the identities service to request the groups the authenticated user is a member of, this request failed, suggesting identity provisioning has not been configured. The identities service also providers uid/gid numbers to allow users to run compute sessions. This documentation goes into more detail on Identity Management: https://go.documentation.sas.com/doc/en/sasadmincdc/v_057/calids/titlepage.htm ... View more

Viya has backup functionality that makes use of persistent volume claims to store backups. If you are using your own on-prem cluster, you would want to have some sort of backup solution of the storage volumes that underpin the persistent volume claims, as well as backups for anything not backed up by the Viya backup functionality. More information on what the Viya backup covers can be found here: https://go.documentation.sas.com/doc/en/sasadmincdc/v_057/calbr/p1hkatn0s9p84fn19swyxm88fors.htm#n1na61n8ogz5j1n14f7793uxbpeh ... View more

In SAS Code you can use the FILESRVC access method to reference a file in the files service from a filename statement: https://go.documentation.sas.com/doc/en/pgmsascdc/v_052/lestmtsglobal/p0qapul7pyz9hmn0zfoefj0c278a.htm ... View more

It looks like your web server is not running on that host as you are getting a connection refused on the 8343 port. ... View more

The sas-viya CLI will return a non-zero exit code if the create fails. You can also check the configuration exists using the CLI, e.g. sas-viya configuration configurations list -d logging.level -s identities ... View more

I believe this is something done at the repository level, so it might be easier to use the CLI to loop through all your repositories to apply the lifecycle policy to each. I've not had any experience using the functionality in AWS. I don't know of any plans to add that functionality to Mirror Manager. It looks like there is functionality in the AWS console to preview the results of the lifecycle policy before applying it. https://docs.aws.amazon.com/AmazonECR/latest/userguide/lpp_creation.html ... View more

If the arke pod restarted and is now running successfully it doesn't sound like you need to perform any further troubleshooting. The arke pod facilitates communication to the rabbitmq servers, so it could fail to start up successfully if rabbitmq was not yet up. ... View more

If you have the assets for a given release, you could grep the overlays/required/transformers.yaml to identify the tag for each image associated with that release, for example: $ grep newTag -m1 -B1 sas-bases/overlays/required/transformers.yaml newName: cr.sas.com/viya-4-x64_oci_linux_2-docker/sas-activities newTag: 1.53.15-20221103.1667486852217 But the version can change during a release cycle, if an update is pushed to 2024.04 for a given image and you pulled the latest assets for it, then the image tag would be different for that image than what you might have in your ECR. Using the lifecycle option lets you instruct the ECR to remove all entries that meet given criteria, while keeping some history. ... View more

The MS SQL ODBC driver should be present by default, and can use DSN-less connections so you wouldn't need an ODBC file but you could put one in the mount you're adding with the data-mounts sample transformers. If you are setting a DSN when configuring the the connection in Viya, you'd probably need to provide the odbc file. For connections from CAS, there would need to be a network path from the CAS node to the MS SQL server, so if that port is not opened it would need to be. Verify SAS/ACCESS Interface to Microsoft SQL Server https://go.documentation.sas.com/doc/en/sasadmincdc/v_055/calvalid/p0455nqweukxh3n1gommqk2sdpaf.htm ... View more

@EyalGonen I tested running with the --remove-old option and received this message: Flag --remove-old has been deprecated, please use --remove-after-upload, and that option would only remove from the local repo after they've been uploaded, so I don't think that would do what you want. It looks like ECR has lifecycle options you can configure: https://docs.aws.amazon.com/AmazonECR/latest/userguide/LifecyclePolicies.html It looks like one way you could do this is with the tagStatus of "tagged" and "imageCountMoreThan" countType, which sounds like it would tell the ECR to remove all tagged images older than the last n images pushed. ... View more