[GitHub] [incubator-dlab] ofuks merged pull request #647: [DLAB-1524] Endpoints fields verification
ofuks merged pull request #647: [DLAB-1524] Endpoints fields verification URL: https://github.com/apache/incubator-dlab/pull/647 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1628) [AWS]: Data Engine Service creation fails if project name contains upper case
Vira Vitanska created DLAB-1628: --- Summary: [AWS]: Data Engine Service creation fails if project name contains upper case Key: DLAB-1628 URL: https://issues.apache.org/jira/browse/DLAB-1628 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Mykola Bodnar Fix For: v.2.3 Attachments: EMR creation.png *Preconditions:* 1. Project is created on remote AWS endpoint 2. Project name contains upper case *Steps to reproduce:* 1. Create EMR on notebook *Actual result:* 1. EMR creation fails *Expected result:* EMR is created successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1626) [GCP]: Notebook termination fails if notebook contains Dataproc
[ https://issues.apache.org/jira/browse/DLAB-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Frolov updated DLAB-1626: Attachment: term_dp_zepp.PNG.png term_dp_jup.PNG > [GCP]: Notebook termination fails if notebook contains Dataproc > --- > > Key: DLAB-1626 > URL: https://issues.apache.org/jira/browse/DLAB-1626 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Debian, DevOps, GCP > Attachments: GCP Notebook termination.png, term_dp_jup.PNG, > term_dp_zepp.PNG.png > > > Dataproc was created on Jupyter. However i think it is related to all > notebooks. > *Preconditions:* > 1. Dataproc is created > *Steps to reproduce:* > 1. Terminate notebook > Actual result: > 1. Notebook termination fail > *Expected result:* > 1. Notebook termination is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] Dyoma33 merged pull request #651: [DLAB-1627]: Notebook creation fails from image
Dyoma33 merged pull request #651: [DLAB-1627]: Notebook creation fails from image URL: https://github.com/apache/incubator-dlab/pull/651 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1625) [GCP]: Edge node starting fails on remote GCP endpoint
[ https://issues.apache.org/jira/browse/DLAB-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Frolov reassigned DLAB-1625: --- Assignee: Mykola Bodnar (was: Leonid Frolov) > [GCP]: Edge node starting fails on remote GCP endpoint > > > Key: DLAB-1625 > URL: https://issues.apache.org/jira/browse/DLAB-1625 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > Attachments: GCP edge node starting.png > > > *Preconditions:* > 1. Edge is created on GCP remote endpoint > 2. Edge node is in stopping status > *Steps to reproduce:* > 1. Start edge node on GCP remote endpoint > *Actual result:* > 1. Edge node stopping fails > *Expected result:* > 1. Edge node stopping is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] leonidfrolov opened a new pull request #651: [DLAB-1627]: Notebook creation fails from image
leonidfrolov opened a new pull request #651: [DLAB-1627]: Notebook creation fails from image URL: https://github.com/apache/incubator-dlab/pull/651 fixed notebook and spark cluster creation This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1627) [GSP]: Notebook creation fails from image
[ https://issues.apache.org/jira/browse/DLAB-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated DLAB-1627: - Labels: Debian DevOps GCP pull-request-available (was: Debian DevOps GCP) > [GSP]: Notebook creation fails from image > - > > Key: DLAB-1627 > URL: https://issues.apache.org/jira/browse/DLAB-1627 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Debian, DevOps, GCP, pull-request-available > Attachments: GCP console.png, Notebook creation.png, Spark cluster > creation.png, changed shared ami name.PNG > > > *Preconditions:* > # Project1 is created on GCP with disabled 'use shared image' > # Notebook1 is created > *Steps to reproduce:* > 1. Create notebook of the same template in Project1 > *Actual result:* > 1. Notebook creation fails > *Expected result:* > 1. Notebook creation is successful > > 1. Also Spark cluster creation fails with the same error. > The bug was reproduced on Zeppelin notebook. But I think it is not depends > on notebook. > 2. If project is with enabled 'use shared image' the bug is not reproduced. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1627) [GSP]: Notebook creation fails from image
[ https://issues.apache.org/jira/browse/DLAB-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Frolov updated DLAB-1627: Attachment: changed shared ami name.PNG > [GSP]: Notebook creation fails from image > - > > Key: DLAB-1627 > URL: https://issues.apache.org/jira/browse/DLAB-1627 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Debian, DevOps, GCP > Attachments: GCP console.png, Notebook creation.png, Spark cluster > creation.png, changed shared ami name.PNG > > > *Preconditions:* > # Project1 is created on GCP with disabled 'use shared image' > # Notebook1 is created > *Steps to reproduce:* > 1. Create notebook of the same template in Project1 > *Actual result:* > 1. Notebook creation fails > *Expected result:* > 1. Notebook creation is successful > > 1. Also Spark cluster creation fails with the same error. > The bug was reproduced on Zeppelin notebook. But I think it is not depends > on notebook. > 2. If project is with enabled 'use shared image' the bug is not reproduced. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] DG1202 merged pull request #650: [DLAB-1615]: Added service value to billing Azure
DG1202 merged pull request #650: [DLAB-1615]: Added service value to billing Azure URL: https://github.com/apache/incubator-dlab/pull/650 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] DG1202 opened a new pull request #650: [DLAB-1615]: Added service value to billing Azure
DG1202 opened a new pull request #650: [DLAB-1615]: Added service value to billing Azure URL: https://github.com/apache/incubator-dlab/pull/650 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] DG1202 closed pull request #649: [DLAB-1615]: Added value to billing Azure
DG1202 closed pull request #649: [DLAB-1615]: Added value to billing Azure URL: https://github.com/apache/incubator-dlab/pull/649 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] DG1202 opened a new pull request #649: [DLAB-1615]: Added value to billing Azure
DG1202 opened a new pull request #649: [DLAB-1615]: Added value to billing Azure URL: https://github.com/apache/incubator-dlab/pull/649 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1627) [GSP]: Notebook creation fails from image
[ https://issues.apache.org/jira/browse/DLAB-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1627: Description: *Preconditions:* # Project1 is created on GCP with disabled 'use shared image' # Notebook1 is created *Steps to reproduce:* 1. Create notebook of the same template in Project1 *Actual result:* 1. Notebook creation fails *Expected result:* 1. Notebook creation is successful 1. Also Spark cluster creation fails with the same error. The bug was reproduced on Zeppelin notebook. But I think it is not depends on notebook. 2. If project is with enabled 'use shared image' the bug is not reproduced. was: *Preconditions:* # Project1 is created on GCP with disabled 'use shared image' # Notebook1 is created *Steps to reproduce:* 1. Create notebook of the same template in Project1 *Actual result:* 1. Notebook creation fails *Expected result:* 1. Notebook creation is successful 1. Also Spark cluster creation fails with the same error. The bug was reproduced on Zeppelin notebook. But I think it is not depends on notebook. > [GSP]: Notebook creation fails from image > - > > Key: DLAB-1627 > URL: https://issues.apache.org/jira/browse/DLAB-1627 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Debian, DevOps, GCP > Attachments: GCP console.png, Notebook creation.png, Spark cluster > creation.png > > > *Preconditions:* > # Project1 is created on GCP with disabled 'use shared image' > # Notebook1 is created > *Steps to reproduce:* > 1. Create notebook of the same template in Project1 > *Actual result:* > 1. Notebook creation fails > *Expected result:* > 1. Notebook creation is successful > > 1. Also Spark cluster creation fails with the same error. > The bug was reproduced on Zeppelin notebook. But I think it is not depends > on notebook. > 2. If project is with enabled 'use shared image' the bug is not reproduced. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1627) [GSP]: Notebook creation fails from image
[ https://issues.apache.org/jira/browse/DLAB-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1627: Description: *Preconditions:* # Project1 is created on GCP with disabled 'use shared image' # Notebook1 is created *Steps to reproduce:* 1. Create notebook of the same template in Project1 *Actual result:* 1. Notebook creation fails *Expected result:* 1. Notebook creation is successful 1. Also Spark cluster creation fails with the same error. The bug was reproduced on Zeppelin notebook. But I think it is not depends on notebook. was: *Preconditions:* # Project1 is created on GCP with disabled 'use shared image' # Notebook1 is created *Steps to reproduce:* 1. Create notebook of the same template in Project1 *Actual result:* 1. Notebook creation fails *Expected result:* 1. Notebook creation is successful 1. Also Spark cluster creation fails with the same error. > [GSP]: Notebook creation fails from image > - > > Key: DLAB-1627 > URL: https://issues.apache.org/jira/browse/DLAB-1627 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Debian, DevOps, GCP > Attachments: GCP console.png, Notebook creation.png, Spark cluster > creation.png > > > *Preconditions:* > # Project1 is created on GCP with disabled 'use shared image' > # Notebook1 is created > *Steps to reproduce:* > 1. Create notebook of the same template in Project1 > *Actual result:* > 1. Notebook creation fails > *Expected result:* > 1. Notebook creation is successful > > 1. Also Spark cluster creation fails with the same error. > The bug was reproduced on Zeppelin notebook. But I think it is not depends > on notebook. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1624) [GCP]: Notebook stopping fails on remote GCP endpoint
[ https://issues.apache.org/jira/browse/DLAB-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleh Martushevskyi reassigned DLAB-1624: Assignee: Leonid Frolov (was: Oleh Martushevskyi) > [GCP]: Notebook stopping fails on remote GCP endpoint > - > > Key: DLAB-1624 > URL: https://issues.apache.org/jira/browse/DLAB-1624 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > Attachments: GCP notebook stopping.png > > > *Preconditions:* > 1. Notebook is created on GCP remote endpoint > *Steps to reproduce:* > 1. Stop notebook > *Actual result:* > 1. Notebook stopping fails > *Expected result:* > 1. Notebook stopping is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1625) [GCP]: Edge node starting fails on remote GCP endpoint
[ https://issues.apache.org/jira/browse/DLAB-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleh Martushevskyi reassigned DLAB-1625: Assignee: Leonid Frolov (was: Oleh Martushevskyi) > [GCP]: Edge node starting fails on remote GCP endpoint > > > Key: DLAB-1625 > URL: https://issues.apache.org/jira/browse/DLAB-1625 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > Attachments: GCP edge node starting.png > > > *Preconditions:* > 1. Edge is created on GCP remote endpoint > 2. Edge node is in stopping status > *Steps to reproduce:* > 1. Start edge node on GCP remote endpoint > *Actual result:* > 1. Edge node stopping fails > *Expected result:* > 1. Edge node stopping is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1225) [Azure]: Failed ssn creation is still running on Azure console
[ https://issues.apache.org/jira/browse/DLAB-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleh Martushevskyi reassigned DLAB-1225: Assignee: Mykola Bodnar (was: Oleh Martushevskyi) > [Azure]: Failed ssn creation is still running on Azure console > -- > > Key: DLAB-1225 > URL: https://issues.apache.org/jira/browse/DLAB-1225 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main > Environment: AZURE >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: 2.3_old, AZURE, Debian, DevOps > Fix For: v.2.3 > > > *Preconditions:* > 1. It is impossible to connect to pkg.jenkins.io > *Steps to reproduce:* > # Deploy DLab via Jenkins job > *Actual result:* > 1. SSN deployment fails > 2. SSN is running on Azure console > *Expected result:* > 1. SSN deployment fails > 2. SSN is terminated on Azure console > Please, see Jenkins job v2.2 #223/#222 > > (i) Now SSN creation was failed on the other stage, however SSN was still > running on Azure console. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1626) [GCP]: Notebook termination fails if notebook contains Dataproc
[ https://issues.apache.org/jira/browse/DLAB-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonid Frolov reassigned DLAB-1626: --- Assignee: Leonid Frolov (was: Oleh Martushevskyi) > [GCP]: Notebook termination fails if notebook contains Dataproc > --- > > Key: DLAB-1626 > URL: https://issues.apache.org/jira/browse/DLAB-1626 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Debian, DevOps, GCP > Attachments: GCP Notebook termination.png > > > Dataproc was created on Jupyter. However i think it is related to all > notebooks. > *Preconditions:* > 1. Dataproc is created > *Steps to reproduce:* > 1. Terminate notebook > Actual result: > 1. Notebook termination fail > *Expected result:* > 1. Notebook termination is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1627) [GSP]: Notebook creation fails from image
[ https://issues.apache.org/jira/browse/DLAB-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleh Martushevskyi reassigned DLAB-1627: Assignee: Leonid Frolov (was: Oleh Martushevskyi) > [GSP]: Notebook creation fails from image > - > > Key: DLAB-1627 > URL: https://issues.apache.org/jira/browse/DLAB-1627 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Debian, DevOps, GCP > Attachments: GCP console.png, Notebook creation.png, Spark cluster > creation.png > > > *Preconditions:* > # Project1 is created on GCP with disabled 'use shared image' > # Notebook1 is created > *Steps to reproduce:* > 1. Create notebook of the same template in Project1 > *Actual result:* > 1. Notebook creation fails > *Expected result:* > 1. Notebook creation is successful > > 1. Also Spark cluster creation fails with the same error. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1627) [GSP]: Notebook creation fails from image
Vira Vitanska created DLAB-1627: --- Summary: [GSP]: Notebook creation fails from image Key: DLAB-1627 URL: https://issues.apache.org/jira/browse/DLAB-1627 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Attachments: GCP console.png, Notebook creation.png, Spark cluster creation.png *Preconditions:* # Project1 is created on GCP with disabled 'use shared image' # Notebook1 is created *Steps to reproduce:* 1. Create notebook of the same template in Project1 *Actual result:* 1. Notebook creation fails *Expected result:* 1. Notebook creation is successful 1. Also Spark cluster creation fails with the same error. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] DG1202 merged pull request #648: [DLAB-1618]: Adjusted role page according to requirements
DG1202 merged pull request #648: [DLAB-1618]: Adjusted role page according to requirements URL: https://github.com/apache/incubator-dlab/pull/648 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1618) Adjust role page according to requirements
[ https://issues.apache.org/jira/browse/DLAB-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated DLAB-1618: - Labels: AWS AZURE Debian Front-end GCP RedHat pull-request-available (was: AWS AZURE Debian Front-end GCP RedHat) > Adjust role page according to requirements > -- > > Key: DLAB-1618 > URL: https://issues.apache.org/jira/browse/DLAB-1618 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: Changes are not confirmed.jpg, Information message.jpg > > > # Changes are not confirmed in role if users column is empty > # 'Success! Group data successfully updated, but users did't delete from > group!' -> 'Success! Group data is updated successfully, but user isn't > delete from group!' > # 'Success! Group data successfully updated!' -> 'Success! Group data is > updated successfully!' > # If add a new user and don't reload page and delete this added user the > confirmation message is absent > # If confirm a user removing and don't reload page and delete the other user > of this group in confirmation message should not contain the previous deleted > user > > If there is any changes should be visible hint for confirmation -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] DG1202 opened a new pull request #648: [DLAB-1618]: Adjusted role page according to requirements
DG1202 opened a new pull request #648: [DLAB-1618]: Adjusted role page according to requirements URL: https://github.com/apache/incubator-dlab/pull/648 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1626) [GCP]: Notebook termination fails if notebook contains Dataproc
[ https://issues.apache.org/jira/browse/DLAB-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1626: Summary: [GCP]: Notebook termination fails if notebook contains Dataproc (was: [GCP]: Terminating notebook fails if notebook contains Dataproc) > [GCP]: Notebook termination fails if notebook contains Dataproc > --- > > Key: DLAB-1626 > URL: https://issues.apache.org/jira/browse/DLAB-1626 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: Debian, DevOps, GCP > Attachments: GCP Notebook termination.png > > > Dataproc was created on Jupyter. However i think it is related to all > notebooks. > *Preconditions:* > 1. Dataproc is created > *Steps to reproduce:* > 1. Terminate notebook > Actual result: > 1. Notebook termination fail > *Expected result:* > 1. Notebook termination is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1626) [GCP]: Terminating notebook fails if notebook contains Dataproc
Vira Vitanska created DLAB-1626: --- Summary: [GCP]: Terminating notebook fails if notebook contains Dataproc Key: DLAB-1626 URL: https://issues.apache.org/jira/browse/DLAB-1626 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Attachments: GCP Notebook termination.png Dataproc was created on Jupyter. However i think it is related to all notebooks. *Preconditions:* 1. Dataproc is created *Steps to reproduce:* 1. Terminate notebook Actual result: 1. Notebook termination fail *Expected result:* 1. Notebook termination is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1225) [Azure]: Failed ssn creation is still running on Azure console
[ https://issues.apache.org/jira/browse/DLAB-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1225: --- Assignee: Oleh Martushevskyi (was: Mykola Bodnar) > [Azure]: Failed ssn creation is still running on Azure console > -- > > Key: DLAB-1225 > URL: https://issues.apache.org/jira/browse/DLAB-1225 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main > Environment: AZURE >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Minor > Labels: 2.3_old, AZURE, Debian, DevOps > Fix For: v.2.3 > > > *Preconditions:* > 1. It is impossible to connect to pkg.jenkins.io > *Steps to reproduce:* > # Deploy DLab via Jenkins job > *Actual result:* > 1. SSN deployment fails > 2. SSN is running on Azure console > *Expected result:* > 1. SSN deployment fails > 2. SSN is terminated on Azure console > Please, see Jenkins job v2.2 #223/#222 > > (i) Now SSN creation was failed on the other stage, however SSN was still > running on Azure console. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1225) [Azure]: Failed ssn creation is still running on Azure console
[ https://issues.apache.org/jira/browse/DLAB-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1225: Description: *Preconditions:* 1. It is impossible to connect to pkg.jenkins.io *Steps to reproduce:* # Deploy DLab via Jenkins job *Actual result:* 1. SSN deployment fails 2. SSN is running on Azure console *Expected result:* 1. SSN deployment fails 2. SSN is terminated on Azure console Please, see Jenkins job v2.2 #223/#222 (i) Now SSN creation was failed on the other stage, however SSN was still running on Azure console. was: *Preconditions:* 1. It is impossible to connect to pkg.jenkins.io *Steps to reproduce:* # Deploy DLab via Jenkins job *Actual result:* 1. SSN deployment fails 2. SSN is running on Azure console *Expected result:* 1. SSN deployment fails 2. SSN is terminated on Azure console Please, see Jenkins job v2.2 #223/#222 - (i) The bug is not reproduced with SSN creation, however if another instance creation fails this instance is still running on Azure console > [Azure]: Failed ssn creation is still running on Azure console > -- > > Key: DLAB-1225 > URL: https://issues.apache.org/jira/browse/DLAB-1225 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main > Environment: AZURE >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: 2.3_old, AZURE, Debian, DevOps > Fix For: v.2.3 > > > *Preconditions:* > 1. It is impossible to connect to pkg.jenkins.io > *Steps to reproduce:* > # Deploy DLab via Jenkins job > *Actual result:* > 1. SSN deployment fails > 2. SSN is running on Azure console > *Expected result:* > 1. SSN deployment fails > 2. SSN is terminated on Azure console > Please, see Jenkins job v2.2 #223/#222 > > (i) Now SSN creation was failed on the other stage, however SSN was still > running on Azure console. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1225) [Azure]: Failed ssn creation is still running on Azure console
[ https://issues.apache.org/jira/browse/DLAB-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1225: Summary: [Azure]: Failed ssn creation is still running on Azure console (was: [Azure]: Failed instance creation is still running on Azure console) > [Azure]: Failed ssn creation is still running on Azure console > -- > > Key: DLAB-1225 > URL: https://issues.apache.org/jira/browse/DLAB-1225 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main > Environment: AZURE >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: 2.3_old, AZURE, Debian, DevOps > Fix For: v.2.3 > > > *Preconditions:* > 1. It is impossible to connect to pkg.jenkins.io > *Steps to reproduce:* > # Deploy DLab via Jenkins job > *Actual result:* > 1. SSN deployment fails > 2. SSN is running on Azure console > *Expected result:* > 1. SSN deployment fails > 2. SSN is terminated on Azure console > Please, see Jenkins job v2.2 #223/#222 > - > (i) The bug is not reproduced with SSN creation, however if another instance > creation fails this instance is still running on Azure console -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1225) [Azure]: Failed instance creation is still running on Azure console
[ https://issues.apache.org/jira/browse/DLAB-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1225: Sprint: Apache DLab release 2.3 > [Azure]: Failed instance creation is still running on Azure console > --- > > Key: DLAB-1225 > URL: https://issues.apache.org/jira/browse/DLAB-1225 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main > Environment: AZURE >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: 2.3_old, AZURE, Debian, DevOps > Fix For: v.2.3 > > > *Preconditions:* > 1. It is impossible to connect to pkg.jenkins.io > *Steps to reproduce:* > # Deploy DLab via Jenkins job > *Actual result:* > 1. SSN deployment fails > 2. SSN is running on Azure console > *Expected result:* > 1. SSN deployment fails > 2. SSN is terminated on Azure console > Please, see Jenkins job v2.2 #223/#222 > - > (i) The bug is not reproduced with SSN creation, however if another instance > creation fails this instance is still running on Azure console -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1225) [Azure]: Failed instance creation is still running on Azure console
[ https://issues.apache.org/jira/browse/DLAB-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1225: Description: *Preconditions:* 1. It is impossible to connect to pkg.jenkins.io *Steps to reproduce:* # Deploy DLab via Jenkins job *Actual result:* 1. SSN deployment fails 2. SSN is running on Azure console *Expected result:* 1. SSN deployment fails 2. SSN is terminated on Azure console Please, see Jenkins job v2.2 #223/#222 - (i) The bug is not reproduced with SSN creation, however if another instance creation fails this instance is still running on Azure console was: *Preconditions:* 1. It is impossible to connect to pkg.jenkins.io *Steps to reproduce:* # Deploy DLab via Jenkins job *Actual result:* 1. SSN deployment fails 2. SSN is running on Azure console *Expected result:* 1. SSN deployment fails 2. SSN is terminated on Azure console Please, see Jenkins job v2.2 #223/#222 > [Azure]: Failed instance creation is still running on Azure console > --- > > Key: DLAB-1225 > URL: https://issues.apache.org/jira/browse/DLAB-1225 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main > Environment: AZURE >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: 2.3_old, AZURE, Debian, DevOps > Fix For: v.2.3 > > > *Preconditions:* > 1. It is impossible to connect to pkg.jenkins.io > *Steps to reproduce:* > # Deploy DLab via Jenkins job > *Actual result:* > 1. SSN deployment fails > 2. SSN is running on Azure console > *Expected result:* > 1. SSN deployment fails > 2. SSN is terminated on Azure console > Please, see Jenkins job v2.2 #223/#222 > - > (i) The bug is not reproduced with SSN creation, however if another instance > creation fails this instance is still running on Azure console -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1225) [Azure]: Failed instance creation is still running on Azure console
[ https://issues.apache.org/jira/browse/DLAB-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1225: Summary: [Azure]: Failed instance creation is still running on Azure console (was: [Azure]: Failed ssn on stage creation is still running on Azure console) > [Azure]: Failed instance creation is still running on Azure console > --- > > Key: DLAB-1225 > URL: https://issues.apache.org/jira/browse/DLAB-1225 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main > Environment: AZURE >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: 2.3_old, AZURE, Debian, DevOps > Fix For: v.2.3 > > > *Preconditions:* > 1. It is impossible to connect to pkg.jenkins.io > *Steps to reproduce:* > # Deploy DLab via Jenkins job > *Actual result:* > 1. SSN deployment fails > 2. SSN is running on Azure console > *Expected result:* > 1. SSN deployment fails > 2. SSN is terminated on Azure console > > Please, see Jenkins job v2.2 #223/#222 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1478) [Project page][Environment management]: Status should not blink during refreshing
[ https://issues.apache.org/jira/browse/DLAB-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057687#comment-17057687 ] Vira Vitanska commented on DLAB-1478: - Reopened: 1. The blink is still reproduced on environment management page, see attachments. 2. Alignment should have consistency on projects page > [Project page][Environment management]: Status should not blink during > refreshing > --- > > Key: DLAB-1478 > URL: https://issues.apache.org/jira/browse/DLAB-1478 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Trivial > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Environment management.png, Project.png, Reopened > alignment.png, Reopened environment management.mov > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1478) [Project page][Environment management]: Status should not blink during refreshing
[ https://issues.apache.org/jira/browse/DLAB-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1478: Attachment: Reopened alignment.png > [Project page][Environment management]: Status should not blink during > refreshing > --- > > Key: DLAB-1478 > URL: https://issues.apache.org/jira/browse/DLAB-1478 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Trivial > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Environment management.png, Project.png, Reopened > alignment.png, Reopened environment management.mov > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1478) [Project page][Environment management]: Status should not blink during refreshing
[ https://issues.apache.org/jira/browse/DLAB-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1478: Attachment: Reopened environment management.mov > [Project page][Environment management]: Status should not blink during > refreshing > --- > > Key: DLAB-1478 > URL: https://issues.apache.org/jira/browse/DLAB-1478 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Trivial > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Environment management.png, Project.png, Reopened > environment management.mov > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
