Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / sassoftware/viya-ark issues and pull requests
#101 - merge develop to main for release
Pull Request -
State: closed - Opened by kevinlinglesas over 1 year ago
#101 - merge develop to main for release
Pull Request -
State: closed - Opened by kevinlinglesas over 1 year ago
#100 - (#92) stop script updates to support RHEL8
Pull Request -
State: closed - Opened by erharb over 1 year ago
#100 - (#92) stop script updates to support RHEL8
Pull Request -
State: closed - Opened by erharb over 1 year ago
#99 - How to restart two CAS controller with Viya-ark ?
Issue -
State: closed - Opened by nhousset over 1 year ago
- 2 comments
#99 - How to restart two CAS controller with Viya-ark ?
Issue -
State: closed - Opened by nhousset over 1 year ago
- 2 comments
#98 - [Viya3.5] Pre-check by pre-install playbook
Issue -
State: closed - Opened by TakeshiMifune over 1 year ago
- 4 comments
#98 - [Viya3.5] Pre-check by pre-install playbook
Issue -
State: closed - Opened by TakeshiMifune over 1 year ago
- 4 comments
#97 - SAS Viya Deployment Report Playbook - Hot Fix report on environments with no Internet access
Issue -
State: closed - Opened by splmie over 1 year ago
- 1 comment
#97 - SAS Viya Deployment Report Playbook - Hot Fix report on environments with no Internet access
Issue -
State: closed - Opened by splmie over 1 year ago
- 1 comment
#96 - merge from old master to main
Pull Request -
State: closed - Opened by kevinlinglesas over 1 year ago
#96 - merge from old master to main
Pull Request -
State: closed - Opened by kevinlinglesas over 1 year ago
#95 - pre.install hangs in "verify sudo" step
Issue -
State: closed - Opened by miaeyg almost 2 years ago
- 4 comments
#95 - pre.install hangs in "verify sudo" step
Issue -
State: closed - Opened by miaeyg almost 2 years ago
- 4 comments
#94 - pre.install fails to run with Ansible-Core 2.12.10 due to missing Ansible modules
Issue -
State: closed - Opened by miaeyg almost 2 years ago
- 1 comment
#94 - pre.install fails to run with Ansible-Core 2.12.10 due to missing Ansible modules
Issue -
State: closed - Opened by miaeyg almost 2 years ago
- 1 comment
#93 - mmsu start fails to start Postgres after SELinux is enabled
Issue -
State: closed - Opened by migu816 about 2 years ago
- 2 comments
#93 - mmsu start fails to start Postgres after SELinux is enabled
Issue -
State: closed - Opened by migu816 about 2 years ago
- 2 comments
#92 - SAS Viya 3.5 sas-viya-launcher-default service is not stopped by viya-services-stop.yml
Issue -
State: closed - Opened by LaimonasReklaitis over 2 years ago
- 5 comments
Labels: bug
#92 - SAS Viya 3.5 sas-viya-launcher-default service is not stopped by viya-services-stop.yml
Issue -
State: closed - Opened by LaimonasReklaitis over 2 years ago
- 5 comments
Labels: bug
#91 - https://github.com/sassoftware/viya-ark/blob/master/playbooks/merge-playbook/README.md
Issue -
State: closed - Opened by Oleggelo79 almost 3 years ago
- 5 comments
#91 - https://github.com/sassoftware/viya-ark/blob/master/playbooks/merge-playbook/README.md
Issue -
State: closed - Opened by Oleggelo79 almost 3 years ago
- 5 comments
#90 - Playbook viya-services-status.yml does not check Apache httpd status and availability
Issue -
State: closed - Opened by JMPoilane almost 3 years ago
- 1 comment
Labels: enhancement
#90 - Playbook viya-services-status.yml does not check Apache httpd status and availability
Issue -
State: closed - Opened by JMPoilane almost 3 years ago
- 1 comment
Labels: enhancement
#89 - Fatal TASK [Perform host connection checks]
Issue -
State: closed - Opened by KaminoU almost 3 years ago
- 5 comments
#89 - Fatal TASK [Perform host connection checks]
Issue -
State: closed - Opened by KaminoU almost 3 years ago
- 5 comments
#88 - Required sudo permissions for viyadep
Issue -
State: closed - Opened by LuciaSantin almost 3 years ago
- 4 comments
#88 - Required sudo permissions for viyadep
Issue -
State: closed - Opened by LuciaSantin almost 3 years ago
- 4 comments
#87 - sesudo instead sudo (eTrust)
Issue -
State: closed - Opened by framhc almost 3 years ago
- 2 comments
#87 - sesudo instead sudo (eTrust)
Issue -
State: closed - Opened by framhc almost 3 years ago
- 2 comments
#86 - "sas-viya-sasdatasvrc-postgres-node0" service inactive (dead) when starting Viya 3.5 with Viya-Ark
Issue -
State: closed - Opened by irchum about 3 years ago
- 3 comments
#86 - "sas-viya-sasdatasvrc-postgres-node0" service inactive (dead) when starting Viya 3.5 with Viya-Ark
Issue -
State: closed - Opened by irchum about 3 years ago
- 3 comments
#85 - Commit updates to README
Pull Request -
State: closed - Opened by lasiva over 3 years ago
- 1 comment
#85 - Commit updates to README
Pull Request -
State: closed - Opened by lasiva over 3 years ago
- 1 comment
#84 - Viya-ARK for 3.5 is throwing errors when checking the status.yml ---> viya-mmsu/viya-services-status.yml
Issue -
State: closed - Opened by Siva830 over 3 years ago
- 5 comments
#84 - Viya-ARK for 3.5 is throwing errors when checking the status.yml ---> viya-mmsu/viya-services-status.yml
Issue -
State: closed - Opened by Siva830 over 3 years ago
- 5 comments
#83 - Why the 5 GB size enforcement on root disk
Issue -
State: closed - Opened by AWSmith0216 almost 4 years ago
- 1 comment
#82 - Automatically install RHEL 8 compatibility packages
Issue -
State: closed - Opened by AWSmith0216 almost 4 years ago
- 2 comments
#82 - Automatically install RHEL 8 compatibility packages
Issue -
State: closed - Opened by AWSmith0216 almost 4 years ago
- 2 comments
#81 - Pre-installation playbook failed on
Issue -
State: closed - Opened by peterscp93 almost 4 years ago
- 5 comments
#81 - Pre-installation playbook failed on
Issue -
State: closed - Opened by peterscp93 almost 4 years ago
- 5 comments
#80 - Remove the pre.timeouts_config
Issue -
State: closed - Opened by aekuback almost 4 years ago
- 2 comments
#80 - Remove the pre.timeouts_config
Issue -
State: closed - Opened by aekuback almost 4 years ago
- 2 comments
#79 - Viya -ark mmsu encountering an error when trying to run as SUDO
Issue -
State: closed - Opened by billwisotsky almost 4 years ago
- 1 comment
#79 - Viya -ark mmsu encountering an error when trying to run as SUDO
Issue -
State: closed - Opened by billwisotsky almost 4 years ago
- 1 comment
#78 - Review microservice dependencies for VI/AML/CDD
Issue -
State: closed - Opened by iagomez almost 4 years ago
- 2 comments
Labels: enhancement
#78 - Review microservice dependencies for VI/AML/CDD
Issue -
State: closed - Opened by iagomez almost 4 years ago
- 2 comments
Labels: enhancement
#77 - Viya 3.5 Pre-Install failed while running pre_install_playbook.yml
Issue -
State: closed - Opened by mukeshkham almost 4 years ago
- 5 comments
#77 - Viya 3.5 Pre-Install failed while running pre_install_playbook.yml
Issue -
State: closed - Opened by mukeshkham almost 4 years ago
- 5 comments
#76 - Merge Deployment Files Error
Issue -
State: closed - Opened by tfullerbmx about 4 years ago
- 3 comments
#76 - Merge Deployment Files Error
Issue -
State: closed - Opened by tfullerbmx about 4 years ago
- 3 comments
#75 - UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 15: ordinal not in range(128)
Issue -
State: closed - Opened by lardabi about 4 years ago
- 4 comments
Labels: bug
#75 - UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position 15: ordinal not in range(128)
Issue -
State: closed - Opened by lardabi about 4 years ago
- 4 comments
Labels: bug
#74 - playbooks/viya-mmsu/viya-services-stop.yml dont work when a worker est down
Issue -
State: closed - Opened by framhc about 4 years ago
- 2 comments
#74 - playbooks/viya-mmsu/viya-services-stop.yml dont work when a worker est down
Issue -
State: closed - Opened by framhc about 4 years ago
- 2 comments
#73 - error on allowed languages for server
Issue -
State: closed - Opened by devopsasadm about 4 years ago
- 4 comments
#73 - error on allowed languages for server
Issue -
State: closed - Opened by devopsasadm about 4 years ago
- 4 comments
#72 - pre-install-playbook - The directory /opt/sas only has 777 permissions. It should have at least 755. Edit the storage_list variable if this is a mistake. Or add --skip-tags skipstoragefail to bypass.
Issue -
State: closed - Opened by bheinsius over 4 years ago
- 3 comments
Labels: bug
#72 - pre-install-playbook - The directory /opt/sas only has 777 permissions. It should have at least 755. Edit the storage_list variable if this is a mistake. Or add --skip-tags skipstoragefail to bypass.
Issue -
State: closed - Opened by bheinsius over 4 years ago
- 3 comments
Labels: bug
#71 - Viya-ARKCD - Namespace Admin Permissions: Insufficient
Issue -
State: closed - Opened by ken-sys over 4 years ago
- 5 comments
#71 - Viya-ARKCD - Namespace Admin Permissions: Insufficient
Issue -
State: closed - Opened by ken-sys over 4 years ago
- 5 comments
#70 - How to bypass the sas_yum_urls when we have a local viya mirror?
Issue -
State: closed - Opened by stagba over 4 years ago
- 4 comments
#70 - How to bypass the sas_yum_urls when we have a local viya mirror?
Issue -
State: closed - Opened by stagba over 4 years ago
- 4 comments
#69 - viya_pre_install_playbook.yml fails on clientaliveinterval control even when you run the playbook with the exclude opti
Issue -
State: closed - Opened by JMPoilane over 4 years ago
- 9 comments
Labels: bug
#69 - viya_pre_install_playbook.yml fails on clientaliveinterval control even when you run the playbook with the exclude opti
Issue -
State: closed - Opened by JMPoilane over 4 years ago
- 9 comments
Labels: bug
#68 - When using local mirror, pre-install playbook should not check the SAS yum repository
Issue -
State: closed - Opened by wweghe over 4 years ago
- 1 comment
#68 - When using local mirror, pre-install playbook should not check the SAS yum repository
Issue -
State: closed - Opened by wweghe over 4 years ago
- 1 comment
#67 - Error message with deployment Report
Issue -
State: closed - Opened by fabricepollet over 4 years ago
- 3 comments
#67 - Error message with deployment Report
Issue -
State: closed - Opened by fabricepollet over 4 years ago
- 3 comments
#66 - Usage instructions
Issue -
State: closed - Opened by AddeGroot over 4 years ago
- 1 comment
#66 - Usage instructions
Issue -
State: closed - Opened by AddeGroot over 4 years ago
- 1 comment
#65 - Viya 3.5 Pre-Install failed while running pre_install_playbook.yml
Issue -
State: closed - Opened by venkattoluchuri over 4 years ago
- 22 comments
#65 - Viya 3.5 Pre-Install failed while running pre_install_playbook.yml
Issue -
State: closed - Opened by venkattoluchuri over 4 years ago
- 22 comments
#64 - Fix if there is no sasnote for hotfix when formatting descriptions
Pull Request -
State: closed - Opened by Vladislaff over 4 years ago
- 2 comments
#64 - Fix if there is no sasnote for hotfix when formatting descriptions
Pull Request -
State: closed - Opened by Vladislaff over 4 years ago
- 2 comments
#63 - Failed to run deployment report
Issue -
State: closed - Opened by kurthaemmerle over 4 years ago
- 8 comments
#63 - Failed to run deployment report
Issue -
State: closed - Opened by kurthaemmerle over 4 years ago
- 8 comments
#62 - A sasauth-mkhomedir.sh script isn't required for SAS Viya
Pull Request -
State: closed - Opened by alexal over 4 years ago
- 2 comments
#62 - A sasauth-mkhomedir.sh script isn't required for SAS Viya
Pull Request -
State: closed - Opened by alexal over 4 years ago
- 2 comments
#61 - Set valid installed package flag failing to compare correctly
Issue -
State: closed - Opened by aekuback over 4 years ago
- 5 comments
#61 - Set valid installed package flag failing to compare correctly
Issue -
State: closed - Opened by aekuback over 4 years ago
- 5 comments
#60 - After Linux Rhel patching we are seeing issues with viya-services-status.yml , alsl start script had issues, so had to restart sas services manually
Issue -
State: closed - Opened by svemuri123 over 4 years ago
- 8 comments
#60 - After Linux Rhel patching we are seeing issues with viya-services-status.yml , alsl start script had issues, so had to restart sas services manually
Issue -
State: closed - Opened by svemuri123 over 4 years ago
- 8 comments
#59 - Remove SAS CAS Worker of playbook
Issue -
State: closed - Opened by cristianmarl over 4 years ago
- 6 comments
#59 - Remove SAS CAS Worker of playbook
Issue -
State: closed - Opened by cristianmarl over 4 years ago
- 6 comments
#58 - Unable to start all services in Viya 3.5 deployment
Issue -
State: closed - Opened by brianmbennett over 4 years ago
- 1 comment
#58 - Unable to start all services in Viya 3.5 deployment
Issue -
State: closed - Opened by brianmbennett over 4 years ago
- 1 comment
#57 - MMSU: Issue starting services
Issue -
State: closed - Opened by sasayd over 4 years ago
- 3 comments
#57 - MMSU: Issue starting services
Issue -
State: closed - Opened by sasayd over 4 years ago
- 3 comments
#56 - pre-install failure for sudo
Issue -
State: closed - Opened by ken-sys almost 5 years ago
- 5 comments
#56 - pre-install failure for sudo
Issue -
State: closed - Opened by ken-sys almost 5 years ago
- 5 comments
#55 - Pre-installation Playbook - report?
Issue -
State: closed - Opened by ken-sys almost 5 years ago
- 2 comments
#55 - Pre-installation Playbook - report?
Issue -
State: closed - Opened by ken-sys almost 5 years ago
- 2 comments
#54 - using Viya-ark with crontab / monitoring uptime
Issue -
State: closed - Opened by devopsasadm almost 5 years ago
- 5 comments
#54 - using Viya-ark with crontab / monitoring uptime
Issue -
State: closed - Opened by devopsasadm almost 5 years ago
- 5 comments
#53 - MMSU doesn't cleanup stray process
Issue -
State: closed - Opened by mawamb almost 5 years ago
- 2 comments
#53 - MMSU doesn't cleanup stray process
Issue -
State: closed - Opened by mawamb almost 5 years ago
- 2 comments
#52 - "basic connection test" fails in viyaldapvalidator.yml without specifying the -b option
Issue -
State: closed - Opened by wweghe almost 5 years ago
- 4 comments
#52 - "basic connection test" fails in viyaldapvalidator.yml without specifying the -b option
Issue -
State: closed - Opened by wweghe almost 5 years ago
- 4 comments
#51 - Can't run pre_install_playbook due to sudo problem.
Issue -
State: closed - Opened by ken-sys almost 5 years ago
- 2 comments