Vira Vitanska created DLAB-279:
----------------------------------

             Summary: Investigate if content of available lib list should 
depend on cloud and OS
                 Key: DLAB-279
                 URL: https://issues.apache.org/jira/browse/DLAB-279
             Project: Apache DLab
          Issue Type: Bug
            Reporter: Vira Vitanska


There is some list of libraries which is available for one cloud/OS and is not 
available for other one.

*For example:*
RStudio ['apt/yum']: 'tkinter' is present in available lib list for AWS 
(RedHat) and the same lib is absent for AWS [Debian], GCP, Azure;
RStudio ['apt/yum']: 'python-mysqldb' is present in available lib list for AWS 
(Debian) and the same lib is absent for AWS [RedHat], GCP, Azure;
RStudio ['apt/yum']: 'tabix' is present in available lib list for AWS (Debian) 
and the same lib is absent for AWS [RedHat], GCP, Azure.

 

*Preconditions:*
 # Library RStudio ['apt/yum']: 'tkinter' is installed on Rstudio  for AWS 
[RedHat] 
 # Rstudio is created on AWS [Debian]
 # Rstudio is created on GCP [Debian]
 # Rstudio is created on Azure [Debian][RedHat]

*Steps to reproduce:*
 # Install Library RStudio ['apt/yum'] on AWS [Debian] via Dlab UI
 # Install Library RStudio ['apt/yum'] on GCP [Debian] via Dlab UI
 # Install Library RStudio ['apt/yum'] on on Azure [Debian][RedHat]  via Dlab UI

*Actual result:*
 # Library RStudio ['apt/yum'] on AWS [Debian]  is not in available lib list
 # Library RStudio ['apt/yum'] on GCP [Debian]  is not in available lib list
 # Library RStudio ['apt/yum'] on Azure [Debian][RedHat]  is not in available 
lib list

*Expected result:*
 # Library RStudio ['apt/yum'] on AWS [Debian]  is installed
 # Library RStudio ['apt/yum'] on GCP [Debian]  is installed
 # Library RStudio ['apt/yum'] on Azure [Debian][RedHat]  is installed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to