[jira] [Resolved] (AIRAVATA-2812) Cannot create new experiments. Getting error 'Failed to create experiment: Trying to get property of non-object'
[ https://issues.apache.org/jira/browse/AIRAVATA-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie resolved AIRAVATA-2812. --- Resolution: Fixed > Cannot create new experiments. Getting error 'Failed to create experiment: > Trying to get property of non-object' > > > Key: AIRAVATA-2812 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2812 > 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-05 at 1.37.12 PM.png > > > When clicked Save and Launch for a new experiment getting error "Failed to > create experiment: Trying to get property of non-object'. But the experiment > record exists in the experiment summary without a compute resource (refer > attachement) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AIRAVATA-2818) Error: No enum constant org.apache.airavata.model.data.replica.DataProductType.0
[
https://issues.apache.org/jira/browse/AIRAVATA-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie resolved AIRAVATA-2818.
---
Resolution: Fixed
> Error: No enum constant
> org.apache.airavata.model.data.replica.DataProductType.0
>
>
> Key: AIRAVATA-2818
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2818
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Stacktrace:
> {noformat}
> 2018-06-07 20:17:37,251 [pool-9-thread-5] ERROR
> o.a.t.server.TThreadPoolServer - Error occurred during processing of m
> essage.
> org.apache.openjpa.persistence.PersistenceException: No enum constant
> org.apache.airavata.model.data.replica.DataProduc
> tType.0
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:1017)
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:911)
> at
> org.apache.openjpa.kernel.DelegatingBroker.find(DelegatingBroker.java:231)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.find(EntityManagerImpl.java:487)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.lambda$get$2(RepCatAb
> stractRepository.java:70)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.execute(RepCatAbstractRepository.java:119)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.get(RepCatAbstractRepository.java:69)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.DataProductRepository.getDataProduct(DataProductRepository.java:112)
> at
> org.apache.airavata.registry.api.service.handler.RegistryServerHandler.getDataProduct(RegistryServerHandler.java:2283)
> at
> org.apache.airavata.registry.api.RegistryService$Processor$getDataProduct.getResult(RegistryService.java:18799)
> at
> org.apache.airavata.registry.api.RegistryService$Processor$getDataProduct.getResult(RegistryService.java:18783)
> 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: java.lang.IllegalArgumentException: No enum constant
> org.apache.airavata.model.data.replica.DataProductType.0
> at java.lang.Enum.valueOf(Enum.java:238)
> at
> org.apache.openjpa.jdbc.meta.strats.EnumValueHandler.toObjectValue(EnumValueHandler.java:118)
> at
> org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.load(HandlerFieldStrategy.java:189)
> at
> org.apache.openjpa.jdbc.meta.FieldMapping.load(FieldMapping.java:928)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1094)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1038)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initializeState(JDBCStoreManager.java:409)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initialize(JDBCStoreManager.java:304)
> at
> org.apache.openjpa.kernel.DelegatingStoreManager.initialize(DelegatingStoreManager.java:112)
> at
> org.apache.openjpa.kernel.ROPStoreManager.initialize(ROPStoreManager.java:57)
> at
> org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:1036)
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:994)
> ... 16 common frames omitted
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2818) Error: No enum constant org.apache.airavata.model.data.replica.DataProductType.0
[
https://issues.apache.org/jira/browse/AIRAVATA-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505285#comment-16505285
]
Marcus Christie commented on AIRAVATA-2818:
---
I fixed this by updating the columns with value '0' to the corresponding enum
string value:
{code:sql}
update DATA_PRODUCT set PRODUCT_TYPE = 'FILE' where PRODUCT_TYPE = '0';
update DATA_REPLICA_LOCATION set REPLICA_LOCATION_CATEGORY =
'GATEWAY_DATA_STORE' where REPLICA_LOCATION_CATEGORY = '0';
update DATA_REPLICA_LOCATION set REPLICA_PERSISTENT_TYPE = 'TRANSIENT' where
REPLICA_PERSISTENT_TYPE = '0';
{code}
> Error: No enum constant
> org.apache.airavata.model.data.replica.DataProductType.0
>
>
> Key: AIRAVATA-2818
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2818
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Stacktrace:
> {noformat}
> 2018-06-07 20:17:37,251 [pool-9-thread-5] ERROR
> o.a.t.server.TThreadPoolServer - Error occurred during processing of m
> essage.
> org.apache.openjpa.persistence.PersistenceException: No enum constant
> org.apache.airavata.model.data.replica.DataProduc
> tType.0
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:1017)
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:911)
> at
> org.apache.openjpa.kernel.DelegatingBroker.find(DelegatingBroker.java:231)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.find(EntityManagerImpl.java:487)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.lambda$get$2(RepCatAb
> stractRepository.java:70)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.execute(RepCatAbstractRepository.java:119)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.get(RepCatAbstractRepository.java:69)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.DataProductRepository.getDataProduct(DataProductRepository.java:112)
> at
> org.apache.airavata.registry.api.service.handler.RegistryServerHandler.getDataProduct(RegistryServerHandler.java:2283)
> at
> org.apache.airavata.registry.api.RegistryService$Processor$getDataProduct.getResult(RegistryService.java:18799)
> at
> org.apache.airavata.registry.api.RegistryService$Processor$getDataProduct.getResult(RegistryService.java:18783)
> 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: java.lang.IllegalArgumentException: No enum constant
> org.apache.airavata.model.data.replica.DataProductType.0
> at java.lang.Enum.valueOf(Enum.java:238)
> at
> org.apache.openjpa.jdbc.meta.strats.EnumValueHandler.toObjectValue(EnumValueHandler.java:118)
> at
> org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.load(HandlerFieldStrategy.java:189)
> at
> org.apache.openjpa.jdbc.meta.FieldMapping.load(FieldMapping.java:928)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1094)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1038)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initializeState(JDBCStoreManager.java:409)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initialize(JDBCStoreManager.java:304)
> at
> org.apache.openjpa.kernel.DelegatingStoreManager.initialize(DelegatingStoreManager.java:112)
> at
> org.apache.openjpa.kernel.ROPStoreManager.initialize(ROPStoreManager.java:57)
> at
> org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:1036)
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:994)
> ... 16 common frames omitted
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2715) Cannot use '&' in user account creation in airavata pga gateway
[ https://issues.apache.org/jira/browse/AIRAVATA-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505258#comment-16505258 ] ASF subversion and git services commented on AIRAVATA-2715: --- Commit 82b896f734eeed8c9725f56a8e0dc8bc77958ca5 in airavata-php-gateway's branch refs/heads/develop from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata-php-gateway.git;h=82b896f ] Merge branch 'password-ampersand-validation' Fixes AIRAVATA-2715 > Cannot use '&' in user account creation in airavata pga gateway > --- > > Key: AIRAVATA-2715 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2715 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.18 >Reporter: Eroma >Assignee: Marcus Christie >Priority: Major > Fix For: 0.18 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2500) Automated cluster account provisioning for gateway users
[ https://issues.apache.org/jira/browse/AIRAVATA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505260#comment-16505260 ] ASF subversion and git services commented on AIRAVATA-2500: --- Commit 81d59ea8a390e65d3c2e9e5f439de5796ba2231d in airavata-php-gateway's branch refs/heads/develop from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata-php-gateway.git;h=81d59ea ] AIRAVATA-2500 Don't display Additional Info if account is all set up > Automated cluster account provisioning for gateway users > > > Key: AIRAVATA-2500 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2500 > Project: Airavata > Issue Type: Bug > Components: Airavata System >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > > The initial use case for this system is the IU Cybergateway. We need the > following capabilities: > * query for whether a user has an account > ** for IU Cybergateway the user cluster access is determined by querying LDAP > * add an SSH public key for the user to authenticate (actually Airavata to > authenticate on behalf of the user) to the cluster > ** for IU Cybergateway the key is added to LDAP > Once the user has a cluster account and their SSH key has been added the > following additional things need to be done > * test that Airavata can authenticate to the cluster on the users behalf > * add a scratch location that Airavata will use for the user on the cluster > Eric Coulter has developed a prototype LDAP client that can query for a > user's account and deposit an SSH key in LDAP: > https://github.iu.edu/jecoulte/airavata-ldap-prototype (note: this link is > only accessible via IU credentials). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2675) Airavata middleware to handle input files and output files with space within the file name
[ https://issues.apache.org/jira/browse/AIRAVATA-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505256#comment-16505256 ] ASF subversion and git services commented on AIRAVATA-2675: --- Commit eda3b65da83679448d2af850241443cc775c522b in airavata-php-gateway's branch refs/heads/develop from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata-php-gateway.git;h=eda3b65 ] Merge pull request #81 from stephenpaul2727/AIRAVATA-2675 AIRAVATA-2674 FIXED > Airavata middleware to handle input files and output files with space within > the file name > -- > > Key: AIRAVATA-2675 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2675 > Project: Airavata > Issue Type: Bug > Components: Airavata System >Affects Versions: 0.18 >Reporter: Eroma >Assignee: Eroma >Priority: Major > Fix For: 0.18 > > > Data_Staging throws an error when the filename contains space. Burden of > uploading files without spaces should b=not be put on the gateway users. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2500) Automated cluster account provisioning for gateway users
[ https://issues.apache.org/jira/browse/AIRAVATA-2500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505259#comment-16505259 ] ASF subversion and git services commented on AIRAVATA-2500: --- Commit 52351bddf4de13552e29289fda32887cf2452f97 in airavata-php-gateway's branch refs/heads/develop from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata-php-gateway.git;h=52351bd ] Merge remote-tracking branch 'origin/AIRAVATA-2500' Merge LDAP based SSH account provisioning into master. > Automated cluster account provisioning for gateway users > > > Key: AIRAVATA-2500 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2500 > Project: Airavata > Issue Type: Bug > Components: Airavata System >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > > The initial use case for this system is the IU Cybergateway. We need the > following capabilities: > * query for whether a user has an account > ** for IU Cybergateway the user cluster access is determined by querying LDAP > * add an SSH public key for the user to authenticate (actually Airavata to > authenticate on behalf of the user) to the cluster > ** for IU Cybergateway the key is added to LDAP > Once the user has a cluster account and their SSH key has been added the > following additional things need to be done > * test that Airavata can authenticate to the cluster on the users behalf > * add a scratch location that Airavata will use for the user on the cluster > Eric Coulter has developed a prototype LDAP client that can query for a > user's account and deposit an SSH key in LDAP: > https://github.iu.edu/jecoulte/airavata-ldap-prototype (note: this link is > only accessible via IU credentials). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2798) Files don't download when filename contains special characters (like "#")
[ https://issues.apache.org/jira/browse/AIRAVATA-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505261#comment-16505261 ] ASF subversion and git services commented on AIRAVATA-2798: --- Commit 0054c6b911b8a4d84e528dd1aa118127454b5790 in airavata-php-gateway's branch refs/heads/develop from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata-php-gateway.git;h=0054c6b ] AIRAVATA-2798 encode special characters in filenames > Files don't download when filename contains special characters (like "#") > - > > Key: AIRAVATA-2798 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2798 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > > Initially reported by SEAGrid gateway: > https://scigap.atlassian.net/browse/SGRID-134 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2674) Re-write file names which has spaces in them
[ https://issues.apache.org/jira/browse/AIRAVATA-2674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505257#comment-16505257 ] ASF subversion and git services commented on AIRAVATA-2674: --- Commit eda3b65da83679448d2af850241443cc775c522b in airavata-php-gateway's branch refs/heads/develop from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata-php-gateway.git;h=eda3b65 ] Merge pull request #81 from stephenpaul2727/AIRAVATA-2675 AIRAVATA-2674 FIXED > Re-write file names which has spaces in them > > > Key: AIRAVATA-2674 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2674 > Project: Airavata > Issue Type: Sub-task > Components: Airavata API, PGA PHP Web Gateway >Affects Versions: 0.18 >Reporter: Eroma >Priority: Major > Fix For: 0.18 > > > Currently airavata could not handle experiment input files with space in the > file name. When an experiment is submitted with a space in the name it fails > at data staging with errors [1] in the log > > Users can be educated but this could keep occurring with new users, etc... > File name to rewrite to remove the space or to replace it wth another > character. > > [1] > org.apache.airavata.gfac.core.GFacException: Error: userFriendly msg :Error > while executing DATA_STAGING task, actual msg :expId: > MACs_in_Metagenomes_27ef130b-9428-4b74-8842-325a36bc544c, processId: > PROCESS_42be4be6-161f-428d-8539-5f375493179a, taskId: > TASK_b8f396cd-0e4e-4564-9101-5bcd4b4ddb6f, type: DATA_STAGING :- DATA_STAGING > failed. Reason: Source or destination uri is not correct source : > file://searchsra.scigap.org:/var/www/portals/gateway-user-data/searching-sra/aalker/DefaultProject/MACs_in_Metagenomes1518210858/SRR_Acc_List > (1).txt, destination : > SCP://g...@js-169-158.jetstream-cloud.org:22/home/gw/airavata-workdirs/PROCESS_42be4be6-161f-428d-8539-5f375493179a/ > at > org.apache.airavata.gfac.impl.GFacEngineImpl.checkFailures(GFacEngineImpl.java:628) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.inputDataStaging(GFacEngineImpl.java:609) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.executeTaskListFrom(GFacEngineImpl.java:347) > at > org.apache.airavata.gfac.impl.GFacEngineImpl.executeProcess(GFacEngineImpl.java:286) > at > org.apache.airavata.gfac.impl.GFacWorker.executeProcess(GFacWorker.java:227) > at org.apache.airavata.gfac.impl.GFacWorker.run(GFacWorker.java:86) at > org.apache.airavata.common.logging.MDCUtil.lambda$wrapWithMDC$0(MDCUtil.java:40) > 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) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (AIRAVATA-2818) Error: No enum constant org.apache.airavata.model.data.replica.DataProductType.0
[
https://issues.apache.org/jira/browse/AIRAVATA-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505216#comment-16505216
]
Marcus Christie edited comment on AIRAVATA-2818 at 6/7/18 8:30 PM:
---
Also getting
{noformat}
org.apache.openjpa.persistence.PersistenceException: No enum constant
org.apache.airavata.model.data.replica.ReplicaLoc
ationCategory.0
{noformat}
The problem is that the JPA mapping was set to use the default ENUM handling of
using the ordinal instead of the string value. The JPA mapping has been fixed
but some bad values (e..g, {{"0"}}) are now in the database.
was (Author: marcuschristie):
Also getting
{noformat}
org.apache.openjpa.persistence.PersistenceException: No enum constant
org.apache.airavata.model.data.replica.ReplicaLoc
ationCategory.0
{noformat}
The problem is that the JPA mapping was set to use the default ENUM handling of
using the ordinal instead of the string value. The JPA mapping has been fixed
but some bad values {{"0"}} are now in the database.
> Error: No enum constant
> org.apache.airavata.model.data.replica.DataProductType.0
>
>
> Key: AIRAVATA-2818
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2818
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Stacktrace:
> {noformat}
> 2018-06-07 20:17:37,251 [pool-9-thread-5] ERROR
> o.a.t.server.TThreadPoolServer - Error occurred during processing of m
> essage.
> org.apache.openjpa.persistence.PersistenceException: No enum constant
> org.apache.airavata.model.data.replica.DataProduc
> tType.0
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:1017)
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:911)
> at
> org.apache.openjpa.kernel.DelegatingBroker.find(DelegatingBroker.java:231)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.find(EntityManagerImpl.java:487)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.lambda$get$2(RepCatAb
> stractRepository.java:70)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.execute(RepCatAbstractRepository.java:119)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.get(RepCatAbstractRepository.java:69)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.DataProductRepository.getDataProduct(DataProductRepository.java:112)
> at
> org.apache.airavata.registry.api.service.handler.RegistryServerHandler.getDataProduct(RegistryServerHandler.java:2283)
> at
> org.apache.airavata.registry.api.RegistryService$Processor$getDataProduct.getResult(RegistryService.java:18799)
> at
> org.apache.airavata.registry.api.RegistryService$Processor$getDataProduct.getResult(RegistryService.java:18783)
> 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: java.lang.IllegalArgumentException: No enum constant
> org.apache.airavata.model.data.replica.DataProductType.0
> at java.lang.Enum.valueOf(Enum.java:238)
> at
> org.apache.openjpa.jdbc.meta.strats.EnumValueHandler.toObjectValue(EnumValueHandler.java:118)
> at
> org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.load(HandlerFieldStrategy.java:189)
> at
> org.apache.openjpa.jdbc.meta.FieldMapping.load(FieldMapping.java:928)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1094)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1038)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initializeState(JDBCStoreManager.java:409)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initialize(JDBCStoreManager.java:304)
> at
> org.apache.openjpa.kernel.DelegatingStoreManager.initialize(DelegatingStoreManager.java:112)
> at
> org.apache.openjpa.kernel.ROPStoreManager.initialize(ROPStoreManager.java:57)
> at
> org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:1036)
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:994)
> ... 16 common frames omitted
> {noformat}
--
This
[jira] [Commented] (AIRAVATA-2818) Error: No enum constant org.apache.airavata.model.data.replica.DataProductType.0
[
https://issues.apache.org/jira/browse/AIRAVATA-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505216#comment-16505216
]
Marcus Christie commented on AIRAVATA-2818:
---
Also getting
{noformat}
org.apache.openjpa.persistence.PersistenceException: No enum constant
org.apache.airavata.model.data.replica.ReplicaLoc
ationCategory.0
{noformat}
The problem is that the JPA mapping was set to use the default ENUM handling of
using the ordinal instead of the string value. The JPA mapping has been fixed
but some bad values {{"0"}} are now in the database.
> Error: No enum constant
> org.apache.airavata.model.data.replica.DataProductType.0
>
>
> Key: AIRAVATA-2818
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2818
> Project: Airavata
> Issue Type: Bug
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Stacktrace:
> {noformat}
> 2018-06-07 20:17:37,251 [pool-9-thread-5] ERROR
> o.a.t.server.TThreadPoolServer - Error occurred during processing of m
> essage.
> org.apache.openjpa.persistence.PersistenceException: No enum constant
> org.apache.airavata.model.data.replica.DataProduc
> tType.0
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:1017)
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:911)
> at
> org.apache.openjpa.kernel.DelegatingBroker.find(DelegatingBroker.java:231)
> at
> org.apache.openjpa.persistence.EntityManagerImpl.find(EntityManagerImpl.java:487)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.lambda$get$2(RepCatAb
> stractRepository.java:70)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.execute(RepCatAbstractRepository.java:119)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.get(RepCatAbstractRepository.java:69)
> at
> org.apache.airavata.registry.core.repositories.replicacatalog.DataProductRepository.getDataProduct(DataProductRepository.java:112)
> at
> org.apache.airavata.registry.api.service.handler.RegistryServerHandler.getDataProduct(RegistryServerHandler.java:2283)
> at
> org.apache.airavata.registry.api.RegistryService$Processor$getDataProduct.getResult(RegistryService.java:18799)
> at
> org.apache.airavata.registry.api.RegistryService$Processor$getDataProduct.getResult(RegistryService.java:18783)
> 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: java.lang.IllegalArgumentException: No enum constant
> org.apache.airavata.model.data.replica.DataProductType.0
> at java.lang.Enum.valueOf(Enum.java:238)
> at
> org.apache.openjpa.jdbc.meta.strats.EnumValueHandler.toObjectValue(EnumValueHandler.java:118)
> at
> org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.load(HandlerFieldStrategy.java:189)
> at
> org.apache.openjpa.jdbc.meta.FieldMapping.load(FieldMapping.java:928)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1094)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1038)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initializeState(JDBCStoreManager.java:409)
> at
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initialize(JDBCStoreManager.java:304)
> at
> org.apache.openjpa.kernel.DelegatingStoreManager.initialize(DelegatingStoreManager.java:112)
> at
> org.apache.openjpa.kernel.ROPStoreManager.initialize(ROPStoreManager.java:57)
> at
> org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:1036)
> at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:994)
> ... 16 common frames omitted
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AIRAVATA-2818) Error: No enum constant org.apache.airavata.model.data.replica.DataProductType.0
Marcus Christie created AIRAVATA-2818:
-
Summary: Error: No enum constant
org.apache.airavata.model.data.replica.DataProductType.0
Key: AIRAVATA-2818
URL: https://issues.apache.org/jira/browse/AIRAVATA-2818
Project: Airavata
Issue Type: Bug
Reporter: Marcus Christie
Assignee: Marcus Christie
Stacktrace:
{noformat}
2018-06-07 20:17:37,251 [pool-9-thread-5] ERROR o.a.t.server.TThreadPoolServer
- Error occurred during processing of m
essage.
org.apache.openjpa.persistence.PersistenceException: No enum constant
org.apache.airavata.model.data.replica.DataProduc
tType.0
at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:1017)
at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:911)
at
org.apache.openjpa.kernel.DelegatingBroker.find(DelegatingBroker.java:231)
at
org.apache.openjpa.persistence.EntityManagerImpl.find(EntityManagerImpl.java:487)
at
org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.lambda$get$2(RepCatAb
stractRepository.java:70)
at
org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.execute(RepCatAbstractRepository.java:119)
at
org.apache.airavata.registry.core.repositories.replicacatalog.RepCatAbstractRepository.get(RepCatAbstractRepository.java:69)
at
org.apache.airavata.registry.core.repositories.replicacatalog.DataProductRepository.getDataProduct(DataProductRepository.java:112)
at
org.apache.airavata.registry.api.service.handler.RegistryServerHandler.getDataProduct(RegistryServerHandler.java:2283)
at
org.apache.airavata.registry.api.RegistryService$Processor$getDataProduct.getResult(RegistryService.java:18799)
at
org.apache.airavata.registry.api.RegistryService$Processor$getDataProduct.getResult(RegistryService.java:18783)
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: java.lang.IllegalArgumentException: No enum constant
org.apache.airavata.model.data.replica.DataProductType.0
at java.lang.Enum.valueOf(Enum.java:238)
at
org.apache.openjpa.jdbc.meta.strats.EnumValueHandler.toObjectValue(EnumValueHandler.java:118)
at
org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.load(HandlerFieldStrategy.java:189)
at org.apache.openjpa.jdbc.meta.FieldMapping.load(FieldMapping.java:928)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1094)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1038)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initializeState(JDBCStoreManager.java:409)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.initialize(JDBCStoreManager.java:304)
at
org.apache.openjpa.kernel.DelegatingStoreManager.initialize(DelegatingStoreManager.java:112)
at
org.apache.openjpa.kernel.ROPStoreManager.initialize(ROPStoreManager.java:57)
at org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:1036)
at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:994)
... 16 common frames omitted
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2812) Cannot create new experiments. Getting error 'Failed to create experiment: Trying to get property of non-object'
[ https://issues.apache.org/jira/browse/AIRAVATA-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505128#comment-16505128 ] ASF subversion and git services commented on AIRAVATA-2812: --- Commit 908471f24974b409f198f6adec1d4b6e4d3673d4 in airavata's branch refs/heads/group-based-auth from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=908471f ] AIRAVATA-2812 Fix mapping of ComputationalResourceSchedulingModel > Cannot create new experiments. Getting error 'Failed to create experiment: > Trying to get property of non-object' > > > Key: AIRAVATA-2812 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2812 > 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-05 at 1.37.12 PM.png > > > When clicked Save and Launch for a new experiment getting error "Failed to > create experiment: Trying to get property of non-object'. But the experiment > record exists in the experiment summary without a compute resource (refer > attachement) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AIRAVATA-2817) Admins need READ and WRITE permission, not just WRITE
[ https://issues.apache.org/jira/browse/AIRAVATA-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie resolved AIRAVATA-2817. --- Resolution: Fixed > Admins need READ and WRITE permission, not just WRITE > - > > Key: AIRAVATA-2817 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2817 > Project: Airavata > Issue Type: Bug >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > > The migration script gives the "Admins" group WRITE permission but they also > explicitly need READ permission. I was thinking that the READ permission > would be implicit but how we've implemented it so far is to grant READ > directly instead of inferring it when a user has WRITE permission. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2800) When user logs in none of the projects are available. Not even the Default Project.
[ https://issues.apache.org/jira/browse/AIRAVATA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505013#comment-16505013 ] Marcus Christie commented on AIRAVATA-2800: --- Projects listing should be fixed now by AIRAVATA-2816. > When user logs in none of the projects are available. Not even the Default > Project. > --- > > Key: AIRAVATA-2800 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2800 > 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.01.36 PM.png, Screen Shot > 2018-06-04 at 10.00.55 AM.png, Screen Shot 2018-06-05 at 10.39.50 AM.png > > > Issue of login in is fixed but now when logged in none of the projects are > available. When tried to view an experiment summary getting ErrorException: > 'Trying to get property of non-object'. Second attachment is the error screen > capture. > > Previous issue details > # Tried to login to PGA with an existing user. > # Getting exception [1] > # Tried to login with recently created user, and getting exception > [2](reported in https://issues.apache.org/jira/browse/AIRAVATA-2797) and then > when refreshed getting [1] > [1] > Error while getting all notifications. More info : null (View: > /var/www/portals/group-based-auth-seagrid/app/views/layout/basic.blade.php) > (View: > /var/www/portals/group-based-auth-seagrid/app/views/layout/basic.blade.php) > [2] > Error while retrieving user resource profile. More info : > getUserResourceProfile failed: unknown result > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AIRAVATA-2800) When user logs in none of the projects are available. Not even the Default Project.
[ https://issues.apache.org/jira/browse/AIRAVATA-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie resolved AIRAVATA-2800. --- Resolution: Fixed > When user logs in none of the projects are available. Not even the Default > Project. > --- > > Key: AIRAVATA-2800 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2800 > 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.01.36 PM.png, Screen Shot > 2018-06-04 at 10.00.55 AM.png, Screen Shot 2018-06-05 at 10.39.50 AM.png > > > Issue of login in is fixed but now when logged in none of the projects are > available. When tried to view an experiment summary getting ErrorException: > 'Trying to get property of non-object'. Second attachment is the error screen > capture. > > Previous issue details > # Tried to login to PGA with an existing user. > # Getting exception [1] > # Tried to login with recently created user, and getting exception > [2](reported in https://issues.apache.org/jira/browse/AIRAVATA-2797) and then > when refreshed getting [1] > [1] > Error while getting all notifications. More info : null (View: > /var/www/portals/group-based-auth-seagrid/app/views/layout/basic.blade.php) > (View: > /var/www/portals/group-based-auth-seagrid/app/views/layout/basic.blade.php) > [2] > Error while retrieving user resource profile. More info : > getUserResourceProfile failed: unknown result > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AIRAVATA-2781) migration script to give Admins READ and WRITE on every 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 READ and WRITE on every 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 Experiment -- 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=16504929#comment-16504929 ] ASF subversion and git services commented on AIRAVATA-2797: --- Commit ba0fb1adfd63b4a0183217171d5488dc274bd53e in airavata's branch refs/heads/group-based-auth from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=ba0fb1a ] AIRAVATA-2797 Fixing UserResourceProfileTest > 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 READ and WRITE on every Experiment
[
https://issues.apache.org/jira/browse/AIRAVATA-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504812#comment-16504812
]
Marcus Christie commented on AIRAVATA-2781:
---
Clean up script to remove sharing Projects with the Admins groups:
{code:sql}
BEGIN;
create table D as (select s.* from SHARING s inner join ENTITY e on e.ENTITY_ID
= s.ENTITY_ID where e.ENTITY_TYPE_ID = 'seagrid:PROJECT' and s.GROUP_ID like
'%Admin_Users%');
delete from SHARING where (ENTITY_ID, DOMAIN_ID, GROUP_ID) in (select
ENTITY_ID, DOMAIN_ID, GROUP_ID from D);
COMMIT;
{code}
> migration script to give Admins READ and WRITE on every 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 Experiment
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRAVATA-2781) migration script to give Admins WRITE on every Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie updated AIRAVATA-2781: -- Summary: migration script to give Admins WRITE on every Experiment (was: migration script to give Admins WRITE on every Project, Experiment) > migration script to give Admins WRITE on every 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-2781) migration script to give Admins WRITE on every Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie updated AIRAVATA-2781: -- Description: * give "Read Only Admins" group READ on every Experiment (was: * give "Read Only Admins" group READ on every Project, Experiment) > migration script to give Admins WRITE on every 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 Experiment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRAVATA-2781) migration script to give Admins READ and WRITE on every Experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie updated AIRAVATA-2781: -- Summary: migration script to give Admins READ and WRITE on every Experiment (was: migration script to give Admins WRITE on every Experiment) > migration script to give Admins READ and WRITE on every 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 Experiment -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2817) Admins need READ and WRITE permission, not just WRITE
[ https://issues.apache.org/jira/browse/AIRAVATA-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504794#comment-16504794 ] ASF subversion and git services commented on AIRAVATA-2817: --- Commit f91e93c454d3b3ec6953295ab10c1fb2dfb3 in airavata's branch refs/heads/group-based-auth from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=f91e93c ] AIRAVATA-2817 AIRAVATA-2781 Give Admins READ as well as WRITE Also removing sharing Projects with Admins groups. > Admins need READ and WRITE permission, not just WRITE > - > > Key: AIRAVATA-2817 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2817 > Project: Airavata > Issue Type: Bug >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > > The migration script gives the "Admins" group WRITE permission but they also > explicitly need READ permission. I was thinking that the READ permission > would be implicit but how we've implemented it so far is to grant READ > directly instead of inferring it when a user has WRITE permission. -- 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=16504795#comment-16504795 ] ASF subversion and git services commented on AIRAVATA-2781: --- Commit f91e93c454d3b3ec6953295ab10c1fb2dfb3 in airavata's branch refs/heads/group-based-auth from [~marcuschristie] [ https://gitbox.apache.org/repos/asf?p=airavata.git;h=f91e93c ] AIRAVATA-2817 AIRAVATA-2781 Give Admins READ as well as WRITE Also removing sharing Projects with Admins groups. > 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] [Assigned] (AIRAVATA-2817) Admins need READ and WRITE permission, not just WRITE
[ https://issues.apache.org/jira/browse/AIRAVATA-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Christie reassigned AIRAVATA-2817: - Assignee: Marcus Christie Description: The migration script gives the "Admins" group WRITE permission but they also explicitly need READ permission. I was thinking that the READ permission would be implicit but how we've implemented it so far is to grant READ directly instead of inferring it when a user has WRITE permission. Issue Type: Bug (was: Story) > Admins need READ and WRITE permission, not just WRITE > - > > Key: AIRAVATA-2817 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2817 > Project: Airavata > Issue Type: Bug >Reporter: Marcus Christie >Assignee: Marcus Christie >Priority: Major > > The migration script gives the "Admins" group WRITE permission but they also > explicitly need READ permission. I was thinking that the READ permission > would be implicit but how we've implemented it so far is to grant READ > directly instead of inferring it when a user has WRITE permission. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRAVATA-2817) Admins need READ and WRITE permission, not just WRITE
Marcus Christie created AIRAVATA-2817: - Summary: Admins need READ and WRITE permission, not just WRITE Key: AIRAVATA-2817 URL: https://issues.apache.org/jira/browse/AIRAVATA-2817 Project: Airavata Issue Type: Story Reporter: Marcus Christie -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (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 resolved AIRAVATA-2816. --- Resolution: Fixed > 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] [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=16504751#comment-16504751 ] Marcus Christie commented on AIRAVATA-2781: --- I'm rethinking whether to give Admins, Read Only Admins WRITE/READ on Projects. We don't currently have this functionality and it bloats the project list for admin users. I'm thinking about removing this for now and only adding it when it is needed. > 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] [Reopened] (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 reopened AIRAVATA-2781: --- > 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)
