[jira] [Commented] (AIRAVATA-2506) Sharing Registry: Error updating user when changed
[
https://issues.apache.org/jira/browse/AIRAVATA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122156#comment-16122156
]
Supun Chathuranga Nakandala commented on AIRAVATA-2506:
---
I made the change and tested on develop branch. Marking as resolved
> Sharing Registry: Error updating user when changed
> --
>
> Key: AIRAVATA-2506
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2506
> Project: Airavata
> Issue Type: Improvement
> Components: Airavata System
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
> Fix For: 0.19
>
>
> Exception:
> {noformat}
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - New DB Event message to sharing
> service.
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - DB Event message to sharing
> service from user.profile
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - User profile specific DB Event
> communicated by user.profile
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - Updating user. User Id :
> eabey...@iu.edu
> 2017-08-04 20:35:41,874 [pool-15-thread-1] ERROR
> o.a.a.s.r.s.SharingRegistryServerHandler - null
> java.lang.NullPointerException: null
> at
> org.apache.airavata.sharing.registry.server.SharingRegistryServerHandler.updatedUser(SharingRegistryServerHandler.java:180)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3992)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3976)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> 2017-08-04 20:35:41,874 [pool-18-thread-3] ERROR
> o.a.a.s.r.m.SharingServiceDBEventHandler - Error processing message.
> org.apache.airavata.sharing.registry.models.SharingRegistryException: null
> Stack trace:java.lang.NullPointerException
> at
> org.apache.airavata.sharing.registry.server.SharingRegistryServerHandler.updatedUser(SharingRegistryServerHandler.java:180)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3992)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3976)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$updatedUser_result$updatedUser_resultStandardScheme.read(SharingRegistryService.java:15260)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$updatedUser_result$updatedUser_resultStandardScheme.read(SharingRegistryService.java:15238)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$updatedUser_result.read(SharingRegistryService.java:15182)
> at
> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:89)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Client.recv_updatedUser(SharingRegistryService.java:757)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Client.updatedUser(SharingRegistryService.java:744)
> at
> org.apache.airavata.sharing.registry.messaging.SharingServiceDBEventHandler.onMessage(SharingServiceDBEventHandler.java:104)
> at
> org.apache.airavata.messaging.core.impl.MessageConsumer.handleDelivery(MessageConsumer.java:70)
> at
> com.rabbitmq.client.impl.ConsumerDispatcher$5.run(ConsumerDispatcher.java:144)
> at
>
[jira] [Resolved] (AIRAVATA-2506) Sharing Registry: Error updating user when changed
[
https://issues.apache.org/jira/browse/AIRAVATA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Chathuranga Nakandala resolved AIRAVATA-2506.
---
Resolution: Fixed
> Sharing Registry: Error updating user when changed
> --
>
> Key: AIRAVATA-2506
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2506
> Project: Airavata
> Issue Type: Improvement
> Components: Airavata System
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
> Fix For: 0.19
>
>
> Exception:
> {noformat}
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - New DB Event message to sharing
> service.
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - DB Event message to sharing
> service from user.profile
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - User profile specific DB Event
> communicated by user.profile
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - Updating user. User Id :
> eabey...@iu.edu
> 2017-08-04 20:35:41,874 [pool-15-thread-1] ERROR
> o.a.a.s.r.s.SharingRegistryServerHandler - null
> java.lang.NullPointerException: null
> at
> org.apache.airavata.sharing.registry.server.SharingRegistryServerHandler.updatedUser(SharingRegistryServerHandler.java:180)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3992)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3976)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> 2017-08-04 20:35:41,874 [pool-18-thread-3] ERROR
> o.a.a.s.r.m.SharingServiceDBEventHandler - Error processing message.
> org.apache.airavata.sharing.registry.models.SharingRegistryException: null
> Stack trace:java.lang.NullPointerException
> at
> org.apache.airavata.sharing.registry.server.SharingRegistryServerHandler.updatedUser(SharingRegistryServerHandler.java:180)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3992)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3976)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$updatedUser_result$updatedUser_resultStandardScheme.read(SharingRegistryService.java:15260)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$updatedUser_result$updatedUser_resultStandardScheme.read(SharingRegistryService.java:15238)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$updatedUser_result.read(SharingRegistryService.java:15182)
> at
> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:89)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Client.recv_updatedUser(SharingRegistryService.java:757)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Client.updatedUser(SharingRegistryService.java:744)
> at
> org.apache.airavata.sharing.registry.messaging.SharingServiceDBEventHandler.onMessage(SharingServiceDBEventHandler.java:104)
> at
> org.apache.airavata.messaging.core.impl.MessageConsumer.handleDelivery(MessageConsumer.java:70)
> at
> com.rabbitmq.client.impl.ConsumerDispatcher$5.run(ConsumerDispatcher.java:144)
> at
> com.rabbitmq.client.impl.ConsumerWorkService$WorkPoolRunnable.run(ConsumerWorkService.java:99)
> at
>
[jira] [Assigned] (AIRAVATA-2506) Sharing Registry: Error updating user when changed
[
https://issues.apache.org/jira/browse/AIRAVATA-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Chathuranga Nakandala reassigned AIRAVATA-2506:
-
Assignee: Supun Chathuranga Nakandala (was: Marcus Christie)
> Sharing Registry: Error updating user when changed
> --
>
> Key: AIRAVATA-2506
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2506
> Project: Airavata
> Issue Type: Improvement
> Components: Airavata System
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
> Fix For: 0.19
>
>
> Exception:
> {noformat}
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - New DB Event message to sharing
> service.
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - DB Event message to sharing
> service from user.profile
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - User profile specific DB Event
> communicated by user.profile
> 2017-08-04 20:35:41,869 [pool-18-thread-3] INFO
> o.a.a.s.r.m.SharingServiceDBEventHandler - Updating user. User Id :
> eabey...@iu.edu
> 2017-08-04 20:35:41,874 [pool-15-thread-1] ERROR
> o.a.a.s.r.s.SharingRegistryServerHandler - null
> java.lang.NullPointerException: null
> at
> org.apache.airavata.sharing.registry.server.SharingRegistryServerHandler.updatedUser(SharingRegistryServerHandler.java:180)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3992)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3976)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> 2017-08-04 20:35:41,874 [pool-18-thread-3] ERROR
> o.a.a.s.r.m.SharingServiceDBEventHandler - Error processing message.
> org.apache.airavata.sharing.registry.models.SharingRegistryException: null
> Stack trace:java.lang.NullPointerException
> at
> org.apache.airavata.sharing.registry.server.SharingRegistryServerHandler.updatedUser(SharingRegistryServerHandler.java:180)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3992)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Processor$updatedUser.getResult(SharingRegistryService.java:3976)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$updatedUser_result$updatedUser_resultStandardScheme.read(SharingRegistryService.java:15260)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$updatedUser_result$updatedUser_resultStandardScheme.read(SharingRegistryService.java:15238)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$updatedUser_result.read(SharingRegistryService.java:15182)
> at
> org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:89)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Client.recv_updatedUser(SharingRegistryService.java:757)
> at
> org.apache.airavata.sharing.registry.service.cpi.SharingRegistryService$Client.updatedUser(SharingRegistryService.java:744)
> at
> org.apache.airavata.sharing.registry.messaging.SharingServiceDBEventHandler.onMessage(SharingServiceDBEventHandler.java:104)
> at
> org.apache.airavata.messaging.core.impl.MessageConsumer.handleDelivery(MessageConsumer.java:70)
> at
> com.rabbitmq.client.impl.ConsumerDispatcher$5.run(ConsumerDispatcher.java:144)
> at
>
[jira] [Resolved] (AIRAVATA-2499) Introduce List of values for an application input
[ https://issues.apache.org/jira/browse/AIRAVATA-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2499. --- Resolution: Fixed > Introduce List of values for an application input > - > > Key: AIRAVATA-2499 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2499 > Project: Airavata > Issue Type: New Feature > Components: Application Catalog, PGA PHP Web Gateway >Affects Versions: 0.17 >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.18 > > > Introducing list of values (LOV) for application input > 1. For any application input type (except for URI) can provide a list of > values separated by comma by the gateway admin > 2. These values are defined in the application interface for each input > 3. First value is the default. > 4. When providing the list, no spaces and separated by comma > 5. At creation, edit and clone user can select a single value from the list. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-2310) Storage resource does not work with gateway profile level credential store token
[ https://issues.apache.org/jira/browse/AIRAVATA-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2310. --- Resolution: Fixed > Storage resource does not work with gateway profile level credential store > token > > > Key: AIRAVATA-2310 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2310 > Project: Airavata > Issue Type: Bug > Components: GFac, PGA PHP Web Gateway >Affects Versions: 0.17 > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.18 > > > Storage resource does not work with gateway profile level credential store > token. > Currently when the generated token is set at gateway level compute resources > work using the token for ssh submissions (if individual tokens are not set at > resource level). > But storage resources are only working at individual resource level. If the > token is not set at resource level ssh submissions fails. The gateway level > set token is not taken into consideration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-2467) When given *.chk as the value for the output file in an application. File(s) with that extension is not listed in the summary.
[ https://issues.apache.org/jira/browse/AIRAVATA-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2467. --- Resolution: Fixed > When given *.chk as the value for the output file in an application. File(s) > with that extension is not listed in the summary. > -- > > Key: AIRAVATA-2467 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2467 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17 > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.18 > > > When * is given the system takes * as the name of the file. Not to bring all > the files with .chk extension. Adding * should mean to bring back all the > files with the extension provided. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-2353) When a defined job output is not generated and not existing exception thrown when user tries to view it
[ https://issues.apache.org/jira/browse/AIRAVATA-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2353. --- Resolution: Fixed > When a defined job output is not generated and not existing exception thrown > when user tries to view it > --- > > Key: AIRAVATA-2353 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2353 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17 > Environment: http://149.165.156.11/ (all airavata environments have > this issue) >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.18 > > > Gateway admins can define application outputs expected in application > interface configuration of the gateway. > If one of those defined outputs are not generated, they will not be available > in the user data for user to download. But since it is defined it will appear > in experiment summary with a fake link. When clicked getting a > FileNotFoundException. > Ideally if a defined file is not generated/ existing in the data directory > that should not appear in the summary. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-1958) Currently in Create,edit and clone experiment there is no validation between number of nodes and CPUs. This need to be added to Airavata
[ https://issues.apache.org/jira/browse/AIRAVATA-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1958. --- Resolution: Fixed > Currently in Create,edit and clone experiment there is no validation between > number of nodes and CPUs. This need to be added to Airavata > > > Key: AIRAVATA-1958 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1958 > Project: Airavata > Issue Type: Bug > Components: Airavata System, PGA PHP Web Gateway >Affects Versions: 0.16 >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.18 > > > Currently we define maximum number of nodes and CPUs for a given resource but > the validation between nodes and CPUs does not exist. > This was discussed to implement. Users will be asked to enter CPUs and > required number of nodes will be auto generated by the system and entered. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-2031) Set configuration of default Node count and CPU Count per compute resource.
[ https://issues.apache.org/jira/browse/AIRAVATA-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2031. --- Resolution: Fixed > Set configuration of default Node count and CPU Count per compute resource. > --- > > Key: AIRAVATA-2031 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2031 > Project: Airavata > Issue Type: Task > Components: PGA PHP Web Gateway >Affects Versions: 0.17 >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Currently the default wall-time, node count and CPU count are set globally at > gateway level in pga_config.php per gateway. > Going forward CPU count and nod count default values should be set based on > the compute resource and gateway. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-2424) Queue specific macros are not added to the job script
[ https://issues.apache.org/jira/browse/AIRAVATA-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2424. --- Resolution: Fixed > Queue specific macros are not added to the job script > - > > Key: AIRAVATA-2424 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2424 > Project: Airavata > Issue Type: Bug >Affects Versions: 0.18 > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.18 > > > Added a queue specific macro in SciGaP portal to be addd to the job script > when a job is submit to the specific queue. > The macro is not in the job script when experiment is launched. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-2397) node, walltime and CPUs are not displayed when compute resource is selected
[ https://issues.apache.org/jira/browse/AIRAVATA-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2397. --- Resolution: Fixed > node, walltime and CPUs are not displayed when compute resource is selected > --- > > Key: AIRAVATA-2397 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2397 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > In experiment creation page when the compute resource is selected queue > appears but not rest of the configuration. Wall-time, CPU and node count > details are not displayed. When the experiment is launched they appear in > summary page. user cannot change or view the values prior to launching the > experiment > Cloned the same experiment and these values are displayed there. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-1941) Cannot view STDOUT and STDERR of applications which has special characters in PGA storage
[ https://issues.apache.org/jira/browse/AIRAVATA-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1941. --- Resolution: Fixed fixed in dev.seagrid > Cannot view STDOUT and STDERR of applications which has special characters in > PGA storage > - > > Key: AIRAVATA-1941 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1941 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.18 > > Attachments: Screen Shot 2016-03-25 at 12.11.21 PM.png > > > For application DFTB the stdout and stderr is generated as DFTB+.stderr & > DFTB+.stdout > When tried to view them in the storage in PGA gives the attached error. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-2264) In project summary when listing experiment display the Creation Time instead of Last Modified Time
[ https://issues.apache.org/jira/browse/AIRAVATA-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2264. --- Resolution: Fixed resolved in dev.seagrid.org > In project summary when listing experiment display the Creation Time instead > of Last Modified Time > -- > > Key: AIRAVATA-2264 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2264 > Project: Airavata > Issue Type: Bug > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.18 > > > In experiment browse we display the experiment Creation Time. Similar to > those in Project Summary please display Creation Time as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-2353) When a defined job output is not generated and not existing exception thrown when user tries to view it
[ https://issues.apache.org/jira/browse/AIRAVATA-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2353. --- Resolution: Fixed resolved in dev.seagrid.org > When a defined job output is not generated and not existing exception thrown > when user tries to view it > --- > > Key: AIRAVATA-2353 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2353 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17 > Environment: http://149.165.156.11/ (all airavata environments have > this issue) >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17 > > > Gateway admins can define application outputs expected in application > interface configuration of the gateway. > If one of those defined outputs are not generated, they will not be available > in the user data for user to download. But since it is defined it will appear > in experiment summary with a fake link. When clicked getting a > FileNotFoundException. > Ideally if a defined file is not generated/ existing in the data directory > that should not appear in the summary. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (AIRAVATA-1863) Please validate existence of defined application inputs at Create and Launch Experiment level in Airavata
[ https://issues.apache.org/jira/browse/AIRAVATA-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1863. --- Resolution: Fixed > Please validate existence of defined application inputs at Create and Launch > Experiment level in Airavata > - > > Key: AIRAVATA-1863 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1863 > Project: Airavata > Issue Type: Bug > Components: Airavata System >Affects Versions: 0.16 > Environment: SEAGrid desktop client and Airavata server >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17 > > Attachments: Screen Shot 2015-10-23 at 2.40.44 PM.png > > > When an experiment is created application level defined inputs need to be > validated for existence. If the files are not existing the experiment should > fail. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AIRAVATA-2353) When a defined job output is not generated and not existing exception thrown when user tries to view it
[ https://issues.apache.org/jira/browse/AIRAVATA-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2353. --- Resolution: Fixed > When a defined job output is not generated and not existing exception thrown > when user tries to view it > --- > > Key: AIRAVATA-2353 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2353 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17 > Environment: http://149.165.156.11/ (all airavata environments have > this issue) >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17 > > > Gateway admins can define application outputs expected in application > interface configuration of the gateway. > If one of those defined outputs are not generated, they will not be available > in the user data for user to download. But since it is defined it will appear > in experiment summary with a fake link. When clicked getting a > FileNotFoundException. > Ideally if a defined file is not generated/ existing in the data directory > that should not appear in the summary. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AIRAVATA-2344) In airavata 0.17 JS deployment cannot create and save new project
[
https://issues.apache.org/jira/browse/AIRAVATA-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Chathuranga Nakandala resolved AIRAVATA-2344.
---
Resolution: Fixed
> In airavata 0.17 JS deployment cannot create and save new project
> -
>
> Key: AIRAVATA-2344
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2344
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
>Affects Versions: 0.17
> Environment: http://149.165.156.11/
>Reporter: Eroma
>Assignee: Supun Chathuranga Nakandala
> Fix For: 0.17
>
>
> When tried to save a new project getting application exception:
> Required field 'projectId' was not present! Struct:
> getProject_args(authzToken:AuthzToken(accessToken:41e7af126fe00bf259730ecac78d0551,
> claimsMap:{userName=ProdEroma2017, gatewayID=seagrid}), projectId:null)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AIRAVATA-1880) In Application Interface ability to make inputs unchangeable by the end user.
[ https://issues.apache.org/jira/browse/AIRAVATA-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1880. --- Resolution: Fixed > In Application Interface ability to make inputs unchangeable by the end user. > - > > Key: AIRAVATA-1880 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1880 > Project: Airavata > Issue Type: Improvement > Components: Airavata System >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17 > > > Currently all the interface inputs we add (String and it could be integer, > float, etc...) can be changed at Create Experiment by the user. > There are some string inputs which we don't want to be changed; It would be > useful and less room for errors if we could make these types of inputs either > unchangeable or if we don't want user to change we can hide them from Create > Experiment -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (AIRAVATA-2218) Cannot change name of project
[
https://issues.apache.org/jira/browse/AIRAVATA-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Chathuranga Nakandala resolved AIRAVATA-2218.
---
Resolution: Fixed
> Cannot change name of project
> -
>
> Key: AIRAVATA-2218
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2218
> Project: Airavata
> Issue Type: Bug
> Components: Registry API
> Environment: dev.seagrid.org
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
> Fix For: 0.17
>
>
> h5. Steps to reproduce
> # Create a project
> # Edit the project
> # Change the name and click Save
> h5. Actual Results
> * Project summary page reload with old project name
> h5. Expected Results
> * Project summary page should reload with the new project name
> Registry server exception
> {noformat}
> 2016-11-08 16:48:37 [pool-1-thread-3370] ERROR
> o.a.a.r.a.s.h.RegistryServerHandler - Error while updating the project
> org.apache.airavata.registry.cpi.RegistryException: Error while updating the
> resource..PROJECT
> at
> org.apache.airavata.registry.core.experiment.catalog.impl.ExperimentCatalogImpl.update(ExperimentCatalogImpl.java:276)
> at
> org.apache.airavata.registry.api.service.handler.RegistryServerHandler.updateProject(RegistryServerHandler.java:3414)
> at
> org.apache.airavata.registry.api.RegistryService$Processor$updateProject.getResult(RegistryService.java:12180)
> at
> org.apache.airavata.registry.api.RegistryService$Processor$updateProject.getResult(RegistryService.java:12164)
> at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
> at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.airavata.registry.cpi.RegistryException:
> java.lang.NullPointerException
> at
> org.apache.airavata.registry.core.experiment.catalog.impl.ProjectRegistry.updateProject(ProjectRegistry.java:148)
> at
> org.apache.airavata.registry.core.experiment.catalog.impl.ExperimentCatalogImpl.update(ExperimentCatalogImpl.java:217)
> ... 9 common frames omitted
> Caused by: java.lang.NullPointerException: null
> at
> org.apache.airavata.registry.core.experiment.catalog.impl.ProjectRegistry.updateProject(ProjectRegistry.java:115)
> ... 10 common frames omitted
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (AIRAVATA-2314) Job notification emails from tandy super computer at OII are not processed by gfac.
[ https://issues.apache.org/jira/browse/AIRAVATA-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2314. --- Resolution: Fixed > Job notification emails from tandy super computer at OII are not processed by > gfac. > --- > > Key: AIRAVATA-2314 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2314 > Project: Airavata > Issue Type: Bug > Components: GFac, PGA PHP Web Gateway >Affects Versions: 0.17 > Environment: http://scigw.oii.org/ >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17 > > > The emails are received by the production server email. But they are not > processed. > Hence the jobs are in QUEUED state without updating further. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] (AIRAVATA-2310) Storage resource does not work with gateway profile level credential store token
Title: Message Title Supun Chathuranga Nakandala resolved as Fixed Airavata / AIRAVATA-2310 Storage resource does not work with gateway profile level credential store token Change By: Supun Chathuranga Nakandala Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (AIRAVATA-2266) When tried to create tenant it asked to enter the auth key and the secret
Title: Message Title Supun Chathuranga Nakandala resolved as Fixed Airavata / AIRAVATA-2266 When tried to create tenant it asked to enter the auth key and the secret Change By: Supun Chathuranga Nakandala Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (AIRAVATA-2309) SHARING table: MySQL complains "Specified key was too long; max key length is 3072 bytes"
Title: Message Title Supun Chathuranga Nakandala resolved as Fixed Airavata / AIRAVATA-2309 SHARING table: MySQL complains "Specified key was too long; max key length is 3072 bytes" Change By: Supun Chathuranga Nakandala Resolution: Fixed Status: Reopened Resolved Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (AIRAVATA-1517) When there are no JobManager Commands, Empty records get created upon updating Job Submission Protocols
Title: Message Title Supun Chathuranga Nakandala resolved as Fixed Airavata / AIRAVATA-1517 When there are no JobManager Commands, Empty records get created upon updating Job Submission Protocols Change By: Supun Chathuranga Nakandala Resolution: Fixed Status: Reopened Resolved Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (AIRAVATA-2267) In view credential please show the domain.
Title: Message Title Supun Chathuranga Nakandala resolved as Fixed Airavata / AIRAVATA-2267 In view credential please show the domain. Change By: Supun Chathuranga Nakandala Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (AIRAVATA-2265) in SciGaP latest record should be on top of the list in Gateway requests.
Title: Message Title Supun Chathuranga Nakandala resolved as Fixed Airavata / AIRAVATA-2265 in SciGaP latest record should be on top of the list in Gateway requests. Change By: Supun Chathuranga Nakandala Resolution: Fixed Status: Open Resolved Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] (AIRAVATA-2309) SHARING table: MySQL complains "Specified key was too long; max key length is 3072 bytes"
Title: Message Title Supun Chathuranga Nakandala commented on AIRAVATA-2309 Re: SHARING table: MySQL complains "Specified key was too long; max key length is 3072 bytes" Marcus Christie Can you test now. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
[jira] [Resolved] (AIRAVATA-2309) SHARING table: MySQL complains "Specified key was too long; max key length is 3072 bytes"
[
https://issues.apache.org/jira/browse/AIRAVATA-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Chathuranga Nakandala resolved AIRAVATA-2309.
---
Resolution: Fixed
> SHARING table: MySQL complains "Specified key was too long; max key length is
> 3072 bytes"
> -
>
> Key: AIRAVATA-2309
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2309
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> Error occurs while trying to create the SHARING table:
> {code:sql}
> CREATE TABLE SHARING (
> PERMISSION_TYPE_ID VARCHAR(255) NOT NULL,
> ENTITY_ID VARCHAR(255) NOT NULL,
> GROUP_ID VARCHAR(255) NOT NULL,
> SHARING_TYPE VARCHAR(255) NOT NULL,
> INHERITED_PARENT_ID VARCHAR(255),
> CREATED_TIME BIGINT NOT NULL,
> UPDATED_TIME BIGINT NOT NULL,
> PRIMARY KEY (PERMISSION_TYPE_ID, ENTITY_ID, GROUP_ID, INHERITED_PARENT_ID),
> FOREIGN KEY (PERMISSION_TYPE_ID) REFERENCES
> PERMISSION_TYPE(PERMISSION_TYPE_ID) ON DELETE CASCADE ON UPDATE CASCADE,
> FOREIGN KEY (INHERITED_PARENT_ID) REFERENCES ENTITY(ENTITY_ID) ON DELETE
> CASCADE ON UPDATE CASCADE,
> FOREIGN KEY (GROUP_ID) REFERENCES USER_GROUP(GROUP_ID) ON DELETE CASCADE ON
> UPDATE CASCADE
> );
> {code}
> This key is fine in the dev database on gw62. I think the reason it fails
> for me is that my databases have a default encoding of UTF-8. On gw62 the
> encoding is latin1_swedish_ci.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2269) The gateway admin cannot get access to the gateway even with 'admin' role
[ https://issues.apache.org/jira/browse/AIRAVATA-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2269. --- Resolution: Fixed > The gateway admin cannot get access to the gateway even with 'admin' role > - > > Key: AIRAVATA-2269 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2269 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.scigap.org > http://test.scigap.org/ >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17 > > > This is the PGA we set up after we created the tenant using 'Gateway Request' > feature in dev.scigap.org -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1885) Cannot add data movement interface for a new storage resource as scigap admin. Page crashes in PGA
[ https://issues.apache.org/jira/browse/AIRAVATA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1885. --- Resolution: Fixed > Cannot add data movement interface for a new storage resource as scigap > admin. Page crashes in PGA > -- > > Key: AIRAVATA-1885 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1885 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://portal.scigap.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17 > > Attachments: Screen Shot 2015-12-17 at 3.21.35 PM.png > > > When tried to add SCP interface with SSH_Keys protocol page crashed with > error page [1] > And the interface is not added as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2285) New users have no authorization to create projects, experiments!
[ https://issues.apache.org/jira/browse/AIRAVATA-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2285. --- Resolution: Fixed > New users have no authorization to create projects, experiments! > > > Key: AIRAVATA-2285 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2285 > Project: Airavata > Issue Type: Bug > Components: Airavata System, PGA PHP Web Gateway > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > New user tried to log in and see 'Unable to Connect to the Airavata Server > Instance!' > Once refreshed the message goes away. > Default project does not exists and also cannot create projects, experiments > Gives the message 'User is not authenticated or authorized.' > Please check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1830) Default Project is not getting created at user account creation
[ https://issues.apache.org/jira/browse/AIRAVATA-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1830. --- Resolution: Fixed > Default Project is not getting created at user account creation > --- > > Key: AIRAVATA-1830 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1830 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.testdrive.airavata.org/portal/master/public/ >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.16 > > > When a new user account is created in the PGA the default project did not get > created. When user tries to create an experiment it says that a project is > required. > In Project Browse there are no projects available as well -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2243) When experiments are retrieved for a given time period the time indicated in the heading is incorrect
[ https://issues.apache.org/jira/browse/AIRAVATA-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2243. --- Resolution: Fixed > When experiments are retrieved for a given time period the time indicated in > the heading is incorrect > - > > Key: AIRAVATA-2243 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2243 > Project: Airavata > Issue Type: Bug > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Attachments: Screen Shot 2016-11-30 at 2.15.21 PM.png > > > In experiment statistics searched for experiments between 11/22/2016 2:15 PM > and 11/30/2016 2:15 PM > When experiments are listed the heading indicates as > Experiment Statistics from 11/22/2016 07:15 PM to 11/30/2016 07:15 PM -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AIRAVATA-2064) In ultrascan production PGA cannot view outputs. Getting the attached error
[ https://issues.apache.org/jira/browse/AIRAVATA-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala reassigned AIRAVATA-2064: - Assignee: Supun Chathuranga Nakandala (was: Eroma) > In ultrascan production PGA cannot view outputs. Getting the attached error > --- > > Key: AIRAVATA-2064 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2064 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Attachments: Screen Shot 2016-08-24 at 1.12.26 PM.png > > > In production ultrascan PGA (https://ultrascan.scigap.org) getting error 'The > file > "/var/www/portals/gateway-user-data/ultrascan/Ero2016/Aug_24_2016/SLM2_US_Stampede_08_24_13_09_401472058589/Ultrascan.stderr" > does not exist' when tried to view the outputs. > The actual data folder does not contain the output file and it could be the > reason for the exception. But it should be handled gracefully. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2276) SQL escaping error in sharing registry: An error occurred while parsing the query filter
[
https://issues.apache.org/jira/browse/AIRAVATA-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Chathuranga Nakandala resolved AIRAVATA-2276.
---
Resolution: Fixed
> SQL escaping error in sharing registry: An error occurred while parsing the
> query filter
>
>
> Key: AIRAVATA-2276
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2276
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> I get the following error when I try to create an experiment with name
> {{~!@#$%^&*()_+?><,./;'}}.
> {noformat}
> 2016-12-14 11:08:55 [pool-7-thread-49] ERROR
> o.a.a.a.s.h.AiravataServerHandler - Error in sharing res
> ource with users. Resource ID :
> ~!@#$%^&*()_+?><,_/;'":_dad1b5f5-025f-452d-9bf0-712277ca36e7 Resource
> Type : EXPERIMENT
> org.apache.openjpa.persistence.ArgumentException: An error occurred while
> parsing the query filter 'S
> ELECT p from EntityEntity as p WHERE p.parentEntityId =
> '~!@#$%^&*()_+?><,_/;'":_dad1b5f5-025f-452d-9bf0-712277ca36e7' ORDER BY
> p.originalEntityCreationTime DESC'. Error message:
> org.apache.openjpa.kernel.jpql.TokenMgrError: Lexical error at line 1, column
> 163. Encountered: after : "\":_dad1b5f5-025f-452d-9bf0-712277ca36e7\'
> ORDER BY p.originalEntityCreationTime DESC"
> at
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.parse(JPQLExpressionBuilder.java:2405)
> at
> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.(JPQLExpressionBuilder.java:2388)
> at org.apache.openjpa.kernel.jpql.JPQLParser.parse(JPQLParser.java:49)
> at
> org.apache.openjpa.kernel.ExpressionStoreQuery.newCompilation(ExpressionStoreQuery.java:154)
> at
> org.apache.openjpa.kernel.QueryImpl.newCompilation(QueryImpl.java:672)
> at
> org.apache.openjpa.kernel.QueryImpl.compilationFromCache(QueryImpl.java:654)
> at
> org.apache.openjpa.kernel.QueryImpl.compileForCompilation(QueryImpl.java:620)
> at
> org.apache.openjpa.kernel.QueryImpl.compileForExecutor(QueryImpl.java:682)
> at org.apache.openjpa.kernel.QueryImpl.compile(QueryImpl.java:589)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:997)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:979)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:102)
> at
> org.apache.airavata.sharing.registry.db.repositories.AbstractRepository.lambda$select$3(AbstractRepository.java:106)
> at
> org.apache.airavata.sharing.registry.db.utils.JPAUtils.execute(JPAUtils.java:108)
> at
> org.apache.airavata.sharing.registry.db.repositories.AbstractRepository.select(AbstractRepository.java:106)
> at
> org.apache.airavata.sharing.registry.db.repositories.EntityRepository.getChildEntities(EntityRepository.java:48)
> at
> org.apache.airavata.sharing.registry.server.SharingRegistryServerHandler.shareEntity(SharingRegistryServerHandler.java:780)
> at
> org.apache.airavata.sharing.registry.server.SharingRegistryServerHandler.shareEntityWithUsers(SharingRegistryServerHandler.java:735)
> at
> org.apache.airavata.api.server.handler.AiravataServerHandler.shareResourceWithUsers(AiravataServerHandler.java:3917)
> at
> org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$354caf4d.CGLIB$shareResourceWithUsers$156()
> at
> org.apache.airavata.api.server.handler.AiravataServerHandler$$EnhancerByGuice$$354caf4d$$FastClassByGuice$$5912d722.invoke()
> at
> com.google.inject.internal.cglib.proxy.$MethodProxy.invokeSuper(MethodProxy.java:228)
> at
> com.google.inject.internal.InterceptorStackCallback$InterceptedMethodInvocation.proceed(InterceptorStackCallback.java:75)
> at
> org.apache.airavata.api.server.security.interceptor.SecurityInterceptor.invoke(SecurityInterceptor.java:57)
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2247) 'TSocket read 0 bytes' error when PGA calls getAllNotifications
[
https://issues.apache.org/jira/browse/AIRAVATA-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15743165#comment-15743165
]
Supun Chathuranga Nakandala commented on AIRAVATA-2247:
---
>From my initial check, I think this is coming because of the iterative user
>profile information retrieval from IS.
> 'TSocket read 0 bytes' error when PGA calls getAllNotifications
> ---
>
> Key: AIRAVATA-2247
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2247
> Project: Airavata
> Issue Type: Bug
> Components: Airavata API, PGA PHP Web Gateway
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> Getting the following error intermittently in PGA
> {noformat}
> [2016-12-01 16:40:05] production.ERROR: exception
> 'Thrift\Exception\TTransportException' with message
> 'TSocket read 0 bytes' in
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Transport/TSocket.php:26
> 9
> Stack trace:
> #0
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Transport/TTransport.php(74):
> Thrift\Transport\T
> Socket->read(4)
> #1
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Protocol/TBinaryProtocol.php(305):
> Thrift\Transp
> ort\TTransport->readAll(4)
> #2
> /var/www/portals/dev-seagrid/app/libraries/Thrift/Protocol/TBinaryProtocol.php(197):
> Thrift\Protoc
> ol\TBinaryProtocol->readI32(NULL)
> #3
> /var/www/portals/dev-seagrid/app/libraries/Airavata/API/Airavata.php(4960):
> Thrift\Protocol\TBinar
> yProtocol->readMessageBegin(NULL, 0, 0)
> #4
> /var/www/portals/dev-seagrid/app/libraries/Airavata/API/Airavata.php(4928):
> Airavata\API\AiravataC
> lient->recv_getAllNotifications()
> #5
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(21
> 1):
> Airavata\API\AiravataClient->getAllNotifications(Object(Airavata\Model\Security\AuthzToken),
> 'sea
> grid')
> #6 /var/www/portals/dev-seagrid/app/libraries/CommonUtilities.php(368):
> Illuminate\Support\Facades\Fa
> cade::__callStatic('getAllNotificat...', Array)
> #7 /var/www/portals/dev-seagrid/app/libraries/CommonUtilities.php(368):
> Airavata\Facades\Airavata::ge
> tAllNotifications(Object(Airavata\Model\Security\AuthzToken), 'seagrid')
> #8 /var/www/portals/dev-seagrid/app/libraries/CommonUtilities.php(214):
> CommonUtilities::get_all_noti
> ces()
> #9
> /var/www/portals/dev-seagrid/app/storage/views/5300885e7f238cf07a10aa6eceb271f8(37):
> CommonUtiliti
> es::create_nav_bar()
> #10
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php(3
> 7): include('/var/www/portal...')
> #11
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.
> php(57):
> Illuminate\View\Engines\PhpEngine->evaluatePath('/var/www/portal...', Array)
> #12
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(140):
> Illumina
> te\View\Engines\CompilerEngine->get('/var/www/portal...', Array)
> #13
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(109):
> Illumina
> te\View\View->getContents()
> #14
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(78):
> Illuminat
> e\View\View->renderContents()
> #15
> /var/www/portals/dev-seagrid/app/storage/views/d7a45c81bb507afc6ab5ba9806a3833d(60):
> Illuminate\V
> iew\View->render()
> #16
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php(3
> 7): include('/var/www/portal...')
> #17
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.
> php(57):
> Illuminate\View\Engines\PhpEngine->evaluatePath('/var/www/portal...', Array)
> #18
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(140):
> Illumina
> te\View\Engines\CompilerEngine->get('/var/www/portal...', Array)
> #19
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(109):
> Illumina
> te\View\View->getContents()
> #20
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/View/View.php(78):
> Illuminat
> e\View\View->renderContents()
> #21
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Http/Response.php(43):
> Illum
> inate\View\View->render()
> #22
> /var/www/portals/dev-seagrid/vendor/symfony/http-foundation/Response.php(202):
> Illuminate\Http\Re
> sponse->setContent(Object(Illuminate\View\View))
> #23
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Routing/Router.php(1501):
> Sy
> mfony\Component\HttpFoundation\Response->__construct(Object(Illuminate\View\View))
> #24
> /var/www/portals/dev-seagrid/vendor/laravel/framework/src/Illuminate/Routing/Router.php(1036):
[jira] [Resolved] (AIRAVATA-1940) When Unicore experiments are cloned US3INPUTTARG and UserDN are not cloned
[ https://issues.apache.org/jira/browse/AIRAVATA-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1940. --- Resolution: Fixed > When Unicore experiments are cloned US3INPUTTARG and UserDN are not cloned > -- > > Key: AIRAVATA-1940 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1940 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.ultrascan.scigap.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2104) Indicate mandatory fields in Create experiment UI in SEAGrid desktop application
[ https://issues.apache.org/jira/browse/AIRAVATA-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2104. --- Resolution: Fixed > Indicate mandatory fields in Create experiment UI in SEAGrid desktop > application > > > Key: AIRAVATA-2104 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2104 > Project: Airavata > Issue Type: Bug >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Similar to experiment creation page on PGA web interface indicate mandatory > fields in Desktop application as well. > Currently the validations are fired when the user tries to save or launch the > experiment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2253) Modifications or new email added for notification are not saved in Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2253. --- Resolution: Fixed > Modifications or new email added for notification are not saved in Experiment > - > > Key: AIRAVATA-2253 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2253 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Modification in edit mode or clone mode for notification email in experiment > is not getting saved/updated. Even though changed and updated the > modifications are not there. > Also if added a another new email or remove the existing in edit or clone > mode still does not get updated. Initially added notification email will > remain. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2258) Implement the notifications display in the SEAGrid Rich Client
[ https://issues.apache.org/jira/browse/AIRAVATA-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2258. --- Resolution: Fixed > Implement the notifications display in the SEAGrid Rich Client > -- > > Key: AIRAVATA-2258 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2258 > Project: Airavata > Issue Type: Improvement >Reporter: Sudhakar Pamidighantam >Assignee: Supun Chathuranga Nakandala >Priority: Minor > > The SEAGrid gateway notifications should be available in the rich client. The > latest one should be displayed in the opening page and others should be > discoverable. Login should not be required ( if possible) to read notices. > These are generic gateway wide information. > If possible we should read the maintenance posts from XSEDE/IU and post them > SciGaP wide and repost them for every gateway hosted (or those that use the > resource). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2254) New gateway user cannot create experiments in SEAGrid production
[ https://issues.apache.org/jira/browse/AIRAVATA-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2254. --- Resolution: Fixed > New gateway user cannot create experiments in SEAGrid production > > > Key: AIRAVATA-2254 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2254 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > New user with gateway-user role cannot create experiments using the web > portal. Getting the error mkdir(): Permission denied > Same user was able to create experiments from seagrid desktop application but > then again the output files are not listed for COMPLETED experiment. > in gfac log has error [1] > 2016-12-02 17:14:04,017 [pool-11-thread-209] ERROR > org.apache.airavata.gfac.impl.SSHUtils - Error Reading input Stream > 2016-12-02 17:14:04,017 [pool-11-thread-209] ERROR > org.apache.airavata.gfac.impl.SSHUtils - Error Reading input Stream > java.lang.Exception: Error Reading input Stream > at > org.apache.airavata.gfac.impl.SSHUtils.scpThirdParty(SSHUtils.java:385) > at > org.apache.airavata.gfac.impl.HPCRemoteCluster.scpThirdParty(HPCRemoteCluster.java:178) > at > org.apache.airavata.gfac.impl.task.ArchiveTask.execute(ArchiveTask.java:139) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.executeTask(GFacEngineImpl.java:771) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.outputDataStaging(GFacEngineImpl.java:723) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.executeTaskListFrom(GFacEngineImpl.java:327) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.continueProcess(GFacEngineImpl.java:682) > at > org.apache.airavata.gfac.impl.GFacWorker.continueTaskExecution(GFacWorker.java:197) > at org.apache.airavata.gfac.impl.GFacWorker.run(GFacWorker.java:97) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > 2016-12-02 17:14:04,018 [pool-11-thread-209] ERROR > org.apache.airavata.gfac.impl.HPCRemoteCluster - Retry count 3 exceeded for > transferring > from:/scratch/00421/ccguser/seagrid-workdirs/PROCESS_264d019e-57ce-4eef-a9cd-157737a30777/archive.tar > To: > /var/www/portals/gateway-user-data/seagrid/ProdSeagrid1/DefaultProject/AutoDock1.1480716701430/archive.tar > com.jcraft.jsch.JSchException: Error Reading input Stream > at > org.apache.airavata.gfac.impl.SSHUtils.scpThirdParty(SSHUtils.java:404) > at > org.apache.airavata.gfac.impl.HPCRemoteCluster.scpThirdParty(HPCRemoteCluster.java:178) > at > org.apache.airavata.gfac.impl.task.ArchiveTask.execute(ArchiveTask.java:139) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.executeTask(GFacEngineImpl.java:771) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.outputDataStaging(GFacEngineImpl.java:723) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.executeTaskListFrom(GFacEngineImpl.java:327) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.continueProcess(GFacEngineImpl.java:682) > at > org.apache.airavata.gfac.impl.GFacWorker.continueTaskExecution(GFacWorker.java:197) > at org.apache.airavata.gfac.impl.GFacWorker.run(GFacWorker.java:97) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > 2016-12-02 17:14:04,019 [pool-11-thread-209] ERROR > org.apache.airavata.gfac.impl.task.ArchiveTask - Error! Archive task failed > org.apache.airavata.gfac.core.SSHApiException: Failed scp > file:/scratch/00421/ccguser/seagrid-workdirs/PROCESS_264d019e-57ce-4eef-a9cd-157737a30777/archive.tar > to remote file > /var/www/portals/gateway-user-data/seagrid/ProdSeagrid1/DefaultProject/AutoDock1.1480716701430/archive.tar > at > org.apache.airavata.gfac.impl.HPCRemoteCluster.scpThirdParty(HPCRemoteCluster.java:191) > at > org.apache.airavata.gfac.impl.task.ArchiveTask.execute(ArchiveTask.java:139) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.executeTask(GFacEngineImpl.java:771) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.outputDataStaging(GFacEngineImpl.java:723) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.executeTaskListFrom(GFacEngineImpl.java:327) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2243) When experiments are retrieved for a given time period the time indicated in the heading is incorrect
[ https://issues.apache.org/jira/browse/AIRAVATA-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2243. --- Resolution: Fixed > When experiments are retrieved for a given time period the time indicated in > the heading is incorrect > - > > Key: AIRAVATA-2243 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2243 > Project: Airavata > Issue Type: Bug > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Attachments: Screen Shot 2016-11-30 at 2.15.21 PM.png > > > In experiment statistics searched for experiments between 11/22/2016 2:15 PM > and 11/30/2016 2:15 PM > When experiments are listed the heading indicates as > Experiment Statistics from 11/22/2016 07:15 PM to 11/30/2016 07:15 PM -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-2256) Implement 'Notices' into SEAGrid desktop client
[ https://issues.apache.org/jira/browse/AIRAVATA-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala updated AIRAVATA-2256: -- Description: Currently 'Notices' are only available in web client. This should be incorporated into desktop client for users to view the Notices. (was: Currently 'Notices' are only available in web client. This should be incorporated in to desktop client for users to view the Notices.) > Implement 'Notices' into SEAGrid desktop client > --- > > Key: AIRAVATA-2256 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2256 > Project: Airavata > Issue Type: New Feature > Components: Airavata System, PGA PHP Web Gateway > Environment: SEAGrid desktop client >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Currently 'Notices' are only available in web client. This should be > incorporated into desktop client for users to view the Notices. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2243) When experiments are retrieved for a given time period the time indicated in the heading is incorrect
[ https://issues.apache.org/jira/browse/AIRAVATA-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2243. --- Resolution: Fixed > When experiments are retrieved for a given time period the time indicated in > the heading is incorrect > - > > Key: AIRAVATA-2243 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2243 > Project: Airavata > Issue Type: Bug > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Attachments: Screen Shot 2016-11-30 at 2.15.21 PM.png > > > In experiment statistics searched for experiments between 11/22/2016 2:15 PM > and 11/30/2016 2:15 PM > When experiments are listed the heading indicates as > Experiment Statistics from 11/22/2016 07:15 PM to 11/30/2016 07:15 PM -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2249) Add information to new gateway requesting owners in gateway request page.
[ https://issues.apache.org/jira/browse/AIRAVATA-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2249. --- Resolution: Fixed > Add information to new gateway requesting owners in gateway request page. > - > > Key: AIRAVATA-2249 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2249 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway > Environment: dev.scigap.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Can we add some text explaining what he needs to do and what he would need to > expect? > Something like. > " You are in this page to create request for a new Gateway. Please click > 'Request a New Gateway' button and proceed. > Once your request is submitted a SciGaP admin will process the request and if > needed will contact you through the process." -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2187) WSO2 IS account confirmation link is only valid once! Cannot use the link afterwards.
[ https://issues.apache.org/jira/browse/AIRAVATA-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15715444#comment-15715444 ] Supun Chathuranga Nakandala commented on AIRAVATA-2187: --- In order to fix this, we need to add a more elaborative message to the failure message. > WSO2 IS account confirmation link is only valid once! Cannot use the link > afterwards. > - > > Key: AIRAVATA-2187 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2187 > Project: Airavata > Issue Type: Sub-task > Components: PGA PHP Web Gateway > Environment: All environments has this >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > The link user gets via email for account confirmation is only a one time use > link. > Once the user clicks on it he has to go through the account confirmation till > the end. > If for some reason user clicks on the link again, gets message 'Account > confirmation failed!'. Link is no use if not used first time. > This is not user friendly at all from user point. Users should be able to use > the link until the account confirmation is completed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2105) Cannot clone an experiment with optional files in SEAGrid desktop client
[ https://issues.apache.org/jira/browse/AIRAVATA-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2105. --- Resolution: Fixed > Cannot clone an experiment with optional files in SEAGrid desktop client > > > Key: AIRAVATA-2105 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2105 > Project: Airavata > Issue Type: Bug >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Attachments: Screen Shot 2016-09-16 at 1.52.26 PM.png > > > Steps > 1. Selected an experiment COMPLETED successfully. > 2. Click 'Clone' > 3. Gives the attached error with error message [1] > 4. New cloned experiment is not created in the backend. Both original > experiment and the cloned is from the same date. > [1] > 2: java.nio.file.NoSuchFileException: > /var/www/portals/gateway-user-data/seagrid/Eroma2016/Vina_3-1474048290073/9e0912b2-2f7c-47de-87b2-7bcfffe66998 > at com.jcraft.jsch.ChannelSftp.throwStatusError(ChannelSftp.java:2846) > at com.jcraft.jsch.ChannelSftp.symlink(ChannelSftp.java:1817) > at > org.seagrid.desktop.connectors.storage.StorageManager.createSymLink(StorageManager.java:84) > at > org.seagrid.desktop.ui.experiment.summary.controller.ExperimentSummaryController.lambda$initialize$18(ExperimentSummaryController.java:200) > at > com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(CompositeEventHandler.java:86) > at > com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:238) > at > com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:191) > at > com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(CompositeEventDispatcher.java:59) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:58) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at com.sun.javafx.event.EventUtil.fireEventImpl(EventUtil.java:74) > at com.sun.javafx.event.EventUtil.fireEvent(EventUtil.java:49) > at javafx.event.Event.fireEvent(Event.java:198) > at javafx.scene.Node.fireEvent(Node.java:8411) > at javafx.scene.control.Button.fire(Button.java:185) > at > com.sun.javafx.scene.control.behavior.ButtonBehavior.mouseReleased(ButtonBehavior.java:182) > at > com.sun.javafx.scene.control.skin.BehaviorSkinBase$1.handle(BehaviorSkinBase.java:96) > at > com.sun.javafx.scene.control.skin.BehaviorSkinBase$1.handle(BehaviorSkinBase.java:89) > at > com.sun.javafx.event.CompositeEventHandler$NormalEventHandlerRecord.handleBubblingEvent(CompositeEventHandler.java:218) > at > com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(CompositeEventHandler.java:80) > at > com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:238) > at > com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:191) > at > com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(CompositeEventDispatcher.java:59) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:58) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at >
[jira] [Resolved] (AIRAVATA-2206) When the SEAGrid rich client times out have the login page to appear for logins
[ https://issues.apache.org/jira/browse/AIRAVATA-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2206. --- Resolution: Fixed > When the SEAGrid rich client times out have the login page to appear for > logins > --- > > Key: AIRAVATA-2206 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2206 > Project: Airavata > Issue Type: Bug > Environment: SEAGrid Desktop Client >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > When SEAGrid rich client times out currently the same page will remain where > users cannot do anything but to close and open again. > Instead have the login page prompted at time out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1885) Cannot add data movement interface for a new storage resource as scigap admin. Page crashes in PGA
[ https://issues.apache.org/jira/browse/AIRAVATA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1885. --- Resolution: Fixed > Cannot add data movement interface for a new storage resource as scigap > admin. Page crashes in PGA > -- > > Key: AIRAVATA-1885 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1885 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://portal.scigap.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > Attachments: Screen Shot 2015-12-17 at 3.21.35 PM.png > > > When tried to add SCP interface with SSH_Keys protocol page crashed with > error page [1] > And the interface is not added as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1361) Search for experiments created, launched within a given time frame
[ https://issues.apache.org/jira/browse/AIRAVATA-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1361. --- Resolution: Fixed > Search for experiments created, launched within a given time frame > -- > > Key: AIRAVATA-1361 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1361 > Project: Airavata > Issue Type: Sub-task >Affects Versions: 0.13 >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > > Search for experiments created, launched within a given time frame > Search for experiments created between 1.00 am - 1.00 pm > Search for experiments in LAUNCHED state for last 4 hours -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-2206) When the SEAGrid rich client times out have the login page to appear for logins
[ https://issues.apache.org/jira/browse/AIRAVATA-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala updated AIRAVATA-2206: -- Environment: SEAGrid Desktop Client (was: seagrid.org) > When the SEAGrid rich client times out have the login page to appear for > logins > --- > > Key: AIRAVATA-2206 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2206 > Project: Airavata > Issue Type: Bug > Environment: SEAGrid Desktop Client >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > When SEAGrid rich client times out currently the same page will remain where > users cannot do anything but to close and open again. > Instead have the login page prompted at time out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1868) When modified and saved the changes are not applied to application interface
[ https://issues.apache.org/jira/browse/AIRAVATA-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1868. --- Resolution: Fixed > When modified and saved the changes are not applied to application interface > > > Key: AIRAVATA-1868 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1868 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://seagrid.org/portal/public/app/interface >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > > Updated existing application interface. > changes the 'Data is staged?' and clicked update. > The changes are not updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-1841) Display a proper message in PGA when Airavata server is down; currently page crashes with an error
[ https://issues.apache.org/jira/browse/AIRAVATA-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala updated AIRAVATA-1841: -- Priority: Minor (was: Major) > Display a proper message in PGA when Airavata server is down; currently page > crashes with an error > --- > > Key: AIRAVATA-1841 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1841 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.testdrive.airavata.org/portal/master/public >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala >Priority: Minor > Fix For: 0.17-SNAPSHOT > > Attachments: Screen Shot 2015-09-28 at 4.06.17 PM.png > > > When airaveata server goes down while in middle of creating an experiment in > PGA this error page suddenly flashes. > As happens if user opens create experiment page while airaveata server is > down. > Instead of the currently displayed error page please provide user wit ha > meaningful message to say that servers are down and we are sorry for > inconvenience caused. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2185) Add OWNER ResourcePermissionType to sharing API
[
https://issues.apache.org/jira/browse/AIRAVATA-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Chathuranga Nakandala resolved AIRAVATA-2185.
---
Resolution: Fixed
> Add OWNER ResourcePermissionType to sharing API
> ---
>
> Key: AIRAVATA-2185
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2185
> Project: Airavata
> Issue Type: New Feature
> Components: Airavata API
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> I [discussed this earlier with
> Supun|https://issues.apache.org/jira/browse/AIRAVATA-2170?focusedCommentId=15588665=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15588665]
> {quote}
> I talked with Supun and he is going to add the OWNER ResourcePermissionType
> to the sharing API. Then I'll be able to call getAllAccessibleUsers with the
> OWNER permission type.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1957) When experiments are cloned there are two data directories getting created in the Storage
[ https://issues.apache.org/jira/browse/AIRAVATA-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1957. --- Resolution: Fixed > When experiments are cloned there are two data directories getting created in > the Storage > - > > Key: AIRAVATA-1957 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1957 > Project: Airavata > Issue Type: Bug > Components: Airavata System, PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > > Cloned an existing experiment. Instead of single data directory getting > created there are two directories with few second apart. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2038) Email address entered for job notifications are not displayed in Experiment Summary or in Edit Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2038. --- Resolution: Fixed > Email address entered for job notifications are not displayed in Experiment > Summary or in Edit Experiment > -- > > Key: AIRAVATA-2038 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2038 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: PGA >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala >Priority: Minor > > When the email address is entered it is not listed in Experiment Summary page > or in Edit Experiment page. > Similarly it is not displayed in clone experiment page as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2224) Contact email given for gateway requests page need to change
[ https://issues.apache.org/jira/browse/AIRAVATA-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2224. --- Resolution: Fixed > Contact email given for gateway requests page need to change > > > Key: AIRAVATA-2224 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2224 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.scigap.org/admin/dashboard >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Please change the existing email to h...@scigap.org. Currently existing > cont...@scigap.org which is not the right one. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AIRAVATA-2038) Email address entered for job notifications are not displayed in Experiment Summary or in Edit Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala reopened AIRAVATA-2038: --- > Email address entered for job notifications are not displayed in Experiment > Summary or in Edit Experiment > -- > > Key: AIRAVATA-2038 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2038 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: PGA >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala >Priority: Minor > > When the email address is entered it is not listed in Experiment Summary page > or in Edit Experiment page. > Similarly it is not displayed in clone experiment page as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2038) Email address entered for job notifications are not displayed in Experiment Summary or in Edit Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2038. --- Resolution: Fixed > Email address entered for job notifications are not displayed in Experiment > Summary or in Edit Experiment > -- > > Key: AIRAVATA-2038 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2038 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: PGA >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala >Priority: Minor > > When the email address is entered it is not listed in Experiment Summary page > or in Edit Experiment page. > Similarly it is not displayed in clone experiment page as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2240) When project summary and experiment summary of an experiment refreshed at the same time exception thrown
[ https://issues.apache.org/jira/browse/AIRAVATA-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2240. --- Resolution: Fixed > When project summary and experiment summary of an experiment refreshed at the > same time exception thrown > > > Key: AIRAVATA-2240 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2240 > Project: Airavata > Issue Type: Bug > Components: Airavata System, PGA PHP Web Gateway > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Attachments: Screen Shot 2016-11-21 at 4.26.17 PM.png > > > An experiment summary and Project summary is refreshed at the same time. > Project summary page crashes with the attached exception. > Refreshed experiment belongs to the Project that is been refreshed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2237) In the gateway provider view of gateway requests change the 'Comments' heading to 'SciGaP Comments'
[ https://issues.apache.org/jira/browse/AIRAVATA-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2237. --- Resolution: Fixed > In the gateway provider view of gateway requests change the 'Comments' > heading to 'SciGaP Comments' > --- > > Key: AIRAVATA-2237 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2237 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: dev.scigap.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala >Priority: Trivial > > Since the comments are from scigap admins the change of heading will make it > more meaningful to the users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-2236) In SciGaP portal cannot request a gateway unless the user is explicitly given admin role
[ https://issues.apache.org/jira/browse/AIRAVATA-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala updated AIRAVATA-2236: -- Assignee: Eroma (was: Supun Chathuranga Nakandala) > In SciGaP portal cannot request a gateway unless the user is explicitly given > admin role > > > Key: AIRAVATA-2236 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2236 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: dev.scigap.org >Reporter: Eroma >Assignee: Eroma > > In dev.scigap.org when a new user creates an account and logs in to confirm, > not directed to 'Request a New Gateway' page. Instead scigap admin needs to > add additionally admin role. Then only the new user would see 'Request a New > Gateway' > Earlier this was not the case. Soon after using the confirmation link to > login user can create a gateway request. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2080) When tried to view the project summary gives error exception in dev seagrid portal
[ https://issues.apache.org/jira/browse/AIRAVATA-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2080. --- Resolution: Fixed > When tried to view the project summary gives error exception in dev seagrid > portal > -- > > Key: AIRAVATA-2080 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2080 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Attachments: Screen Shot 2016-09-02 at 2.26.29 PM.png, Screen Shot > 2016-10-05 at 3.02.50 PM.png > > > error exception > Error while retrieving the job statuses. More info : Internal error > processing getJobStatuses (View: > /var/www/portals/dev-seagrid/app/views/project/summary.blade.php) > when tried to view project summary. This project was created today and it has > experiment which has no job status in it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2015) When a gateway user shares a project or an experiment have a notification sent
[ https://issues.apache.org/jira/browse/AIRAVATA-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657848#comment-15657848 ] Supun Chathuranga Nakandala commented on AIRAVATA-2015: --- [~eroma_a] Can't we handle at the PGA ? > When a gateway user shares a project or an experiment have a notification sent > -- > > Key: AIRAVATA-2015 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2015 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala >Priority: Minor > > When a project or experiment shared, unshared please notify the other person. > It would be ideal if we also could notify the owner when any changes take > place in project and experiment by shared users as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-2064) In ultrascan production PGA cannot view outputs. Getting the attached error
[ https://issues.apache.org/jira/browse/AIRAVATA-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala updated AIRAVATA-2064: -- Assignee: Eroma (was: Supun Chathuranga Nakandala) > In ultrascan production PGA cannot view outputs. Getting the attached error > --- > > Key: AIRAVATA-2064 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2064 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 >Reporter: Eroma >Assignee: Eroma > Attachments: Screen Shot 2016-08-24 at 1.12.26 PM.png > > > In production ultrascan PGA (https://ultrascan.scigap.org) getting error 'The > file > "/var/www/portals/gateway-user-data/ultrascan/Ero2016/Aug_24_2016/SLM2_US_Stampede_08_24_13_09_401472058589/Ultrascan.stderr" > does not exist' when tried to view the outputs. > The actual data folder does not contain the output file and it could be the > reason for the exception. But it should be handled gracefully. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2120) Application deployments are merged together when tried to create a new deployment in same resource using same app module
[ https://issues.apache.org/jira/browse/AIRAVATA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2120. --- Resolution: Won't Fix > Application deployments are merged together when tried to create a new > deployment in same resource using same app module > > > Key: AIRAVATA-2120 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2120 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Single compute resource holding two separate deployments of the same > application module (2 separate application interfaces) results merge of the > old and the new deployment. > Updates the existing merging both pre job commands, etc. > Abaqus has two separate application interfaces using same module. When tried > to deploy the new deployment in Comet, PGA allowed me to create a new > deployment but when revisited there is only one merged deployment in Comet > instead of two separate ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2175) Prevent changing project owner
[ https://issues.apache.org/jira/browse/AIRAVATA-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2175. --- Resolution: Fixed > Prevent changing project owner > -- > > Key: AIRAVATA-2175 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2175 > Project: Airavata > Issue Type: Bug > Components: Airavata API >Reporter: Marcus Christie >Assignee: Supun Chathuranga Nakandala > > Currently Airavata.updateProject allows updating the owner of the project. > This was causing the owner of a shared project to change to whoever last > edited it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2206) When the SEAGrid rich client times out have the login page to appear for logins
[ https://issues.apache.org/jira/browse/AIRAVATA-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657582#comment-15657582 ] Supun Chathuranga Nakandala commented on AIRAVATA-2206: --- [~eroma_a] when this happen does it pops up an exception dialog > When the SEAGrid rich client times out have the login page to appear for > logins > --- > > Key: AIRAVATA-2206 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2206 > Project: Airavata > Issue Type: Bug > Environment: seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > When SEAGrid rich client times out currently the same page will remain where > users cannot do anything but to close and open again. > Instead have the login page prompted at time out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2185) Add OWNER ResourcePermissionType to sharing API
[
https://issues.apache.org/jira/browse/AIRAVATA-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Supun Chathuranga Nakandala resolved AIRAVATA-2185.
---
Resolution: Fixed
> Add OWNER ResourcePermissionType to sharing API
> ---
>
> Key: AIRAVATA-2185
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2185
> Project: Airavata
> Issue Type: New Feature
> Components: Airavata API
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> I [discussed this earlier with
> Supun|https://issues.apache.org/jira/browse/AIRAVATA-2170?focusedCommentId=15588665=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15588665]
> {quote}
> I talked with Supun and he is going to add the OWNER ResourcePermissionType
> to the sharing API. Then I'll be able to call getAllAccessibleUsers with the
> OWNER permission type.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (AIRAVATA-2041) Provide proper error message when searched non existing experiment ID in Experiment Statistics page
[ https://issues.apache.org/jira/browse/AIRAVATA-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala updated AIRAVATA-2041: -- Assignee: Eroma (was: Supun Chathuranga Nakandala) > Provide proper error message when searched non existing experiment ID in > Experiment Statistics page > --- > > Key: AIRAVATA-2041 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2041 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Reporter: Eroma >Assignee: Eroma > > When searched a non existing or wrong experiment ID > 1. New tab opens with message 'Exception: Internal error processing > getExperiment' > This should be replaced with proper PGA message meaningful to the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-2020) Do we need user role creation in gateway Admin Dashboard?
[ https://issues.apache.org/jira/browse/AIRAVATA-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala updated AIRAVATA-2020: -- Assignee: Eroma (was: Supun Chathuranga Nakandala) > Do we need user role creation in gateway Admin Dashboard? > - > > Key: AIRAVATA-2020 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2020 > Project: Airavata > Issue Type: Sub-task > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT >Reporter: Eroma >Assignee: Eroma > > Currently role creation exists from Admin Dashboard -->Roles > Creating this role and assigning the role does not mange user access or > privileges in the gateway. > Can we remove role creation? Any current gateway users using this feature > successfully? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2081) Error exception thrown when clicked on clone for an experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2081. --- Resolution: Fixed > Error exception thrown when clicked on clone for an experiment > -- > > Key: AIRAVATA-2081 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2081 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Attachments: Screen Shot 2016-09-02 at 2.34.51 PM.png, Screen Shot > 2016-10-05 at 3.13.58 PM.png > > > when clicked on clone gets the error > Undefined index: scheduling > but the new cloned experiment is actually created in the backend. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2185) Add OWNER ResourcePermissionType to sharing API
[
https://issues.apache.org/jira/browse/AIRAVATA-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15655065#comment-15655065
]
Supun Chathuranga Nakandala commented on AIRAVATA-2185:
---
@Marcus There will be one owner for an entity which can be found from the owner
field in the entity object. Is that what you want to find.
> Add OWNER ResourcePermissionType to sharing API
> ---
>
> Key: AIRAVATA-2185
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2185
> Project: Airavata
> Issue Type: New Feature
> Components: Airavata API
>Reporter: Marcus Christie
>Assignee: Supun Chathuranga Nakandala
>
> I [discussed this earlier with
> Supun|https://issues.apache.org/jira/browse/AIRAVATA-2170?focusedCommentId=15588665=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15588665]
> {quote}
> I talked with Supun and he is going to add the OWNER ResourcePermissionType
> to the sharing API. Then I'll be able to call getAllAccessibleUsers with the
> OWNER permission type.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2021) User shared only a single experiment; project also got shared with the new user
[ https://issues.apache.org/jira/browse/AIRAVATA-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2021. --- Resolution: Fixed > User shared only a single experiment; project also got shared with the new > user > --- > > Key: AIRAVATA-2021 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2021 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Steps; > 1. User A (gateway-user role) shared a single experiment with user B (admin > role) > 2. User B logs in > 3. In Project Browse it shows as Usr A shared the project as well > 4. Experiment also displayed in Experiment browse. > 5. When only a experiment is shared only the Experiment browse should > display. Should NOT share the whole project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2202) Experiment data not available in https://data.seagrid.org/
[ https://issues.apache.org/jira/browse/AIRAVATA-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2202. --- Resolution: Fixed > Experiment data not available in https://data.seagrid.org/ > -- > > Key: AIRAVATA-2202 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2202 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > 1. Created and launched an experiment. > 2. Once the job got completed and files are transferred to PGA side logged in > to https://data.seagrid.org/ > 3. When searched for the experiment using the name nothing is retrieved. > Seems like only some pervious data is existing in https://data.seagrid.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2220) When a brand new user with 'gateway-user' role logs in the default Project is missing.
[ https://issues.apache.org/jira/browse/AIRAVATA-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2220. --- Resolution: Fixed > When a brand new user with 'gateway-user' role logs in the default Project is > missing. > -- > > Key: AIRAVATA-2220 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2220 > Project: Airavata > Issue Type: Bug > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Attachments: Screen Shot 2016-11-10 at 2.56.22 PM.png > > > After assigning 'gateway-user' role when the user logs in to PGA for the > first time in Project browser no default project exists. > Displays message 'You have not created any projects yet, so no results will > be returned! Click here to create a new project.' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-2191) Experiment of User A got automatically shared with User B when User A shares another experiment with user C
[ https://issues.apache.org/jira/browse/AIRAVATA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala updated AIRAVATA-2191: -- Assignee: Eroma (was: Supun Chathuranga Nakandala) > Experiment of User A got automatically shared with User B when User A shares > another experiment with user C > --- > > Key: AIRAVATA-2191 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2191 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Eroma > Fix For: 0.17-SNAPSHOT > > Attachments: Screen Shot 2016-10-25 at 12.02.53 PM.png > > > 1. User A create Project A and shares it with User B > 2. User A creates an experiment under Project A but removes sharing with User > B > 3. User A creates another experiment and shares it with User C under the same > project A > 4. Upon sharing second experiment with User C, the first one now appears as a > shared experiment for User B. Even when it is not shared. > 5. When User B tries to view the experiment summary throws the attached > exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2191) Experiment of User A got automatically shared with User B when User A shares another experiment with user C
[ https://issues.apache.org/jira/browse/AIRAVATA-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654996#comment-15654996 ] Supun Chathuranga Nakandala commented on AIRAVATA-2191: --- If doing experiment level fine grained sharing first the project level sharing should be removed or should be shared with non-cascading. If project A is shared with User X with cascading permission we cannot say we want to remove permission of User X to a child in project A. If that needs to be done first the top level project permission should be removed. > Experiment of User A got automatically shared with User B when User A shares > another experiment with user C > --- > > Key: AIRAVATA-2191 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2191 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > Attachments: Screen Shot 2016-10-25 at 12.02.53 PM.png > > > 1. User A create Project A and shares it with User B > 2. User A creates an experiment under Project A but removes sharing with User > B > 3. User A creates another experiment and shares it with User C under the same > project A > 4. Upon sharing second experiment with User C, the first one now appears as a > shared experiment for User B. Even when it is not shared. > 5. When User B tries to view the experiment summary throws the attached > exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2192) user A shared a project which has two experiments with user B. Exception thrown, User B cannot view the experiment summary
[ https://issues.apache.org/jira/browse/AIRAVATA-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2192. --- Resolution: Fixed > user A shared a project which has two experiments with user B. Exception > thrown, User B cannot view the experiment summary > -- > > Key: AIRAVATA-2192 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2192 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > Attachments: Screen Shot 2016-10-25 at 2.07.39 PM.png > > > Steps > 1. User A creates experiments under a unshared project.Experiments are not > shared as well. > 2. When one experiment was in COMPLETED and other in EXECUTING User A shares > the project with User B > 3. User B can see the COMPLETED experiment shared with him but cannot view > the summary. Throws exception > 4. Other experiment which is in EXECUTING is not even displayed in Project > Summary. > When a project with experiments are shared with a user (Professor wants to > share all the research experiments for the last month), he should be able to > view all experiments inside the project and also the new ones created in the > project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (AIRAVATA-2217) Sharing service should prevent removing sharing of experiments from the project's owner
[ https://issues.apache.org/jira/browse/AIRAVATA-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala reopened AIRAVATA-2217: --- > Sharing service should prevent removing sharing of experiments from the > project's owner > --- > > Key: AIRAVATA-2217 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2217 > Project: Airavata > Issue Type: Bug >Reporter: Marcus Christie >Assignee: Supun Chathuranga Nakandala > > See the steps to reproduce in AIRAVATA-2195. The sharing service allows User > C to remove access to an experiment in a shared project that is owned by User > A. User C should not be able to remove access to the experiment from User A > since User A is the owner of the project in which the experiment exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2217) Sharing service should prevent removing sharing of experiments from the project's owner
[ https://issues.apache.org/jira/browse/AIRAVATA-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2217. --- Resolution: Fixed > Sharing service should prevent removing sharing of experiments from the > project's owner > --- > > Key: AIRAVATA-2217 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2217 > Project: Airavata > Issue Type: Bug >Reporter: Marcus Christie >Assignee: Supun Chathuranga Nakandala > > See the steps to reproduce in AIRAVATA-2195. The sharing service allows User > C to remove access to an experiment in a shared project that is owned by User > A. User C should not be able to remove access to the experiment from User A > since User A is the owner of the project in which the experiment exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2217) Sharing service should prevent removing sharing of experiments from the project's owner
[ https://issues.apache.org/jira/browse/AIRAVATA-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2217. --- Resolution: Fixed > Sharing service should prevent removing sharing of experiments from the > project's owner > --- > > Key: AIRAVATA-2217 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2217 > Project: Airavata > Issue Type: Bug >Reporter: Marcus Christie >Assignee: Supun Chathuranga Nakandala > > See the steps to reproduce in AIRAVATA-2195. The sharing service allows User > C to remove access to an experiment in a shared project that is owned by User > A. User C should not be able to remove access to the experiment from User A > since User A is the owner of the project in which the experiment exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AIRAVATA-1999) Exception thrown when updated the Default Project name and description
[ https://issues.apache.org/jira/browse/AIRAVATA-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala closed AIRAVATA-1999. - Resolution: Fixed > Exception thrown when updated the Default Project name and description > -- > > Key: AIRAVATA-1999 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1999 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > > Steps followed; > 1. Created a new user and given admin-read-only role > 2. Updated the Default Project by sharing the project with a user. > 3. The above user got added succsesfully. > 4. Tried to update Project name and description of the above shared Default > Project and got the exception 'Invalid argument supplied for foreach()' > 5. Added modifications to the name and description are also not saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1936) When a compute resource is deleted related other entries are not getting deleted from the database
[ https://issues.apache.org/jira/browse/AIRAVATA-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1936. --- Resolution: Won't Fix > When a compute resource is deleted related other entries are not getting > deleted from the database > -- > > Key: AIRAVATA-1936 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1936 > Project: Airavata > Issue Type: Bug > Components: Airavata API, PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.scigap.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > > When a compute resource is deleted related records re not getting deleted > from some of the related tables. > E.g.: > COMPUTE_RESOURCE_FILE_SYSTEM > DATA_MOVEMENT_INTERFACE > HOST_ALIAS > JOB_MANAGER_COMMAND > JOB_SUBMISSION_INTERFACE > PARALLELISM_COMMAND > RESOURCE_JOB_MANAGER > Seems like only COMPUTE_RESOURCE table record is deleted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1517) When there are no JobManager Commands, Empty records get created upon updating Job Submission Protocols
[ https://issues.apache.org/jira/browse/AIRAVATA-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1517. --- Resolution: Fixed > When there are no JobManager Commands, Empty records get created upon > updating Job Submission Protocols > --- > > Key: AIRAVATA-1517 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1517 > Project: Airavata > Issue Type: Bug > Components: Application Catalog > Environment: http://dev.test-drive.airavata.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala >Priority: Minor > Fix For: 0.17-SNAPSHOT > > > when adding Job Submission Protocols to Job submission interfaces, > Empty command records get created in the DB even when user does not enter any > commands. > This issue exists with both SSH and LOCAL protocols. > Others didn't test as they are not available for testing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2181) Cannot view the experiment outputs from PGA. Getting exception: The file "/var/www/portals/gateway-user-data/dev-seagrid/" does not exist
[ https://issues.apache.org/jira/browse/AIRAVATA-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2181. --- Resolution: Fixed This commit will fix this issue https://github.com/apache/airavata/commit/926a01a11f44acfbbab33d4a460771d0b85b057f > Cannot view the experiment outputs from PGA. Getting exception: The file > "/var/www/portals/gateway-user-data/dev-seagrid/" does not exist > - > > Key: AIRAVATA-2181 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2181 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Marcus Christie > Fix For: 0.17-SNAPSHOT > > > When tried to view inputs and outputs from experiment summary; > 1. Can successfully download the input file > 2. Cannot view the outputs. > 3. They exists in the specific data directory of the experiment in gw54 > machine. (Path: > var/www/portals/gateway-user-data/dev-seagrid/ProdE2016/October_21_2016/Clone_of_SLM2_Gaussian_Gordon1477061600) > Experiment ID: > Clone_of_SLM2-Gaussian-Gordon_e44417f0-de47-4baf-aceb-5bd7a6126fef -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2015) When a gateway user shares a project or an experiment have a notification sent
[ https://issues.apache.org/jira/browse/AIRAVATA-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2015. --- Resolution: Fixed > When a gateway user shares a project or an experiment have a notification sent > -- > > Key: AIRAVATA-2015 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2015 > Project: Airavata > Issue Type: Sub-task > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala >Priority: Minor > > When a project or experiment shared, unshared please notify the other person. > It would be ideal if we also could notify the owner when any changes take > place in project and experiment by shared users as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2006) Users should be able to share COMPLETED experiments as well.
[ https://issues.apache.org/jira/browse/AIRAVATA-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2006. --- Resolution: Fixed > Users should be able to share COMPLETED experiments as well. > > > Key: AIRAVATA-2006 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2006 > Project: Airavata > Issue Type: Sub-task > Components: Airavata System, PGA PHP Web Gateway >Affects Versions: 0.16 >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Currently sharing capability is added modified through 'create' and 'edit' > functions for both experiments and projects. > Although projects can be edited at any given time experiments cannot be > edited once they are launched. > PGA need to provide sharing even after experiment details are no longer > modifiable. (Experiments in status EXECUTING) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2021) User shared only a single experiment; project also got shared with the new user
[ https://issues.apache.org/jira/browse/AIRAVATA-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2021. --- Resolution: Fixed > User shared only a single experiment; project also got shared with the new > user > --- > > Key: AIRAVATA-2021 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2021 > Project: Airavata > Issue Type: Sub-task > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Steps; > 1. User A (gateway-user role) shared a single experiment with user B (admin > role) > 2. User B logs in > 3. In Project Browse it shows as Usr A shared the project as well > 4. Experiment also displayed in Experiment browse. > 5. When only a experiment is shared only the Experiment browse should > display. Should NOT share the whole project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2120) Application deployments are merged together when tried to create a new deployment in same resource using same app module
[ https://issues.apache.org/jira/browse/AIRAVATA-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530505#comment-15530505 ] Supun Chathuranga Nakandala commented on AIRAVATA-2120: --- In the current design and implementation each deployment should be unique given the module and interface. The way to do this will be to define different modules for different versions of application > Application deployments are merged together when tried to create a new > deployment in same resource using same app module > > > Key: AIRAVATA-2120 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2120 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Single compute resource holding two separate deployments of the same > application module (2 separate application interfaces) results merge of the > old and the new deployment. > Updates the existing merging both pre job commands, etc. > Abaqus has two separate application interfaces using same module. When tried > to deploy the new deployment in Comet, PGA allowed me to create a new > deployment but when revisited there is only one merged deployment in Comet > instead of two separate ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1997) Gateway ID saved as project name. Default Project not existing for new users.
[ https://issues.apache.org/jira/browse/AIRAVATA-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1997. --- Resolution: Fixed > Gateway ID saved as project name. Default Project not existing for new users. > - > > Key: AIRAVATA-1997 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1997 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > > When a new use with gateway-user role logs in > 1. Default Project does not exists > 2. When a new project is created project name is not the name given by user > but the gateway ID -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1971) 'Launch Selected' and 'Delete Selected' buttons are not working in SEAGrid desktop client
[ https://issues.apache.org/jira/browse/AIRAVATA-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1971. --- Resolution: Fixed > 'Launch Selected' and 'Delete Selected' buttons are not working in SEAGrid > desktop client > - > > Key: AIRAVATA-1971 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1971 > Project: Airavata > Issue Type: Bug >Affects Versions: 0.16 > Environment: SEAGrid Desktop Client >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.17-SNAPSHOT > > > Selected multiple experiments and tried to launch them and also tried > deleting but both did not work. > Please check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2016) In production SEAGrid portal for some user accounts getting error 'User is not authenticated or authorized' when tried to login
[ https://issues.apache.org/jira/browse/AIRAVATA-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2016. --- Resolution: Fixed > In production SEAGrid portal for some user accounts getting error 'User is > not authenticated or authorized' when tried to login > --- > > Key: AIRAVATA-2016 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2016 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://seagrid.org/ >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > For some users getting the ErrorException but not for all of them. Users with > admin, gateway-user role got the error and at the same time users with same > access roles were able to login without an issue. > Please check. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2048) In SEAGrid desktop client cannot view the experiment summary when multiple optional input files are uploaded.
[ https://issues.apache.org/jira/browse/AIRAVATA-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2048. --- Resolution: Fixed > In SEAGrid desktop client cannot view the experiment summary when multiple > optional input files are uploaded. > - > > Key: AIRAVATA-2048 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2048 > Project: Airavata > Issue Type: Bug >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Submitted an experiment with multiple optional files. Experiment got executed > and status is displayed as COMPLETED in 'recent experiment tab. But cannot > view the experiment summary. giving error [1] > Experiment ID: Aut-Vina1_a8b91184-6cb8-439a-a3a6-76232d07376c > Experiment can be viewed in web application and shows both job and experiment > in COMPLETED state. > [1] > java.lang.IndexOutOfBoundsException: Index: 19, Size: 17 > at java.util.ArrayList.rangeCheckForAdd(ArrayList.java:661) > at java.util.ArrayList.add(ArrayList.java:473) > at > com.sun.javafx.collections.ObservableListWrapper.doAdd(ObservableListWrapper.java:101) > at > javafx.collections.ModifiableObservableListBase.add(ModifiableObservableListBase.java:151) > at > org.seagrid.desktop.ui.experiment.summary.controller.ExperimentSummaryController.showExperimentInputs(ExperimentSummaryController.java:434) > at > org.seagrid.desktop.ui.experiment.summary.controller.ExperimentSummaryController.initExperimentInfo(ExperimentSummaryController.java:275) > at > org.seagrid.desktop.ui.experiment.summary.controller.ExperimentSummaryController.initExperimentInfo(ExperimentSummaryController.java:300) > at > org.seagrid.desktop.ui.experiment.summary.ExperimentSummaryWindow.getExperimentInfoNode(ExperimentSummaryWindow.java:54) > at > org.seagrid.desktop.ui.home.controller.HomeController.lambda$null$119(HomeController.java:394) > at > com.sun.javafx.event.CompositeEventHandler.dispatchBubblingEvent(CompositeEventHandler.java:86) > at > com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:238) > at > com.sun.javafx.event.EventHandlerManager.dispatchBubblingEvent(EventHandlerManager.java:191) > at > com.sun.javafx.event.CompositeEventDispatcher.dispatchBubblingEvent(CompositeEventDispatcher.java:59) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:58) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at > com.sun.javafx.event.BasicEventDispatcher.dispatchEvent(BasicEventDispatcher.java:56) > at > com.sun.javafx.event.EventDispatchChainImpl.dispatchEvent(EventDispatchChainImpl.java:114) > at com.sun.javafx.event.EventUtil.fireEventImpl(EventUtil.java:74) > at com.sun.javafx.event.EventUtil.fireEvent(EventUtil.java:54) > at javafx.event.Event.fireEvent(Event.java:198) > at javafx.scene.Scene$ClickGenerator.postProcess(Scene.java:3470) > at javafx.scene.Scene$ClickGenerator.access$8100(Scene.java:3398) > at javafx.scene.Scene$MouseHandler.process(Scene.java:3766) > at javafx.scene.Scene$MouseHandler.access$1500(Scene.java:3485) > at javafx.scene.Scene.impl_processMouseEvent(Scene.java:1762) > at javafx.scene.Scene$ScenePeerListener.mouseEvent(Scene.java:2494) > at > com.sun.javafx.tk.quantum.GlassViewEventHandler$MouseEventNotification.run(GlassViewEventHandler.java:352) > at > com.sun.javafx.tk.quantum.GlassViewEventHandler$MouseEventNotification.run(GlassViewEventHandler.java:275) > at
[jira] [Resolved] (AIRAVATA-2080) When tried to view the project summary gives error exception in dev seagrid portal
[ https://issues.apache.org/jira/browse/AIRAVATA-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-2080. --- Resolution: Fixed > When tried to view the project summary gives error exception in dev seagrid > portal > -- > > Key: AIRAVATA-2080 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2080 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Attachments: Screen Shot 2016-09-02 at 2.26.29 PM.png > > > error exception > Error while retrieving the job statuses. More info : Internal error > processing getJobStatuses (View: > /var/www/portals/dev-seagrid/app/views/project/summary.blade.php) > when tried to view project summary. This project was created today and it has > experiment which has no job status in it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1969) 'Register a new Password Credential' not working
[ https://issues.apache.org/jira/browse/AIRAVATA-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1969. --- Resolution: Fixed > 'Register a new Password Credential' not working > > > Key: AIRAVATA-1969 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1969 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.seagrid.org/ >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.16 > > > With latest release section 'Password Credentials' added to Credential Store > UI. But the button does not function. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1968) In Admin Dashboard --> Gateway Profile section Identity Server Configuration is not functioning
[ https://issues.apache.org/jira/browse/AIRAVATA-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1968. --- Resolution: Fixed > In Admin Dashboard --> Gateway Profile section Identity Server Configuration > is not functioning > --- > > Key: AIRAVATA-1968 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1968 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.16 > > > In Admin Dashboard --> Gateway Profile section 'Identity Server > Configuration' is not functioning. > With latest PGA release in Gateway Profile page there are two text fields > (Tenant ID and Password Credential Token) added but they are not functioning; > empty fields without any link to actions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1624) [GSoC] Securing Airavata API
[ https://issues.apache.org/jira/browse/AIRAVATA-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1624. --- Resolution: Fixed > [GSoC] Securing Airavata API > > > Key: AIRAVATA-1624 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1624 > Project: Airavata > Issue Type: New Feature > Components: Airavata API >Reporter: Suresh Marru >Assignee: Supun Chathuranga Nakandala > Labels: gsoc, gsoc2015, mentor > Fix For: WISHLIST > > Attachments: Securing_ARAVATA_API_V1.pdf > > > Apache Airavata uses Thrift based API's for external facing API's and for > system internal CPI's. The API's need to be secured adding authentication and > authorization capabilities. > The Authentication need to ensure only approved users/clients can > communicate. Similarly clients should only interact with valid servers. > Authorization need to be enforced to ensure only users with specific roles > can appropriately access specific API's. As an example, administrative roles > should be able see all the users experiments where as end users can only see > his/her data and not access other information (unless explicitly shared). > Earlier GSoC project focused on this topic has relavent discussion. > https://cwiki.apache.org/confluence/display/AIRAVATA/GSoC+2014+-+Add+Security+capabilities+to+Airavata+Thrift+services+and+clients -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1927) In SEAGrid desktop client NanoCAD window 'Import Structure' screen is not opening
[ https://issues.apache.org/jira/browse/AIRAVATA-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1927. --- Resolution: Fixed > In SEAGrid desktop client NanoCAD window 'Import Structure' screen is not > opening > - > > Key: AIRAVATA-1927 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1927 > Project: Airavata > Issue Type: Bug >Affects Versions: 0.16 > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > Fix For: 0.16 > > > In NanoCAD window when clicked button 'structure' the 'Import Structure' > pop-up window does not open. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1688) Add Identity Server Admin Services PHP Stubs
[ https://issues.apache.org/jira/browse/AIRAVATA-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Chathuranga Nakandala resolved AIRAVATA-1688. --- Resolution: Fixed Assignee: Supun Chathuranga Nakandala > Add Identity Server Admin Services PHP Stubs > > > Key: AIRAVATA-1688 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1688 > Project: Airavata > Issue Type: New Feature > Components: PGA PHP Web Gateway >Reporter: Suresh Marru >Assignee: Supun Chathuranga Nakandala > > For PGA to remotely manage tentants and manage user roles, the following > stubs to identity server are required: > RemoteAuthorizationManagerService > TenantMgtAdminService > RemoteProfileConfigurationManagerService > RemoteClaimManagerService > Full reference of admin services is at - > https://github.com/wso2/carbon-identity/blob/master/components/remote-usermgt/org.wso2.carbon.um.ws.service/src/main/resources/META-INF/services.xml > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
