search

sassoftware / viya4-deployment

This project contains Ansible code that creates a baseline in an existing Kubernetes environment for use with the SAS Viya Platform, generates the manifest for an order, and then can also deploy that order into the Kubernetes environment specified.
Apache License 2.0
71 stars 64 forks source link

2022.10 deployment failure: "sas-bases/overlays/internal-postgres: no such file or directory" #325

Closed bullcity42 closed 11 months ago

bullcity42 commented 2 years ago

Attempting to deploy 2022.10 fails with "sas-bases/overlays/internal-postgres: no such file or directory": 

stderr: 'Error: accumulating resources: accumulateFile "accumulating resources from ''sas-bases/overlays/internal-postgres'': 
open /data/test-aks/viya/sas-bases/overlays/internal-postgres: no such file or directory", 
loader.New "Error loading sas-bases/overlays/internal-postgres with git: 
url lacks host: sas-bases/overlays/internal-postgres, dir: 
evalsymlink failure on ''/data/test-aks/viya/sas-bases/overlays/internal-postgres'' :
lstat /data/test-aks/viya/sas-bases/overlays/internal-postgres: no such file or directory, 
get: invalid source string: sas-bases/overlays/internal-postgres"'

Because the kustomization.yaml generated by viya4-deployment includes:

resources:
## vdm defined resources (pre)
...
  - sas-bases/overlays/internal-postgres
...

But sas-bases/overlays/internal-postgres path does not exist in 2022.10 deployment assets. It exists at 2022.09 but not 2022.10. Why is viya4-deployment project creating the kustomization.yaml this way? Due to the related change at 2022.10 moving to Crunchy Data 5, is this a bug that needs to be fixed?

Refer to the deployment notes which discusses this change: Update to Crunchy Data 5 for Internal Instances of PostgreSQL

dhoucgitter commented 2 years ago

Hi @bullcity42, what release version of viya4-deployment are you using? The behavior that you described above is consistent with what you'd see trying to deploy a "2022.10" cadence version or newer with a release version of viya4-deployment prior to the latest which is 5.6.0. See the release notes here. The 5.6.0 release includes support for Viya cadences using crunchy version 5. If the release version of viya4-deployment that are you using is not the latest 5.6.0 release, please move up to that release level as it supports Viya releases using crunchy v5.

riragh commented 11 months ago

Closing this issue due to inactivity. Please feel free to reopen if the issue still persist.