apply new license not working

[biohazd]

Viya4 Deployment Version Details

I have deployed using the viya4-aws and viya4-deployment onto Kubernetes.

When trying to apply the new license it doesnt seem to work.

Question 1 - after runnign the docker/deploy - should the license show up in the GUI immediately, or does it need any restarts ?

Im on Cadence STABLE - 2024.02

docker run --platform linux/x86_64 --rm
--group-add root
--user $(ls -lnd build | awk '{str = $3 ":" $4; print str }')
--volume viya4-01/build/viya4-deployment/deployments:/data
--volume /viya4-01/ansible-vars.yaml:/config/config
--volume /viya4-01/terraform.tfstate:/config/tfstate
--volume /viya4-01/build/viya4-deployment/ssh_private_key:/config/jump_svr_private_key
--volume /Users/an//Downloads/SASViyaV4_XXX_3_stable_2024.02_20240319.1710889818208_multipleAssets_2024-03-20T144337/SASViyaV4_XXX_3_stable_2024.02_20240319.1710889818208_deploymentAssets_2024-03-20T144337.tgz:/config/deployment.tgz
--volume /Users/an/Downloads/SASViyaV4_XXX_4_stable_2025.03_license_1743589811852.jwt:/config/SASViyaV4_XXX_4_stable_2025.03_licensgfgfgf1852.jwt
viya4-deployment
-e 'NAMESPACE=sas-viya4'
-e 'V4_CFG_SAS_API_KEY=ZZZZZZZZZZZZZZ'
-e 'V4_CFG_SAS_API_SECRET=YYYYYYYY'
-e 'V4_CFG_ORDER_NUMBER=XXXXXX'
-e 'V4_CFG_INGRESS_FQDN=viya4-02.sas.platform.com'
-e 'V4M_BASE_DOMAIN=viya4-02.sas.platform.com'
-e 'V4_CFG_LICENSE=/config/SASViyaV4_XXX_4_stable_2025.03_license_174cccccc852.jwt'
-e 'V4_CFG_DEPLOYMENT_ASSETS=/config/deployment.tgz'
--tags "viya,install"

Ansible Variable File Details

No response

Steps to Reproduce

run a docker run

Expected Behavior

new license applied

Actual Behavior

new license is applied

Additional Context

No response

References

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[biohazd]

in rhe troubleshooting file it says this

After downloading the license file perform the following steps:

1. Set V4_CFG_LICENSE to path where your license file is located. Note, it is a .jwt file.
2. Using viya4-deployment rerun the viya,install tasks to regenerate your kustomization.yaml that will now have an updated reference to the new license file, generate the SASDeployment custom resource file, and apply it into your cluster.
3. You will see your license file referenced in the kustomization.yaml as a generator, look for site-config/vdm/generators/sas-license.yaml

Do you simply add the variable "V4_CFG_LICENSE" and run the "docker run" and the new license is deployed?
the above seems to imply running the "Using viya4-deployment rerun the viya,install tasks to regenerate your kustomization.yaml". AND then run the next step of "generate the SASDeployment custom resource file," - how do you ""generate the SASDeployment custom resource file," ?

[dhoucgitter]

Hi, I suspect that you obfuscated parts of the license file names in the command above, however, you can simplify specifying your license file name and increase the odds that the host and docker container file names will line up properly when using docker by using a single volume mapping and path specification to the license file using --volume <path_to_license_file_name_on_your_local_host>:/config/v4_cfg_license as documented here instead of having to create your own volume reference and then having refer to the right-side again with -e V4_CFG_LICENSE=value like you've done above.

Regarding step #2, when you rerun "viya,install", all of the actions listed, the updated reference in kustomization.yaml, generating the SASDeployment custom resource file and applying it into your cluster should all happen rerunning "viya,install" when DEPLOY=true in your ansible cfg yaml file.

[biohazd]

if the run works correctly, should the license in the GUI immediately show the new expiration date ? OR do i need to restart soemthing ?

I'm not seeing any errors, but in the SAS gui it still shows the old license expiration date.

[dhoucgitter]

I'm not certain what's required for the GUI reflect the newly applied license information.
You could also try following the steps here to view your SAS Programming Run-Time License Information.
https://go.documentation.sas.com/doc/en/sasadmincdc/v_059/callicense/n03028saslicensing00000admin.htm

[github-actions]

This issue is stale because it has been open 30 days with no activity.

[saschjmil]

@biohazd, were you able to figure out the license issue?

[github-actions]

This issue is stale because it has been open 30 days with no activity.