[jira] [Commented] (AIRAVATA-2816) Default project not getting created, new user sees all projects
[ https://issues.apache.org/jira/browse/AIRAVATA-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503681#comment-16503681 ] ASF subversion and git services commented on AIRAVATA-2816: --- Commit 2919c7af8328a159eeb5aef0d7dddb0211088d27 in airavata's branch refs/heads/group-based-auth from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=2919c7a ] AIRAVATA-2816 Return empty project list when user has no projects > Default project not getting created, new user sees all projects > --- > > Key: AIRAVATA-2816 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2816 > Project: Airavata > Issue Type: Bug >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRAVATA-2816) Default project not getting created, new user sees all projects
Marcus Christie created AIRAVATA-2816: - Summary: Default project not getting created, new user sees all projects Key: AIRAVATA-2816 URL: https://issues.apache.org/jira/browse/AIRAVATA-2816 Project: Airavata Issue Type: Bug Reporter: Marcus Christie -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (AIRAVATA-2816) Default project not getting created, new user sees all projects
[ https://issues.apache.org/jira/browse/AIRAVATA-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie reassigned AIRAVATA-2816: - Assignee: Marcus Christie > Default project not getting created, new user sees all projects > --- > > Key: AIRAVATA-2816 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2816 > Project: Airavata > Issue Type: Bug >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AIRAVATA-2802) When clicked 'Create' from Experiment menu in PGA, throwing an error exception
[ https://issues.apache.org/jira/browse/AIRAVATA-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie resolved AIRAVATA-2802. --- Resolution: Cannot Reproduce > When clicked 'Create' from Experiment menu in PGA, throwing an error exception > -- > > Key: AIRAVATA-2802 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2802 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.18 > Environment: https://pga.group-based-auth.scigap.org/ >Reporter: Eroma >Assignee: Marcus Christie >Priority: Major > Fix For: 0.18 > > Attachments: Screen Shot 2018-06-04 at 1.41.15 PM.png > > > When tried to create an experiment (just clicked the create in the Experiment > menu) getting error exception: > Invalid argument supplied for foreach() (View: > /var/www/portals/group-based-auth-seagrid/app/views/experiment/create.blade.php) > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRAVATA-2815) First experiment fails after API server restart
Eroma created AIRAVATA-2815: --- Summary: First experiment fails after API server restart Key: AIRAVATA-2815 URL: https://issues.apache.org/jira/browse/AIRAVATA-2815 Project: Airavata Issue Type: Bug Components: Airavata API, helix implementation, Registry API Affects Versions: 0.18 Environment: https://staging.ultrascan.scigap.org/home Reporter: Eroma Assignee: Dimuthu Upeksha Fix For: 0.18 After API server restart the connections to Helix servers drops. As a result the very first experiment doesn't move beyond LAUNCHED and its failed in the back end. Helix should have a way of establishing the link and have the experiment reprocessed rather than failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AIRAVATA-2797) Cannot login with newly created accounts in the PGA
[ https://issues.apache.org/jira/browse/AIRAVATA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie resolved AIRAVATA-2797. --- Resolution: Fixed > Cannot login with newly created accounts in the PGA > --- > > Key: AIRAVATA-2797 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2797 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.18 > Environment: https://pga.group-based-auth.scigap.org/login >Reporter: Eroma >Assignee: Marcus Christie >Priority: Major > Fix For: 0.18 > > Attachments: Screen Shot 2018-06-01 at 3.38.58 PM.png > > > # Created a new account and was able to login to the gateway when in > pending-user role. > # After receiving the privilege change email, tried to login and getting > Airavata system exception. "Error while retrieving user resource profile. > More info : getUserResourceProfile failed: unknown result" > # User cannot login to dashbaord. > # When the exception page was refreshed, then the error is gone and user is > in [https://pga.group-based-auth.scigap.org/home] > # User has gateway-user role. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2797) Cannot login with newly created accounts in the PGA
[ https://issues.apache.org/jira/browse/AIRAVATA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503548#comment-16503548 ] ASF subversion and git services commented on AIRAVATA-2797: --- Commit ecf6de27953cecd730f1c15a20fb228958af7736 in airavata-php-gateway's branch refs/heads/develop from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata-php-gateway.git;h=ecf6de2 ] AIRAVATA-2797 using isUserResourceProfileExists API method > Cannot login with newly created accounts in the PGA > --- > > Key: AIRAVATA-2797 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2797 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.18 > Environment: https://pga.group-based-auth.scigap.org/login >Reporter: Eroma >Assignee: Marcus Christie >Priority: Major > Fix For: 0.18 > > Attachments: Screen Shot 2018-06-01 at 3.38.58 PM.png > > > # Created a new account and was able to login to the gateway when in > pending-user role. > # After receiving the privilege change email, tried to login and getting > Airavata system exception. "Error while retrieving user resource profile. > More info : getUserResourceProfile failed: unknown result" > # User cannot login to dashbaord. > # When the exception page was refreshed, then the error is gone and user is > in [https://pga.group-based-auth.scigap.org/home] > # User has gateway-user role. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2781) migration script to give Admins WRITE on every Project, Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503549#comment-16503549 ] ASF subversion and git services commented on AIRAVATA-2781: --- Commit 8358e6b5d3f9b2be2fa5f3f77eacb82cf3d817af in airavata-php-gateway's branch refs/heads/develop from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata-php-gateway.git;h=8358e6b ] AIRAVATA-2781 Using userHasAccess to test migration script > migration script to give Admins WRITE on every Project, Experiment > -- > > Key: AIRAVATA-2781 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2781 > Project: Airavata > Issue Type: Story >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > > * give "Read Only Admins" group READ on every Project, Experiment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRAVATA-2814) Error: "PersistenceException: Table "PROJECT" has a foreign key to table "USERS" that has not been generated."
[
https://issues.apache.org/jira/browse/AIRAVATA-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-2814:
--
Description:
This error occurs int he logs when the API server starts up.
Stacktrace:
{noformat}
2018-06-06 16:22:34,167 [pool-9-thread-2] ERROR
o.a.a.r.a.s.h.RegistryServerHandler - default
java.lang.RuntimeException: Failed to get Experiment Catalog EntityManager
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.execute(ExpCatAbstractRepository.java:95)
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.get(ExpCatAbstractRepository.java:49)
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.isExists(ExpCatAbstractRepository.java:87)
at
org.apache.airavata.registry.core.repositories.expcatalog.GatewayRepository.isGatewayExist(GatewayRepository.java:99)
at
org.apache.airavata.registry.api.service.handler.RegistryServerHandler.isGatewayExistInternal(RegistryServerHandler.java:4165)
at
org.apache.airavata.registry.api.service.handler.RegistryServerHandler.getGatewayResourceProfile(RegistryServerHandler.java:1966)
at
org.apache.airavata.registry.api.RegistryService$Processor$getGatewayResourceProfile.getResult(RegistryService.java:17795)
at
org.apache.airavata.registry.api.RegistryService$Processor$getGatewayResourceProfile.getResult(RegistryService.java:17779)
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)
Caused by: org.apache.openjpa.persistence.PersistenceException: Table "PROJECT"
has a foreign key to table "USERS" that has not been generated. You must run
the schema generator on all inter-related tables at once.
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559)
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455)
at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
at
org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
at
org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156)
at
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227)
at
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:154)
at
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:60)
at
org.apache.airavata.registry.core.utils.JPAUtil.ExpCatalogJPAUtils.getEntityManager(ExpCatalogJPAUtils.java:71)
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.execute(ExpCatAbstractRepository.java:93)
... 13 common frames omitted
{noformat}
was:
Stacktrace:
{noformat}
2018-06-06 16:22:34,167 [pool-9-thread-2] ERROR
o.a.a.r.a.s.h.RegistryServerHandler - default
java.lang.RuntimeException: Failed to get Experiment Catalog EntityManager
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.execute(ExpCatAbstractRepository.java:95)
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.get(ExpCatAbstractRepository.java:49)
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.isExists(ExpCatAbstractRepository.java:87)
at
org.apache.airavata.registry.core.repositories.expcatalog.GatewayRepository.isGatewayExist(GatewayRepository.java:99)
at
org.apache.airavata.registry.api.service.handler.RegistryServerHandler.isGatewayExistInternal(RegistryServerHandler.java:4165)
at
org.apache.airavata.registry.api.service.handler.RegistryServerHandler.getGatewayResourceProfile(RegistryServerHandler.java:1966)
at
org.apache.airavata.registry.api.RegistryService$Processor$getGatewayResourceProfile.getResult(RegistryService.java:17795)
at
org.apache.airavata.registry.api.RegistryService$Processor$getGatewayResourceProfile.getResult(RegistryService.java:17779)
at
[jira] [Created] (AIRAVATA-2814) Error: "PersistenceException: Table "PROJECT" has a foreign key to table "USERS" that has not been generated."
Marcus Christie created AIRAVATA-2814:
-
Summary: Error: "PersistenceException: Table "PROJECT" has a
foreign key to table "USERS" that has not been generated."
Key: AIRAVATA-2814
URL: https://issues.apache.org/jira/browse/AIRAVATA-2814
Project: Airavata
Issue Type: Bug
Reporter: Marcus Christie
Assignee: Marcus Christie
Stacktrace:
{noformat}
2018-06-06 16:22:34,167 [pool-9-thread-2] ERROR
o.a.a.r.a.s.h.RegistryServerHandler - default
java.lang.RuntimeException: Failed to get Experiment Catalog EntityManager
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.execute(ExpCatAbstractRepository.java:95)
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.get(ExpCatAbstractRepository.java:49)
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.isExists(ExpCatAbstractRepository.java:87)
at
org.apache.airavata.registry.core.repositories.expcatalog.GatewayRepository.isGatewayExist(GatewayRepository.java:99)
at
org.apache.airavata.registry.api.service.handler.RegistryServerHandler.isGatewayExistInternal(RegistryServerHandler.java:4165)
at
org.apache.airavata.registry.api.service.handler.RegistryServerHandler.getGatewayResourceProfile(RegistryServerHandler.java:1966)
at
org.apache.airavata.registry.api.RegistryService$Processor$getGatewayResourceProfile.getResult(RegistryService.java:17795)
at
org.apache.airavata.registry.api.RegistryService$Processor$getGatewayResourceProfile.getResult(RegistryService.java:17779)
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)
Caused by: org.apache.openjpa.persistence.PersistenceException: Table "PROJECT"
has a foreign key to table "USERS" that has not been generated. You must run
the schema generator on all inter-related tables at once.
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559)
at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455)
at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
at
org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
at
org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
at
org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:156)
at
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:227)
at
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:154)
at
org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:60)
at
org.apache.airavata.registry.core.utils.JPAUtil.ExpCatalogJPAUtils.getEntityManager(ExpCatalogJPAUtils.java:71)
at
org.apache.airavata.registry.core.repositories.expcatalog.ExpCatAbstractRepository.execute(ExpCatAbstractRepository.java:93)
... 13 common frames omitted
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2797) Cannot login with newly created accounts in the PGA
[ https://issues.apache.org/jira/browse/AIRAVATA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503509#comment-16503509 ] ASF subversion and git services commented on AIRAVATA-2797: --- Commit 64b567846647526d3309234f4d6cce2b83239f28 in airavata's branch refs/heads/group-based-auth from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=64b5678 ] AIRAVATA-2797 Removing use of removed isNull flag > Cannot login with newly created accounts in the PGA > --- > > Key: AIRAVATA-2797 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2797 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.18 > Environment: https://pga.group-based-auth.scigap.org/login >Reporter: Eroma >Assignee: Marcus Christie >Priority: Major > Fix For: 0.18 > > Attachments: Screen Shot 2018-06-01 at 3.38.58 PM.png > > > # Created a new account and was able to login to the gateway when in > pending-user role. > # After receiving the privilege change email, tried to login and getting > Airavata system exception. "Error while retrieving user resource profile. > More info : getUserResourceProfile failed: unknown result" > # User cannot login to dashbaord. > # When the exception page was refreshed, then the error is gone and user is > in [https://pga.group-based-auth.scigap.org/home] > # User has gateway-user role. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2797) Cannot login with newly created accounts in the PGA
[ https://issues.apache.org/jira/browse/AIRAVATA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503485#comment-16503485 ] ASF subversion and git services commented on AIRAVATA-2797: --- Commit f56bbe36f8f895e645c10b3ab1e00235756dbdf3 in airavata's branch refs/heads/group-based-auth from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=f56bbe3 ] AIRAVATA-2797 Regenerate Thrift stubs > Cannot login with newly created accounts in the PGA > --- > > Key: AIRAVATA-2797 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2797 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.18 > Environment: https://pga.group-based-auth.scigap.org/login >Reporter: Eroma >Assignee: Marcus Christie >Priority: Major > Fix For: 0.18 > > Attachments: Screen Shot 2018-06-01 at 3.38.58 PM.png > > > # Created a new account and was able to login to the gateway when in > pending-user role. > # After receiving the privilege change email, tried to login and getting > Airavata system exception. "Error while retrieving user resource profile. > More info : getUserResourceProfile failed: unknown result" > # User cannot login to dashbaord. > # When the exception page was refreshed, then the error is gone and user is > in [https://pga.group-based-auth.scigap.org/home] > # User has gateway-user role. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2797) Cannot login with newly created accounts in the PGA
[ https://issues.apache.org/jira/browse/AIRAVATA-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503484#comment-16503484 ] ASF subversion and git services commented on AIRAVATA-2797: --- Commit d2811fbd0356688a14509ce640e7a4e981374884 in airavata's branch refs/heads/group-based-auth from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=d2811fb ] AIRAVATA-2797 Add isUserResourceProfileExists to API instead of isNull flag > Cannot login with newly created accounts in the PGA > --- > > Key: AIRAVATA-2797 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2797 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.18 > Environment: https://pga.group-based-auth.scigap.org/login >Reporter: Eroma >Assignee: Marcus Christie >Priority: Major > Fix For: 0.18 > > Attachments: Screen Shot 2018-06-01 at 3.38.58 PM.png > > > # Created a new account and was able to login to the gateway when in > pending-user role. > # After receiving the privilege change email, tried to login and getting > Airavata system exception. "Error while retrieving user resource profile. > More info : getUserResourceProfile failed: unknown result" > # User cannot login to dashbaord. > # When the exception page was refreshed, then the error is gone and user is > in [https://pga.group-based-auth.scigap.org/home] > # User has gateway-user role. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AIRAVATA-2801) Cannot create new projects in group base auth implementation. Throws AIravataSystemException.
[
https://issues.apache.org/jira/browse/AIRAVATA-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie resolved AIRAVATA-2801.
---
Resolution: Fixed
> Cannot create new projects in group base auth implementation. Throws
> AIravataSystemException.
> -
>
> Key: AIRAVATA-2801
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2801
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
>Affects Versions: 0.18
> Environment: https://pga.group-based-auth.scigap.org/
>Reporter: Eroma
>Assignee: Marcus Christie
>Priority: Major
> Fix For: 0.18
>
> Attachments: Screen Shot 2018-06-04 at 12.16.33 PM.png
>
>
> When tried to save a new project, getting an Airavata System Exception
> AiravataSystemException!
> Error while retrieving the experiments. More info : Error while retrieving
> the experiments. More info : (conn:14649) Unknown column
> 't1.GATEWAY_INSTANCE_ID' in 'field list' \{prepstmnt 2101807834 SELECT
> t0.EXPERIMENT_ID, t1.PROCESS_ID, t1.APPLICATION_DEPLOYMENT_ID,
> t1.APPLICATION_INTERFACE_ID, t1.COMPUTE_RESOURCE_ID, t1.CREATION_TIME,
> t1.ENABLE_EMAIL_NOTIFICATION, t1.EXPERIMENT_ID, t1.EXPERIMENT_DATA_DIR,
> t1.GATEWAY_EXECUTION_ID, t1.GATEWAY_INSTANCE_ID, t1.GENERATE_CERT,
> t1.GROUP_RESOURCE_PROFILE_ID, t1.LAST_UPDATE_TIME, t1.PROCESS_DETAIL,
> t2.PROCESS_ID, t2.NODE_COUNT, t2.NUMBER_OF_THREADS, t2.QUEUE_NAME,
> t2.RESOURCE_HOST_ID, t2.TOTAL_CPU_COUNT, t2.TOTAL_PHYSICAL_MEMORY,
> t2.WALL_TIME_LIMIT, t1.STORAGE_RESOURCE_ID, t1.TASK_DAG,
> t1.IS_USE_USER_CR_PREF, t1.USER_DN, t1.USERNAME FROM EXPERIMENT t0 INNER JOIN
> PROCESS t1 ON t0.EXPERIMENT_ID = t1.EXPERIMENT_ID LEFT OUTER JOIN
> PROCESS_RESOURCE_SCHEDULE t2 ON t1.PROCESS_ID = t2.PROCESS_ID WHERE
> (t0.PROJECT_ID LIKE ? ESCAPE '\\') ORDER BY t0.EXPERIMENT_ID ASC
> [params=(String) Test1_c822fbfb-0300-4187-9773-5875caf79298]} [code=1054,
> state=42S22]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2704) Improve the process of running the Sharing Registry data migrator
[
https://issues.apache.org/jira/browse/AIRAVATA-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503397#comment-16503397
]
ASF subversion and git services commented on AIRAVATA-2704:
---
Commit f5bd24a7fd4ee29f3b4b2510387f1a175e6d0bc7 in airavata's branch
refs/heads/group-based-auth from [~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=f5bd24a ]
AIRAVATA-2704 Add plugin for running AiravataDataMigrator with maven
Can run the migration script by using `mvn compile exec:java`. See
README.md for details.
> Improve the process of running the Sharing Registry data migrator
> -
>
> Key: AIRAVATA-2704
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2704
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Currently the process of running the sharing registry data migrator is
> undocumented and probably unnecessarily complex. Here's what [~tilaks26] and
> I had to do to run it:
> * (/) create a src/main/resources directory and copy the
> airavata-server.properties file from airavata-server-configuration into this
> directory
> * (/) we then needed to change the following properties
> ** sharingcatalog.jdbc.driver=org.mariadb.jdbc.Driver
> ** sharingcatalog.jdbc.url=jdbc:mariadb://XXX.XXX.XXX.XXX:3306/sharing_catalog
> ** sharingcatalog.jdbc.user=airavata
> ** sharingcatalog.jdbc.password=XX
> ** credential.store.server.host=XXX.XXX.XXX.XXX
> ** regserver.server.host=X.X.X
> ** regserver.server.port=8970
> ** trust.store=/path/to/client_truststore.jks
> ** trust.store.password=...
> * (/) next was modifying ConnectionFactory and add the MySQL connection info
> * (/) we also needed to add the mariadb driver to the pom.xml
> {code:xml}
>
> org.mariadb.jdbc
> mariadb-java-client
> 2.0.2
>
> {code}
> * also had to run {{mvn install}} in sharing-registry to run the openjpa
> enhancement otherwise we got errors about the models not being enhanced.
> I think ideally we would only make calls to the services instead of accessing
> the database directly, but perhaps I'm missing something and we really do
> need to access the database directly. Also we need an easier way of running
> it, maybe with some Maven integration so we can run it from Maven.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AIRAVATA-2704) Improve the process of running the Sharing Registry data migrator
[
https://issues.apache.org/jira/browse/AIRAVATA-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie resolved AIRAVATA-2704.
---
Resolution: Fixed
> Improve the process of running the Sharing Registry data migrator
> -
>
> Key: AIRAVATA-2704
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2704
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Currently the process of running the sharing registry data migrator is
> undocumented and probably unnecessarily complex. Here's what [~tilaks26] and
> I had to do to run it:
> * (/) create a src/main/resources directory and copy the
> airavata-server.properties file from airavata-server-configuration into this
> directory
> * (/) we then needed to change the following properties
> ** sharingcatalog.jdbc.driver=org.mariadb.jdbc.Driver
> ** sharingcatalog.jdbc.url=jdbc:mariadb://XXX.XXX.XXX.XXX:3306/sharing_catalog
> ** sharingcatalog.jdbc.user=airavata
> ** sharingcatalog.jdbc.password=XX
> ** credential.store.server.host=XXX.XXX.XXX.XXX
> ** regserver.server.host=X.X.X
> ** regserver.server.port=8970
> ** trust.store=/path/to/client_truststore.jks
> ** trust.store.password=...
> * (/) next was modifying ConnectionFactory and add the MySQL connection info
> * (/) we also needed to add the mariadb driver to the pom.xml
> {code:xml}
>
> org.mariadb.jdbc
> mariadb-java-client
> 2.0.2
>
> {code}
> * also had to run {{mvn install}} in sharing-registry to run the openjpa
> enhancement otherwise we got errors about the models not being enhanced.
> I think ideally we would only make calls to the services instead of accessing
> the database directly, but perhaps I'm missing something and we really do
> need to access the database directly. Also we need an easier way of running
> it, maybe with some Maven integration so we can run it from Maven.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (AIRAVATA-2704) Improve the process of running the Sharing Registry data migrator
[
https://issues.apache.org/jira/browse/AIRAVATA-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie reopened AIRAVATA-2704:
---
Assignee: Marcus Christie
Going to configure this so we can run it from Maven.
> Improve the process of running the Sharing Registry data migrator
> -
>
> Key: AIRAVATA-2704
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2704
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Currently the process of running the sharing registry data migrator is
> undocumented and probably unnecessarily complex. Here's what [~tilaks26] and
> I had to do to run it:
> * (/) create a src/main/resources directory and copy the
> airavata-server.properties file from airavata-server-configuration into this
> directory
> * (/) we then needed to change the following properties
> ** sharingcatalog.jdbc.driver=org.mariadb.jdbc.Driver
> ** sharingcatalog.jdbc.url=jdbc:mariadb://XXX.XXX.XXX.XXX:3306/sharing_catalog
> ** sharingcatalog.jdbc.user=airavata
> ** sharingcatalog.jdbc.password=XX
> ** credential.store.server.host=XXX.XXX.XXX.XXX
> ** regserver.server.host=X.X.X
> ** regserver.server.port=8970
> ** trust.store=/path/to/client_truststore.jks
> ** trust.store.password=...
> * (/) next was modifying ConnectionFactory and add the MySQL connection info
> * (/) we also needed to add the mariadb driver to the pom.xml
> {code:xml}
>
> org.mariadb.jdbc
> mariadb-java-client
> 2.0.2
>
> {code}
> * also had to run {{mvn install}} in sharing-registry to run the openjpa
> enhancement otherwise we got errors about the models not being enhanced.
> I think ideally we would only make calls to the services instead of accessing
> the database directly, but perhaps I'm missing something and we really do
> need to access the database directly. Also we need an easier way of running
> it, maybe with some Maven integration so we can run it from Maven.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (AIRAVATA-2781) migration script to give Admins WRITE on every Project, Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie resolved AIRAVATA-2781. --- Resolution: Fixed > migration script to give Admins WRITE on every Project, Experiment > -- > > Key: AIRAVATA-2781 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2781 > Project: Airavata > Issue Type: Story >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > > * give "Read Only Admins" group READ on every Project, Experiment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2781) migration script to give Admins WRITE on every Project, Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503305#comment-16503305 ] ASF subversion and git services commented on AIRAVATA-2781: --- Commit 8dacd905dd5e4f3827bc9012442dde150bc7fd01 in airavata's branch refs/heads/group-based-auth from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=8dacd90 ] AIRAVATA-2781 Give Admins WRITE on every Project, Experiment > migration script to give Admins WRITE on every Project, Experiment > -- > > Key: AIRAVATA-2781 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2781 > Project: Airavata > Issue Type: Story >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > > * give "Read Only Admins" group READ on every Project, Experiment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
