SAS Viya 3.5 Deployment failed: The generated orchestration is not current

[Iyappan21]

Hi Experts,

We are performing SAS Viya 3.5 Single Machine Deployment. Deployment is done with failed task : 1.

We are able to see the folders under /opt/sas but it seems some of the m are missing.

While analysing the log files we could see below:

"stderr": "The generated orchestration is not current.\nYou must regenerate the orchestration for this order and restart the deployment.\n\nThe following software units are in the repository warehouse but not in the intended orchestration\n x64_redhat_linux_6-yum:default\n pgpoolc\n sas-postgresql-secure-11:rpm\n sas-postgresql-secure-libs-11:rpm\n sas_casserver_primary\n sas-pgpool-II-40:rpm\n sas_casserver_secondary\n sas-pgpool-II-40:rpm\n sas_casserver_worker\n sas-pgpool-II-40:rpm\n sasdatasvrc\n sas-pgpool-II-40:rpm",
"stderr_lines": [
"The generated orchestration is not current.",
"You must regenerate the orchestration for this order and restart the deployment.",
"",
"The following software units are in the repository warehouse but not in the intended orchestration",
" x64_redhat_linux_6-yum:default",
" pgpoolc",
" sas-postgresql-secure-11:rpm",
" sas-postgresql-secure-libs-11:rpm",
" sas_casserver_primary",
" sas-pgpool-II-40:rpm",
" sas_casserver_secondary",
" sas-pgpool-II-40:rpm",
" sas_casserver_worker",
" sas-pgpool-II-40:rpm",
" sasdatasvrc",
" sas-pgpool-II-40:rpm"
],

Can anyone help us to get the issue and resolve it.

Thanks

[alexal · Accepted solution]

@Iyappan21 ,

You have to download the most recent version of SAS Orchestration Command Line Interface (CLI) https://support.sas.com/en/documentation/install-center/viya/deployment-tools/35/command-line-interf... and regenerate your playbook.

[Iyappan21]

Hi Alex,

The above issue is resolved by creating a playbook with proper Deployment file. But we are facing issue with below error

[Errno 16] error opening local file from https://sasviyablobstorage6.blob.core.windows.net/sasviya-mirror-repository-35/sas_repos/repos/shipp..., IOError: [Errno 28] No space left on device: '/var/cache/yum/x86_64/7Server/sas-inteldecn-125-x64_redhat_linux_6-yum/packages/sas-modelsvr1-03.21.00-20191104.232733829217.x86_64.rpm'\nTrying other mirror.\nhttps://sasviyablobstorage6.blob.core.windows.net/sasviya-mirror-repository-35/sas_repos/repos/shipped/dmdatap/125/dmdatap-125-x64_redhat_linux_6-yum/Packages/s/sas-monitoring-2.2.7-20191105.1572981193739.x86_64.rpm: [Errno 16] error opening local file from https://sasviyablobstorage6.blob.core.windows.net/sasviya-mirror-repository-35/sas_repos/repos/shipp..., IOError: [Errno 28] No space left on device: '/var/cache/yum/x86_64/7Server/sas-dmdatap-125-x64_redhat_linux_6-yum/packages/sas-monitoring-2.2.7-20191105.1572981193739.x86_64.rpm'\nTrying other mirror.

Repository Warehouse is accesible and enough space as well. What needs to be done on this.

Please guide.

[alexal]

@Iyappan21 ,

Check your disk space, seems like you do not have enough space.

[Iyappan21]

@alexal  We kept Keepcache =0 and deploying with local repository, still it downloads the repository in /var/cache/yum. Is it an expected behaviour? Or anything else to be done to avoid the additional download.

Thanks for the reponse.



Thanks,

Iyappan M S

[Iyappan21]

@alexal This issue is resolved with extending var/cache folder disk.

Thanks for the response