[jira] [Resolved] (AIRAVATA-2023) In SciGaP portal for new gateway owners should not display experiment, project, storage menus
[ https://issues.apache.org/jira/browse/AIRAVATA-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2023. Resolution: Fixed > In SciGaP portal for new gateway owners should not display experiment, > project, storage menus > - > > Key: AIRAVATA-2023 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2023 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT >Reporter: Eroma >Assignee: Nipurn Doshi > > When a new gateway owner (who has a new gateway request in pending) logs in > can see Project, Experiment and Storage menus. > These should not be accessible or available for the new users. Unlike SciGaP > admins they might try them out -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2046) SciGaP admins should be able to edit the gateway request
[ https://issues.apache.org/jira/browse/AIRAVATA-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2046. Resolution: Fixed > SciGaP admins should be able to edit the gateway request > > > Key: AIRAVATA-2046 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2046 > Project: Airavata > Issue Type: New Feature > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT >Reporter: Eroma >Assignee: Nipurn Doshi > > Currently the gateway request is only displayed to the SciGaP admins. They > should be able to edit the request. > Because; > 1. User given portal URL could be already active and running. > 2. If they have added some info which will generate errors in IS it need to > be changed > 3. WE might need to change the details they have given to make public > When editing the request admin should only be able to edit requests which are > not APPROVED, CANCELLED or DENIED. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2153) Added comment to Gateway request is not available when the record is viewed again
[ https://issues.apache.org/jira/browse/AIRAVATA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2153. Resolution: Fixed > Added comment to Gateway request is not available when the record is viewed > again > - > > Key: AIRAVATA-2153 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2153 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi > > Added comment to Gateway request is not available when the record is viewed > again. > SciGaP admin viewed a gateway request and then added a comment and clicked > update gateway. > 1. When SciGaP admin viewed the comment again it is not displayed in comment > section. > 2. In DB table 'GATEWAY' the added comment is saved in 'DECLINED_REASON'. > 3. Only added a comment and already the status in GATEWAY table is APPROVED. > 4. For the gateway requested PI the status is showed as APPROVED. Added > comments are displayed there as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2238) Deactivate Gateway button should only appear for gateways APPROVED and ACTIVE
[ https://issues.apache.org/jira/browse/AIRAVATA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2238. Resolution: Fixed > Deactivate Gateway button should only appear for gateways APPROVED and ACTIVE > - > > Key: AIRAVATA-2238 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2238 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi > > Currently even for requests with REQUESTED state the button appears. > This comes when the record is updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-2238) Deactivate Gateway button should only appear for gateways APPROVED and ACTIVE
[ https://issues.apache.org/jira/browse/AIRAVATA-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711013#comment-15711013 ] Nipurn Doshi commented on AIRAVATA-2238: This bug has been fixed in Develop branch. > Deactivate Gateway button should only appear for gateways APPROVED and ACTIVE > - > > Key: AIRAVATA-2238 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2238 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi > > Currently even for requests with REQUESTED state the button appears. > This comes when the record is updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2153) Added comment to Gateway request is not available when the record is viewed again
[ https://issues.apache.org/jira/browse/AIRAVATA-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2153. Resolution: Fixed > Added comment to Gateway request is not available when the record is viewed > again > - > > Key: AIRAVATA-2153 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2153 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi > > Added comment to Gateway request is not available when the record is viewed > again. > SciGaP admin viewed a gateway request and then added a comment and clicked > update gateway. > 1. When SciGaP admin viewed the comment again it is not displayed in comment > section. > 2. In DB table 'GATEWAY' the added comment is saved in 'DECLINED_REASON'. > 3. Only added a comment and already the status in GATEWAY table is APPROVED. > 4. For the gateway requested PI the status is showed as APPROVED. Added > comments are displayed there as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2155) 'Deactivate Gateway' button should exists only for gateway requests which are approved.
[ https://issues.apache.org/jira/browse/AIRAVATA-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2155. Resolution: Fixed > 'Deactivate Gateway' button should exists only for gateway requests which are > approved. > --- > > Key: AIRAVATA-2155 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2155 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Reporter: Eroma >Assignee: Nipurn Doshi > > 'Deactivate Gateway' button should exists only for gateway requests which are > approved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2029) Display gateway request creation date time for both gateway owner and SciGaP admin
[ https://issues.apache.org/jira/browse/AIRAVATA-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2029. Resolution: Fixed > Display gateway request creation date time for both gateway owner and SciGaP > admin > -- > > Key: AIRAVATA-2029 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2029 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: https://dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi > > Creation time exists in the DB table. Lets display the request creation time > and date to both request owner and SciGaP admins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2032) In PGA --> Admin Dashboard --> Experiment Statistics page cannot close the tabs opened due to searching experiments
[ https://issues.apache.org/jira/browse/AIRAVATA-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2032. Resolution: Fixed > In PGA --> Admin Dashboard --> Experiment Statistics page cannot close the > tabs opened due to searching experiments > --- > > Key: AIRAVATA-2032 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2032 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Reporter: Eroma >Assignee: Nipurn Doshi > > Gateway admin can search for specific experiment by giving the experiment ID > in above path. > When searched for an experiment, details open in a new tab. > for each experiment ID searched a new tab will open (which is OK) > But we need to give close button for each of these tabs. No way of closing > them currently -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1871) Currently gateway admins see all the roles in PGA; Some meaningless at gateway level for gateway admins. Exists due to IS requirements.
[ https://issues.apache.org/jira/browse/AIRAVATA-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1871. Resolution: Fixed > Currently gateway admins see all the roles in PGA; Some meaningless at > gateway level for gateway admins. Exists due to IS requirements. > --- > > Key: AIRAVATA-1871 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1871 > Project: Airavata > Issue Type: Sub-task > Components: PGA PHP Web Gateway >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.17-SNAPSHOT > > > For gateway admins please display user roles which are meaningful and also at > the same level or below gateway admin level in the user hierarchy. Currently > they see all the roles available in WSO2 IS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2088) In 'View Credential' please provide the gateway URL as well.
[ https://issues.apache.org/jira/browse/AIRAVATA-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2088. Resolution: Fixed > In 'View Credential' please provide the gateway URL as well. > > > Key: AIRAVATA-2088 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2088 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT >Reporter: Eroma >Assignee: Nipurn Doshi > > Currently we show gateway ID but not the URL. Since gateway provider cannot > view the gateway URL in the request record as well we should provide it in > View Credentials. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2045) When didnt add http:// in the domain and URL it is not detected and also the gateway is not added to IS
[ https://issues.apache.org/jira/browse/AIRAVATA-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2045. Resolution: Fixed > When didnt add http:// in the domain and URL it is not detected and also the > gateway is not added to IS > > > Key: AIRAVATA-2045 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2045 > Project: Airavata > Issue Type: Bug >Reporter: Eroma >Assignee: Nipurn Doshi > > When didnt add 'http:/'/ in the domain and URL it is not detected and also > the gateway is not added to IS. > Gave below for gateway domain and gateway URL > domain: http:science.org > gateway URL: http:my.science.org > And when the request is submitted I APPROVED as scigap admin. > Now for longtime i see the pop up with message 'Adding tenant for GatewayId: > MyScience. Please do not refresh or close this page!' > Seems like issues in adding the gateway in IS. > 1. If there are any issues adding the gateway in IS it should be returned and > displayed to scigap admin. > Should not hang like it does now -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2044) Gateway request owner cancelled the request, still the cancelled gateway appeared in 'Approved Gateways' tab
[ https://issues.apache.org/jira/browse/AIRAVATA-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2044. Resolution: Fixed > Gateway request owner cancelled the request, still the cancelled gateway > appeared in 'Approved Gateways' tab > > > Key: AIRAVATA-2044 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2044 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: https://dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2047) When creating the new gateway from gateway request the domain should not be added as part of the username
[ https://issues.apache.org/jira/browse/AIRAVATA-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2047. Resolution: Fixed > When creating the new gateway from gateway request the domain should not be > added as part of the username > - > > Key: AIRAVATA-2047 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2047 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: https://dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi > > When creating a gateway request added below details > admin username: PhyGateway6 > domain: medresearch.org > gateway URL: portal.medical.org > in IS tenant details it shows > admin username: phygatew...@medresearch.org > domain: portal.medical.org > username should not carry the parts after given username (@medresearch.org) > and gateway URL added as the domain -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2074) Newly created gateway request cannot be viewed by the owner.
[ https://issues.apache.org/jira/browse/AIRAVATA-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2074. Resolution: Fixed > Newly created gateway request cannot be viewed by the owner. > > > Key: AIRAVATA-2074 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2074 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: dev.seagrid.org >Reporter: Eroma >Assignee: Nipurn Doshi > > Because the user cannot view the request > 1. He cannot cancel it. > 2. When the gateway request is completed cannot view credentials as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2033) Add new Gateway link in Gateway Profile gives error 'Required field 'gatewayApprovalStatus' is unset!'
[ https://issues.apache.org/jira/browse/AIRAVATA-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2033. Resolution: Fixed > Add new Gateway link in Gateway Profile gives error 'Required field > 'gatewayApprovalStatus' is unset!' > -- > > Key: AIRAVATA-2033 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2033 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT >Reporter: Eroma >Assignee: Nipurn Doshi > > As a SciGaP admin has the option of adding a gateway using the button in > Gateway Profile. When clicked 'Register' gives error > 'Required field 'gatewayApprovalStatus' is unset! > Struct:Gateway(gatewayId:Test Chem Gateway1, gatewayApprovalStatus:null, > gatewayName:Test Chem Gateway1, domain:chem.airavata, > emailAddress:eroma.abeysin...@gmail.com)' > Seems like status is not set when tried to add from here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2034) New account creation confirmation fails in dev.scigap.org with error message 'Unable to Connect to the Airavata Server Instance!'
[ https://issues.apache.org/jira/browse/AIRAVATA-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2034. Resolution: Fixed > New account creation confirmation fails in dev.scigap.org with error message > 'Unable to Connect to the Airavata Server Instance!' > - > > Key: AIRAVATA-2034 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2034 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: https://dev.scigap.org/ >Reporter: Eroma >Assignee: Nipurn Doshi > Attachments: Screen Shot 2016-08-10 at 2.32.35 PM.png, Screen Shot > 2016-08-11 at 10.40.50 AM.png > > > When I entered username and password to confirm an account creation in > getting 'Unable to Connect to the Airavata Server Instance!' > But the airavata server is running and was able to successfully confirm > account creation in a different gateway connecting to same airavata server. > Also can successfully login with existing users as well. getting this message > only when tried to confirm new account creation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15423355#comment-15423355 ] Nipurn Doshi commented on AIRAVATA-2041: searching for experiment ids which do not exist used to be working fine. This issue seems to be coming from Airavata from getExperiment() method > 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: Nipurn Doshi > > 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] [Resolved] (AIRAVATA-2043) When cancelled a Application Module update and click on 'Create a new Application Module' opens the previously cancelled module details
[ https://issues.apache.org/jira/browse/AIRAVATA-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2043. Resolution: Fixed > When cancelled a Application Module update and click on 'Create a new > Application Module' opens the previously cancelled module details > --- > > Key: AIRAVATA-2043 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2043 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Nipurn Doshi > > Steps taken, > 1. Open an existing application module in edit mode > 2. edit current data but without updating click cancel > 3. Click 'Create a new Application Module' > 4. Instead of empty pop up screen it opens the previous application module > screen with data. > 5. When clicked 'Creat another new application module get created with sane > info as the module before. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2025) When clicked 'Approved' for a gateway request error exception thrown
[ https://issues.apache.org/jira/browse/AIRAVATA-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2025. Resolution: Fixed > When clicked 'Approved' for a gateway request error exception thrown > > > Key: AIRAVATA-2025 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2025 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.17-SNAPSHOT >Reporter: Eroma >Assignee: Nipurn Doshi > Attachments: Screen Shot 2016-08-08 at 12.23.48 AM.png > > > When clicked 'Approved' error exception thrown. This should be handled. If > the domain needs an extension we need to enforce at request creation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-2003) When SciGaP admin click 'APPROVE' for a new gateway page crashes.
[ https://issues.apache.org/jira/browse/AIRAVATA-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-2003. Resolution: Fixed > When SciGaP admin click 'APPROVE' for a new gateway page crashes. > - > > Key: AIRAVATA-2003 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2003 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.17-SNAPSHOT > > > When clicked on APPROVE for a new gateway in Gateway profile page crashed > with errors > SoapFault > You should have an extension to your domain. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AIRAVATA-1996) User account confirmation fails
[ https://issues.apache.org/jira/browse/AIRAVATA-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi closed AIRAVATA-1996. -- Resolution: Fixed > User account confirmation fails > --- > > Key: AIRAVATA-1996 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1996 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Nipurn Doshi > Attachments: Screen Shot 2016-07-13 at 1.07.34 AM.png > > > When clicked the link in mail to confirm the account creation after giving > login credentials exception thrown > User is not authenticated or authorized. > Please check -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1994) Cannot open the Gateway Profile in Production PGAs
[ https://issues.apache.org/jira/browse/AIRAVATA-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1994. Resolution: Fixed > Cannot open the Gateway Profile in Production PGAs > -- > > Key: AIRAVATA-1994 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1994 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > When clicked to open Gateway Profile page in Admin Dashboard it takes such a > long time and in the end error message appears. > 'Whoops, looks like something went wrong.' > in dev PGAs the issue is not existing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1887) Fixes to 'Detailed Experiment Information' in Admin Dashboard
[ https://issues.apache.org/jira/browse/AIRAVATA-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15271365#comment-15271365 ] Nipurn Doshi commented on AIRAVATA-1887: This order comes from tasks list inside process object of getDetailedExperimentTree() Airavata API and there is no way to know how to sort the tasks in the frontend. > Fixes to 'Detailed Experiment Information' in Admin Dashboard > - > > Key: AIRAVATA-1887 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1887 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://testdrive.airavata.org/ >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > Fix in Admin Dashboard --> Experiment Statistics --> Detail Experiment > Information; > 1. Remove 'Jobs:' indication in tasks except for Job Submission task > 2. Display the Job ID in Job Submission task > 3. Display errors at task levels > 4. Order the tasks in correct order. Currently the Env set up is at the > bottom. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1934) SEAGrid Client Opening page
[ https://issues.apache.org/jira/browse/AIRAVATA-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1934. Resolution: Fixed > SEAGrid Client Opening page > --- > > Key: AIRAVATA-1934 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1934 > Project: Airavata > Issue Type: Bug >Reporter: Sudhakar Pamidighantam >Assignee: Nipurn Doshi > Fix For: 0.16 > > > SEAGrid Opening page should have a Welcome message and a place to show > notices (MOTD) along with the login options. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1934) SEAGrid Client Opening page
[ https://issues.apache.org/jira/browse/AIRAVATA-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15271346#comment-15271346 ] Nipurn Doshi commented on AIRAVATA-1934: Notification system has been implemented. I'm resolving this. > SEAGrid Client Opening page > --- > > Key: AIRAVATA-1934 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1934 > Project: Airavata > Issue Type: Bug >Reporter: Sudhakar Pamidighantam >Assignee: Nipurn Doshi > Fix For: 0.16 > > > SEAGrid Opening page should have a Welcome message and a place to show > notices (MOTD) along with the login options. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1952) When a deployment is no longer existing in a certain resource clone experiment launch crashes with error-exception
[ https://issues.apache.org/jira/browse/AIRAVATA-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1952. Resolution: Fixed > When a deployment is no longer existing in a certain resource clone > experiment launch crashes with error-exception > -- > > Key: AIRAVATA-1952 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1952 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > Attachments: Screen Shot 2016-04-13 at 4.26.11 PM.png > > > When a deployment is no longer existing in a certain resource clone > experiment launch crashes with error-exception > Steps > 1. Selected an old experiment > 2. Cloned and changed the queue > 3. Clicked launch > 4. Gives the attached error. > This was because in the present the application is not deployed anywhere. In > cases like this cloning should be restricted or handled with a proper message > to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1926) In both SEAGrid desktop client and PGA web client make project non-editable when editing and cloning
[ https://issues.apache.org/jira/browse/AIRAVATA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1926. Resolution: Fixed Project can be changed for an experiment now only on first time experiment creation. Not afterwards. > In both SEAGrid desktop client and PGA web client make project non-editable > when editing and cloning > - > > Key: AIRAVATA-1926 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1926 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.seagrid.org and SEAGrid desktop client >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > Currently the project can be changed in both edit and cloning. > But since we create the storage folder using project of the experiment moving > an experiment from one project to another makes errors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1951) When editing an already created experiment prompts it needs input files. When they were already attached and available in create experiment
[ https://issues.apache.org/jira/browse/AIRAVATA-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1951. Resolution: Fixed > When editing an already created experiment prompts it needs input files. When > they were already attached and available in create experiment > --- > > Key: AIRAVATA-1951 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1951 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.seagrid.org >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > In 'edit Experiment' page it keep asking for input files when tried to save > and launch. But files are already existing as they were attached at initial > experiment creation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1887) Fixes to 'Detailed Experiment Information' in Admin Dashboard
[ https://issues.apache.org/jira/browse/AIRAVATA-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1887. Resolution: Fixed > Fixes to 'Detailed Experiment Information' in Admin Dashboard > - > > Key: AIRAVATA-1887 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1887 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://testdrive.airavata.org/ >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > Fix in Admin Dashboard --> Experiment Statistics --> Detail Experiment > Information; > 1. Remove 'Jobs:' indication in tasks except for Job Submission task > 2. Display the Job ID in Job Submission task > 3. Display errors at task levels > 4. Order the tasks in correct order. Currently the Env set up is at the > bottom. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1910) Button to add input files in Create Experiment is not clickable when opened in Chrome
[ https://issues.apache.org/jira/browse/AIRAVATA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226661#comment-15226661 ] Nipurn Doshi commented on AIRAVATA-1910: This commit was actually meant for AIRAVATA-1926. Please ignore. > Button to add input files in Create Experiment is not clickable when opened > in Chrome > -- > > Key: AIRAVATA-1910 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1910 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: All PGA instances has this >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > When PGA is open in Chrome browser; > 1. Open Create experiment > 2. Select project and application > 3. Click Continue > 4. Click 'Choose File' to add inputs > 5. Button does not work. > 6. This only happens in Chrome browser; works fine in Firefox and Safari -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1926) In both SEAGrid desktop client and PGA web client make project non-editable when editing and cloning
[ https://issues.apache.org/jira/browse/AIRAVATA-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226656#comment-15226656 ] Nipurn Doshi commented on AIRAVATA-1926: I have made these changes on PGA end as well (develop branch). [~eroma_a] could you do some simple tests to check, whether this change breaks any other usecases of Experiment creation. > In both SEAGrid desktop client and PGA web client make project non-editable > when editing and cloning > - > > Key: AIRAVATA-1926 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1926 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.seagrid.org and SEAGrid desktop client >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > Currently the project can be changed in both edit and cloning. > But since we create the storage folder using project of the experiment moving > an experiment from one project to another makes errors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (AIRAVATA-1910) Button to add input files in Create Experiment is not clickable when opened in Chrome
[ https://issues.apache.org/jira/browse/AIRAVATA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi updated AIRAVATA-1910: --- Comment: was deleted (was: I have made these changes on PGA end as well (develop branch). [~eroma_a] could you do some simple tests to check, whether this change breaks any other usecases of Experiment creation.) > Button to add input files in Create Experiment is not clickable when opened > in Chrome > -- > > Key: AIRAVATA-1910 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1910 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: All PGA instances has this >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > When PGA is open in Chrome browser; > 1. Open Create experiment > 2. Select project and application > 3. Click Continue > 4. Click 'Choose File' to add inputs > 5. Button does not work. > 6. This only happens in Chrome browser; works fine in Firefox and Safari -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1910) Button to add input files in Create Experiment is not clickable when opened in Chrome
[ https://issues.apache.org/jira/browse/AIRAVATA-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226629#comment-15226629 ] Nipurn Doshi commented on AIRAVATA-1910: I have made these changes on PGA end as well (develop branch). [~eroma_a] could you do some simple tests to check, whether this change breaks any other usecases of Experiment creation. > Button to add input files in Create Experiment is not clickable when opened > in Chrome > -- > > Key: AIRAVATA-1910 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1910 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: All PGA instances has this >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > When PGA is open in Chrome browser; > 1. Open Create experiment > 2. Select project and application > 3. Click Continue > 4. Click 'Choose File' to add inputs > 5. Button does not work. > 6. This only happens in Chrome browser; works fine in Firefox and Safari -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1911) Clicking on Stats icon on one Experiment Statistics UI loads Experiment Statistics in 3 tabs.
[ https://issues.apache.org/jira/browse/AIRAVATA-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1911. Resolution: Fixed > Clicking on Stats icon on one Experiment Statistics UI loads Experiment > Statistics in 3 tabs. > -- > > Key: AIRAVATA-1911 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1911 > Project: Airavata > Issue Type: Bug >Reporter: Nipurn Doshi >Assignee: Nipurn Doshi > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1948) Replace Experiment summary with Detail
[ https://issues.apache.org/jira/browse/AIRAVATA-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15226467#comment-15226467 ] Nipurn Doshi commented on AIRAVATA-1948: So in Experiments' context, do we want all user types be able to see a detailed view? > Replace Experiment summary with Detail > -- > > Key: AIRAVATA-1948 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1948 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway >Reporter: Suresh Marru >Assignee: Nipurn Doshi > > Since Experiment Summary only pulls one experiment at a time, it make sense > to directly show the full experiment detail instead of the summary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1946) Search in gateway preference page to search for gateways is not working in scigap portal
[ https://issues.apache.org/jira/browse/AIRAVATA-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1946. Resolution: Fixed > Search in gateway preference page to search for gateways is not working in > scigap portal > > > Key: AIRAVATA-1946 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1946 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > In Admin Dashboard path https://dev.scigap.org/admin/dashboard/gateway > search for gateways is not working. > it does not retrieve any values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1938) In gateway preference page when CS token is not set at compute resource preference level still it appears as if it is allocated.
[ https://issues.apache.org/jira/browse/AIRAVATA-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1938. Resolution: Fixed > In gateway preference page when CS token is not set at compute resource > preference level still it appears as if it is allocated. > > > Key: AIRAVATA-1938 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1938 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.scigap.org >Reporter: Eroma >Assignee: Nipurn Doshi >Priority: Minor > Fix For: 0.16 > > Attachments: Screen Shot 2016-03-22 at 2.06.16 PM.png > > > Please see the attached image. even when the CS token is not assigned at > compute resource level it is indicated with a mark. When CS token is not > assigned at compute resource level display 'NOT-SET' as the value for the > field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1760) In PGA date selection fields; popped up calendar should disappear when user selects a Date
[ https://issues.apache.org/jira/browse/AIRAVATA-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1760. Resolution: Fixed > In PGA date selection fields; popped up calendar should disappear when user > selects a Date > > > Key: AIRAVATA-1760 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1760 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.15 > Environment: http://test-drive.airavata.org/pga/public >Reporter: Eroma >Assignee: Nipurn Doshi >Priority: Minor > Fix For: 0.16 > > > Currently when a date is selected from the pop up calendar it stays. User has > ti click on a different place in the UI make it go away. > Ideally when the user selects a date and it appears in the field the calendar > should go away -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1847) Airavata Logo Drafts
[ https://issues.apache.org/jira/browse/AIRAVATA-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15203604#comment-15203604 ] Nipurn Doshi commented on AIRAVATA-1847: Thanks for the feedback Suresh. We'll try something on the lines of what you suggested. > Airavata Logo Drafts > > > Key: AIRAVATA-1847 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1847 > Project: Airavata > Issue Type: New Feature >Reporter: Blair Carlisle > Attachments: Airavata Logos - By Shivika.pdf, Airavata.pdf, airavata > branding 2.pdf > > > See the PDF below to view options for the new Airavata logo. Comments welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1917) Change the message displayed for new users, when logged into PGA to confirm account creation
[ https://issues.apache.org/jira/browse/AIRAVATA-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1917. Resolution: Fixed > Change the message displayed for new users, when logged into PGA to confirm > account creation > > > Key: AIRAVATA-1917 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1917 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://seagrid.org >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > Change the message displayed for new users, when logged into PGA to confirm > account creation > Currently when logged in, in order to confirm the account creation displays; > > Hi! You look new here. > Please contact the gateway administrator to request access to run experiments > and more. > > User does not need to contact admin as information will be notified to admin > through mail. If admin wants more details he can send an email to the user. > Message should be something like; > > Hi! You look new here. > You will be notified via email by your gateway admin when you are provided > access to the gateway to run experiments. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AIRAVATA-1911) Clicking on Stats icon on one Experiment Statistics UI loads Experiment Statistics in 3 tabs.
Nipurn Doshi created AIRAVATA-1911: -- Summary: Clicking on Stats icon on one Experiment Statistics UI loads Experiment Statistics in 3 tabs. Key: AIRAVATA-1911 URL: https://issues.apache.org/jira/browse/AIRAVATA-1911 Project: Airavata Issue Type: Bug Reporter: Nipurn Doshi Assignee: Nipurn Doshi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1898) When normal gateway user logs in for the first time after account activation message' 'You need to be an admin to use this service.' is displayed
[ https://issues.apache.org/jira/browse/AIRAVATA-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1898. Resolution: Fixed > When normal gateway user logs in for the first time after account activation > message' 'You need to be an admin to use this service.' is displayed > - > > Key: AIRAVATA-1898 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1898 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway > Environment: dev.seagrid and dev.testdrive >Reporter: Eroma >Assignee: Nipurn Doshi > > This message is wrong to display. This should be removed as it is misleading > the user. Because although the message is displayed he can carry out using > features intended for him -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-1847) Airavata Logo Drafts
[ https://issues.apache.org/jira/browse/AIRAVATA-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi updated AIRAVATA-1847: --- Attachment: airavata branding 2.pdf Shivika and I have created a second set of proposed Airavata Logo(Attached PDF, 'airavata branding 2.pdf' ). Please comment with your suggestions, feedback and choices. Thanks! > Airavata Logo Drafts > > > Key: AIRAVATA-1847 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1847 > Project: Airavata > Issue Type: New Feature >Reporter: Blair Carlisle > Attachments: Airavata Logos - By Shivika.pdf, Airavata.pdf, airavata > branding 2.pdf > > > See the PDF below to view options for the new Airavata logo. Comments welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1908) Bottom green boarder of Create Experiment page is shifted when opened from FireFox
[ https://issues.apache.org/jira/browse/AIRAVATA-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1908. Resolution: Fixed > Bottom green boarder of Create Experiment page is shifted when opened from > FireFox > -- > > Key: AIRAVATA-1908 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1908 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Affects Versions: 0.16 >Reporter: Eroma > Fix For: 0.16 > > > When PGA is opened in Firefox browser the bottom borderline shifts in Create > experiment page. This is a browser specific look and feel improvement. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (AIRAVATA-1877) When a session time outs while a user is working (adding a app deployment. etc...) use should be able to log in and continue from where he stopped
[ https://issues.apache.org/jira/browse/AIRAVATA-1877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi reassigned AIRAVATA-1877: -- Assignee: Supun Chathuranga Nakandala (was: Nipurn Doshi) > When a session time outs while a user is working (adding a app deployment. > etc...) use should be able to log in and continue from where he stopped > -- > > Key: AIRAVATA-1877 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1877 > Project: Airavata > Issue Type: Improvement > Components: PGA PHP Web Gateway >Reporter: Eroma >Assignee: Supun Chathuranga Nakandala > > Currently if user is in middle of adding n application deployment, compute > resource is PGA session time outs the work done is lost when logged in again. > User should be able to continue from where he stopped. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1878) Adding App Module and Deployment pages closes if user clicks outside background page
[ https://issues.apache.org/jira/browse/AIRAVATA-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15051587#comment-15051587 ] Nipurn Doshi commented on AIRAVATA-1878: Deployment and Module popup/modal forms have been made similar to Interface popup forms. Now they do not close on clicking outside the form. User has to manually cancel or close it. > Adding App Module and Deployment pages closes if user clicks outside > background page > > > Key: AIRAVATA-1878 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1878 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Reporter: Eroma >Assignee: Nipurn Doshi > > While adding application module or application deployment if user > accidentally clicks the background UI the 'Create Application Module' or > 'Create Application Deployment' pages will be closed. No confirmation message > is given for user to respond. > But in Adding Application Interface popup screen clicking in the background > UI doesn't do such -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1878) Adding App Module and Deployment pages closes if user clicks outside background page
[ https://issues.apache.org/jira/browse/AIRAVATA-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1878. Resolution: Fixed > Adding App Module and Deployment pages closes if user clicks outside > background page > > > Key: AIRAVATA-1878 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1878 > Project: Airavata > Issue Type: Bug > Components: PGA PHP Web Gateway >Reporter: Eroma >Assignee: Nipurn Doshi > > While adding application module or application deployment if user > accidentally clicks the background UI the 'Create Application Module' or > 'Create Application Deployment' pages will be closed. No confirmation message > is given for user to respond. > But in Adding Application Interface popup screen clicking in the background > UI doesn't do such -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AIRAVATA-1847) Airavata Logo Drafts
[ https://issues.apache.org/jira/browse/AIRAVATA-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi updated AIRAVATA-1847: --- Attachment: Airavata Logos - By Shivika.pdf Hi Everyone, I am uploding another set of logo proposal contributed by Shivika Thapar. Please have a look and comment! > Airavata Logo Drafts > > > Key: AIRAVATA-1847 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1847 > Project: Airavata > Issue Type: New Feature >Reporter: Blair Carlisle > Attachments: Airavata Logos - By Shivika.pdf, Airavata.pdf > > > See the PDF below to view options for the new Airavata logo. Comments welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1853) New validations to PGA user account password
[ https://issues.apache.org/jira/browse/AIRAVATA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1853. Resolution: Fixed > New validations to PGA user account password > > > Key: AIRAVATA-1853 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1853 > Project: Airavata > Issue Type: Task > Components: PGA PHP Web Gateway >Affects Versions: 0.16 > Environment: https://dev.testdrive.airavata.org/portal/master/public/ >Reporter: Eroma >Assignee: Nipurn Doshi > Fix For: 0.16 > > > With the account verification step added according to the IS requirements > there are extra validations required for the user password at account > creation. > Please add > Password should contain a digit[0-9] > A lower case letter[a-z] > An upper case letter[A-Z] > One of !@#$%&* characters -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1847) Airavata Logo Drafts
[ https://issues.apache.org/jira/browse/AIRAVATA-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14940354#comment-14940354 ] Nipurn Doshi commented on AIRAVATA-1847: In the first look - - Like Eroma, I also like the previous simpler single-headed elephant's logo more over the three-headed versions because of simplicity. - i am not inclined towards having black color on the logo, mainly because to me it doesn't represent an opensource foundationn. It suits more to a stylish/classy brand like a car or a watch company, but that is just my opinion. - I like the use of font in 'APACHE AIRAVATA' in the three-headed RED logo. - I don't know why, but the three-headed logos with trunks in the same direction do not resonate with me. Can we get an explanation behind the making of the logos to get a deeper understanding about them of why they are the way they are? - I'm not a graphic designer and I understand very little about philosophy of logo design, but I have a couple of suggestions that I would like to add with examples that we can try if we have time - We could try flat colors used now-a-days like - http://www.flatuicolorpicker.com/ We could try giving a material feel to the logo like this one - https://cdn.colorlib.com/wp/wp-content/uploads/sites/2/2013/10/hudddle-logo.png --- > Airavata Logo Drafts > > > Key: AIRAVATA-1847 > URL: https://issues.apache.org/jira/browse/AIRAVATA-1847 > Project: Airavata > Issue Type: New Feature >Reporter: Blair Carlisle > Attachments: Airavata.pdf > > > See the PDF below to view options for the new Airavata logo. Comments welcome. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1702) Data in Browse Compute Resource page in dev-pga is right aligned and not centered. Please correct the alignment
[ https://issues.apache.org/jira/browse/AIRAVATA-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1702. Resolution: Fixed Data in Browse Compute Resource page in dev-pga is right aligned and not centered. Please correct the alignment Key: AIRAVATA-1702 URL: https://issues.apache.org/jira/browse/AIRAVATA-1702 Project: Airavata Issue Type: Bug Components: PGA PHP Web Gateway Affects Versions: 0.15 Environment: http://dev.test-drive.airavata.org/portal/pga/public/cr/browse Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2015-05-13 at 11.30.50 AM.png Screen shot attached Navigation: Compute Resource -- Browse -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AIRAVATA-1695) Change queue selection as a dropdown while creating experiments based on selected compute resource
Nipurn Doshi created AIRAVATA-1695: -- Summary: Change queue selection as a dropdown while creating experiments based on selected compute resource Key: AIRAVATA-1695 URL: https://issues.apache.org/jira/browse/AIRAVATA-1695 Project: Airavata Issue Type: Bug Reporter: Nipurn Doshi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AIRAVATA-1507) WRF experiment creation fails (Both manual execution and through Selenium script)
[ https://issues.apache.org/jira/browse/AIRAVATA-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi closed AIRAVATA-1507. -- Resolution: Fixed WRF experiment creation fails (Both manual execution and through Selenium script) - Key: AIRAVATA-1507 URL: https://issues.apache.org/jira/browse/AIRAVATA-1507 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-11-05 at 4.35.49 PM.png Navigation Experiment -- Create Experiment Entered all the input fields and attached the files and clicked on Continue Gives the attached error screen (Same result when tried it manually or through Selenium Tool) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AIRAVATA-1613) Cannot create an experiment on dev.test-drive
[ https://issues.apache.org/jira/browse/AIRAVATA-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi closed AIRAVATA-1613. -- Resolution: Fixed Cannot create an experiment on dev.test-drive - Key: AIRAVATA-1613 URL: https://issues.apache.org/jira/browse/AIRAVATA-1613 Project: Airavata Issue Type: Bug Environment: interface: web; browser: chrome 40.0.2214.115 (64-bit); os: Linux; Reporter: Shahbaz Memon Assignee: Nipurn Doshi Continue at the Create a new Experiment page leads to the following error, ErrorException thrown with message TSocket read 0 bytes (View: /var/www/html/pga/app/views/experiment/create-complete.blade.php) Stacktrace: #28 ErrorException in /var/www/html/pga/vendor/apache/thrift/lib/php/lib/Thrift/Transport/TSocket.php:269 #27 Illuminate\View\Engines\CompilerEngine:handleViewException in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php:41 #26 Thrift\Exception\TTransportException in /var/www/html/pga/vendor/apache/thrift/lib/php/lib/Thrift/Transport/TSocket.php:269 #25 Thrift\Transport\TSocket:read in /var/www/html/pga/vendor/apache/thrift/lib/php/lib/Thrift/Transport/TTransport.php:74 #24 Thrift\Transport\TTransport:readAll in /var/www/html/pga/vendor/apache/thrift/lib/php/lib/Thrift/Protocol/TBinaryProtocol.php:305 #23 Thrift\Protocol\TBinaryProtocol:readI32 in /var/www/html/pga/vendor/apache/thrift/lib/php/lib/Thrift/Protocol/TBinaryProtocol.php:197 #22 Thrift\Protocol\TBinaryProtocol:readMessageBegin in /var/www/html/pga/app/libraries/Airavata/API/Airavata.php:3013 #21 Airavata\API\AiravataClient:recv_getAvailableAppInterfaceComputeResources in /var/www/html/pga/app/libraries/Airavata/API/Airavata.php:2982 #20 Airavata\API\AiravataClient:getAvailableAppInterfaceComputeResources in /var/www/html/pga/app/libraries/utilities.php:453 #19 Utilities:get_available_app_interface_compute_resources in /var/www/html/pga/app/libraries/utilities.php:1252 #18 Utilities:create_compute_resources_select in /var/www/html/pga/app/storage/views/940d078e435420273432848fbbabae24:46 #17 include in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php:37 #16 Illuminate\View\Engines\PhpEngine:evaluatePath in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.php:56 #15 Illuminate\View\Engines\CompilerEngine:get in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/View.php:134 #14 Illuminate\View\View:getContents in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/View.php:102 #13 Illuminate\View\View:renderContents in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/View.php:76 #12 Illuminate\View\View:render in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Http/Response.php:43 #11 Illuminate\Http\Response:setContent in /var/www/html/pga/vendor/symfony/http-foundation/Symfony/Component/HttpFoundation/Response.php:202 #10 Symfony\Component\HttpFoundation\Response:__construct in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Routing/Router.php:1496 #9 Illuminate\Routing\Router:prepareResponse in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Routing/Router.php:1031 #8 Illuminate\Routing\Router:dispatchToRoute in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Routing/Router.php:996 #7 Illuminate\Routing\Router:dispatch in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:775 #6 Illuminate\Foundation\Application:dispatch in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:745 #5 Illuminate\Foundation\Application:handle in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Session/Middleware.php:72 #4 Illuminate\Session\Middleware:handle in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Cookie/Queue.php:47 #3 Illuminate\Cookie\Queue:handle in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Cookie/Guard.php:51 #2 Illuminate\Cookie\Guard:handle in /var/www/html/pga/vendor/stack/builder/src/Stack/StackedHttpKernel.php:23 #1 Stack\StackedHttpKernel:handle in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:641 #0 Illuminate\Foundation\Application:run in /var/www/html/pga/public/index.php:51 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AIRAVATA-1588) When clicked on button 'Start over' in Create Experiment page, page crashes
[ https://issues.apache.org/jira/browse/AIRAVATA-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi closed AIRAVATA-1588. -- Resolution: Fixed When clicked on button 'Start over' in Create Experiment page, page crashes --- Key: AIRAVATA-1588 URL: https://issues.apache.org/jira/browse/AIRAVATA-1588 Project: Airavata Issue Type: Bug Affects Versions: 0.14 Environment: http://test-drive.airavata.org/pga/public Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2015-02-19 at 12.49.07 PM.png Entered the experiment name, project was the auto selected first project in the LOV and the application is AutoDock Clicked on Continue button and then clicked on 'Start over' button (wanted to select a different application and start over) Page crashed. Error page attached Created the experiment as the admin user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AIRAVATA-1548) Cannot Save and Launch WRF and Trinity on Stampede from the Gateway; Exits the Create Experiment Page
[ https://issues.apache.org/jira/browse/AIRAVATA-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi closed AIRAVATA-1548. -- Resolution: Fixed Cannot Save and Launch WRF and Trinity on Stampede from the Gateway; Exits the Create Experiment Page - Key: AIRAVATA-1548 URL: https://issues.apache.org/jira/browse/AIRAVATA-1548 Project: Airavata Issue Type: Bug Components: Website/Documentation Environment: http://dev.test-drive.airavata.org/pga/public/ gw111 Reporter: Eroma Assignee: Nipurn Doshi In Create Experiments page entered all information for WRF and Trinity application and clicked on save. Without any error message or notice user is existed from the page; no experiment is created or launched -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AIRAVATA-1543) Deleting a Queue from existing compute resource and updating priority order in job submission interface navigates to http://dev.test-drive.airavata.org/pga/public/cr/de
[ https://issues.apache.org/jira/browse/AIRAVATA-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi closed AIRAVATA-1543. -- Resolution: Fixed Deleting a Queue from existing compute resource and updating priority order in job submission interface navigates to http://dev.test-drive.airavata.org/pga/public/cr/delete-jsi (This is a blank page) and then page crashes - Key: AIRAVATA-1543 URL: https://issues.apache.org/jira/browse/AIRAVATA-1543 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org/pga/public/ Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-12-03 at 2.12.42 PM.png When editing an existing compute resource; clicked on Delete button in the deletion confirmation pop-up window and was navigated to http://dev.test-drive.airavata.org/pga/public/cr/delete-jsi page. When clicked on this link it crashes the page (image attached) Same happened when tried to update priority for Job Submission Interfaces in compute resource. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AIRAVATA-1539) Create Experiment Crashes when clicked button 'Continue' in http://dev.test-drive.airavata.org/pga/public/
[ https://issues.apache.org/jira/browse/AIRAVATA-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi closed AIRAVATA-1539. -- Resolution: Fixed Create Experiment Crashes when clicked button 'Continue' in http://dev.test-drive.airavata.org/pga/public/ -- Key: AIRAVATA-1539 URL: https://issues.apache.org/jira/browse/AIRAVATA-1539 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org/pga/public/ Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-12-01 at 11.53.21 AM.png Navigated to Experiment -- Create Experiment Entered experiment name and clicked 'Continue' page crashed (image attached) Observation: The crash is due to the selected default Application; ultrascan -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1693) Clone is not working in http://dev.test-drive.airavata.org/portal/pga/public/ PGA
[ https://issues.apache.org/jira/browse/AIRAVATA-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1693. Resolution: Fixed Clone is not working in http://dev.test-drive.airavata.org/portal/pga/public/ PGA - Key: AIRAVATA-1693 URL: https://issues.apache.org/jira/browse/AIRAVATA-1693 Project: Airavata Issue Type: Bug Components: PGA PHP Web Gateway Environment: http://dev.test-drive.airavata.org/portal/pga/public/ Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2015-04-27 at 10.48.15 AM.png Clicked on button 'Clone' in Experiment Summary page and the page crashed. error page image attached When searched the clone was actually created; new cloned experiment exists in 'CREATED' state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1693) Clone is not working in http://dev.test-drive.airavata.org/portal/ultrascan-testing/public PGA http://dev.test-drive.airavata.org/portal/pga/public/
[ https://issues.apache.org/jira/browse/AIRAVATA-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14514589#comment-14514589 ] Nipurn Doshi commented on AIRAVATA-1693: The issue is fixed. All portals just need to be updated. Currently only pga is updated with the new code. Clone is not working in http://dev.test-drive.airavata.org/portal/ultrascan-testing/public PGA http://dev.test-drive.airavata.org/portal/pga/public/ -- Key: AIRAVATA-1693 URL: https://issues.apache.org/jira/browse/AIRAVATA-1693 Project: Airavata Issue Type: Bug Components: PGA PHP Web Gateway Environment: http://dev.test-drive.airavata.org/portal/ultrascan-testing/public http://dev.test-drive.airavata.org/portal/pga/public/ Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2015-04-27 at 10.48.15 AM.png, Screen Shot 2015-04-27 at 2.08.52 PM.png Clicked on button 'Clone' in Experiment Summary page and the page crashed. error page image attached When searched the clone was actually created; new cloned experiment exists in 'CREATED' state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1613) Cannot create an experiment on dev.test-drive
[ https://issues.apache.org/jira/browse/AIRAVATA-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14345279#comment-14345279 ] Nipurn Doshi commented on AIRAVATA-1613: Can you also tell me the project and application you are trying to use? Cannot create an experiment on dev.test-drive - Key: AIRAVATA-1613 URL: https://issues.apache.org/jira/browse/AIRAVATA-1613 Project: Airavata Issue Type: Bug Environment: interface: web; browser: chrome 40.0.2214.115 (64-bit); os: Linux; Reporter: Shahbaz Memon Assignee: Nipurn Doshi Continue at the Create a new Experiment page leads to the following error, ErrorException thrown with message TSocket read 0 bytes (View: /var/www/html/pga/app/views/experiment/create-complete.blade.php) Stacktrace: #28 ErrorException in /var/www/html/pga/vendor/apache/thrift/lib/php/lib/Thrift/Transport/TSocket.php:269 #27 Illuminate\View\Engines\CompilerEngine:handleViewException in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php:41 #26 Thrift\Exception\TTransportException in /var/www/html/pga/vendor/apache/thrift/lib/php/lib/Thrift/Transport/TSocket.php:269 #25 Thrift\Transport\TSocket:read in /var/www/html/pga/vendor/apache/thrift/lib/php/lib/Thrift/Transport/TTransport.php:74 #24 Thrift\Transport\TTransport:readAll in /var/www/html/pga/vendor/apache/thrift/lib/php/lib/Thrift/Protocol/TBinaryProtocol.php:305 #23 Thrift\Protocol\TBinaryProtocol:readI32 in /var/www/html/pga/vendor/apache/thrift/lib/php/lib/Thrift/Protocol/TBinaryProtocol.php:197 #22 Thrift\Protocol\TBinaryProtocol:readMessageBegin in /var/www/html/pga/app/libraries/Airavata/API/Airavata.php:3013 #21 Airavata\API\AiravataClient:recv_getAvailableAppInterfaceComputeResources in /var/www/html/pga/app/libraries/Airavata/API/Airavata.php:2982 #20 Airavata\API\AiravataClient:getAvailableAppInterfaceComputeResources in /var/www/html/pga/app/libraries/utilities.php:453 #19 Utilities:get_available_app_interface_compute_resources in /var/www/html/pga/app/libraries/utilities.php:1252 #18 Utilities:create_compute_resources_select in /var/www/html/pga/app/storage/views/940d078e435420273432848fbbabae24:46 #17 include in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/Engines/PhpEngine.php:37 #16 Illuminate\View\Engines\PhpEngine:evaluatePath in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/Engines/CompilerEngine.php:56 #15 Illuminate\View\Engines\CompilerEngine:get in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/View.php:134 #14 Illuminate\View\View:getContents in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/View.php:102 #13 Illuminate\View\View:renderContents in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/View/View.php:76 #12 Illuminate\View\View:render in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Http/Response.php:43 #11 Illuminate\Http\Response:setContent in /var/www/html/pga/vendor/symfony/http-foundation/Symfony/Component/HttpFoundation/Response.php:202 #10 Symfony\Component\HttpFoundation\Response:__construct in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Routing/Router.php:1496 #9 Illuminate\Routing\Router:prepareResponse in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Routing/Router.php:1031 #8 Illuminate\Routing\Router:dispatchToRoute in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Routing/Router.php:996 #7 Illuminate\Routing\Router:dispatch in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:775 #6 Illuminate\Foundation\Application:dispatch in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:745 #5 Illuminate\Foundation\Application:handle in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Session/Middleware.php:72 #4 Illuminate\Session\Middleware:handle in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Cookie/Queue.php:47 #3 Illuminate\Cookie\Queue:handle in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Cookie/Guard.php:51 #2 Illuminate\Cookie\Guard:handle in /var/www/html/pga/vendor/stack/builder/src/Stack/StackedHttpKernel.php:23 #1 Stack\StackedHttpKernel:handle in /var/www/html/pga/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:641 #0 Illuminate\Foundation\Application:run in /var/www/html/pga/public/index.php:51 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1537) Can save Application Input and Application Output details without the mandatory Name (Input and Output Key)
[ https://issues.apache.org/jira/browse/AIRAVATA-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1537. Resolution: Fixed Can save Application Input and Application Output details without the mandatory Name (Input and Output Key) --- Key: AIRAVATA-1537 URL: https://issues.apache.org/jira/browse/AIRAVATA-1537 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Application Interfaces can be created and updated to have Input and Output Fields without the Name (Input Key/Output Key) Records gets saved in to database with default data type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1532) Echo fails on http://dev.test-drive.airavata.org when Saved Launched
[ https://issues.apache.org/jira/browse/AIRAVATA-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1532. Resolution: Fixed Echo fails on http://dev.test-drive.airavata.org when Saved Launched -- Key: AIRAVATA-1532 URL: https://issues.apache.org/jira/browse/AIRAVATA-1532 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-11-15 at 6.48.11 PM.png In http://dev.test-drive.airavata.org gw111 Echo failed on BR2. Upon clicking Save and Launch in Create Experiment page crashed. Error screen image attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1535) In edit moe when more GRID FTP end points are added and updated they do not get saved
[ https://issues.apache.org/jira/browse/AIRAVATA-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223602#comment-14223602 ] Nipurn Doshi commented on AIRAVATA-1535: Hi, its a problem in the backend with respect to the API. Can you reassign this to Chathuri? In edit moe when more GRID FTP end points are added and updated they do not get saved - Key: AIRAVATA-1535 URL: https://issues.apache.org/jira/browse/AIRAVATA-1535 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org/pga/public Reporter: Eroma Assignee: Nipurn Doshi In edit mode when existing Grip End Points (when Data Movement Protocol is GridFTP) are removed, or modified and saved the new changes do not get saved. The previous will remain. In edit mode if new GRID FTP end points are added and saved they also don't get saved. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1533) Cannot successfully save and create application interface in http://test-drive.airavata.org/pga/public/
[ https://issues.apache.org/jira/browse/AIRAVATA-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1533. Resolution: Fixed Cannot successfully save and create application interface in http://test-drive.airavata.org/pga/public/ --- Key: AIRAVATA-1533 URL: https://issues.apache.org/jira/browse/AIRAVATA-1533 Project: Airavata Issue Type: Bug Components: Application Catalog Affects Versions: 0.14 Environment: http://test-drive.airavata.org/pga/public/ Reporter: Eroma Assignee: Nipurn Doshi Entered application interface details, input and output parameters and clicked on 'Create'; application interface does not get created; no error messages as well -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1499) In Compute resource 'Register' and 'Browse' all integer fields (number fields) should not allow saving minus values.
[ https://issues.apache.org/jira/browse/AIRAVATA-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1499. Resolution: Fixed In Compute resource 'Register' and 'Browse' all integer fields (number fields) should not allow saving minus values. Key: AIRAVATA-1499 URL: https://issues.apache.org/jira/browse/AIRAVATA-1499 Project: Airavata Issue Type: Bug Environment: Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor Number fields avoids saving decimal points and characters but allows minus values. Even when user enters decimal, characters, etc... user can save the record successfully. No warning or error message given. Only when retrieved the record back would be able to see that the values given was not actually saved. Better to give tooltips on the value range allowed in these fields. Should restrict decimal, characters and mini values. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1525) When clicked on 'Continue' button in Create Experiment Page crashes
[ https://issues.apache.org/jira/browse/AIRAVATA-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1525. Resolution: Fixed When clicked on 'Continue' button in Create Experiment Page crashes --- Key: AIRAVATA-1525 URL: https://issues.apache.org/jira/browse/AIRAVATA-1525 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-11-14 at 6.48.46 AM.png In Create Experiment selected input file uploading application (Amber/WRF) and clicked on 'Continue' button Page crashed; image attached. Cannot continue with Experiment creation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1528) In Application Interface create mode 'Add Application Input' and 'Add Application Output' buttons are not labeled; they are just blank buttons
[ https://issues.apache.org/jira/browse/AIRAVATA-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1528. Resolution: Fixed In Application Interface create mode 'Add Application Input' and 'Add Application Output' buttons are not labeled; they are just blank buttons -- Key: AIRAVATA-1528 URL: https://issues.apache.org/jira/browse/AIRAVATA-1528 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor In Application Interface creating mode above mentioned buttons are blank buttons without a caption. Also they are not at the bottom of the last created input or output filed but somewhere in middle. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1513) In field 'Queue Max Run Time' indicate that time is captured in Minutes.
[ https://issues.apache.org/jira/browse/AIRAVATA-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1513. Resolution: Fixed In field 'Queue Max Run Time' indicate that time is captured in Minutes. - Key: AIRAVATA-1513 URL: https://issues.apache.org/jira/browse/AIRAVATA-1513 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor Similar to 'Wall Time Limit' in Create Experiment please indicate the captured 'Queue Max Run Time' in Queue is in 'Minutes'. Also in this field decimals and minus values should be restricted. Currently minus values are taken as valid entries. For a invalid entry a meaningful message/tooltip should be prompted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1516) Message tooltip prompted in 'Priority' field of 'Job Submission interface' should show the user valid number range
[ https://issues.apache.org/jira/browse/AIRAVATA-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1516. Resolution: Fixed Message tooltip prompted in 'Priority' field of 'Job Submission interface' should show the user valid number range --- Key: AIRAVATA-1516 URL: https://issues.apache.org/jira/browse/AIRAVATA-1516 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor Currently when user enters characters; tooltip given is 'Please fill out this field' Instead of this user should be informed the valid range. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1515) When user gives an existing Queue Name indicate its a unique value and cannot repeat
[ https://issues.apache.org/jira/browse/AIRAVATA-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1515. Resolution: Fixed When user gives an existing Queue Name indicate its a unique value and cannot repeat - Key: AIRAVATA-1515 URL: https://issues.apache.org/jira/browse/AIRAVATA-1515 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor Queue Name is a primary key (Names are defined by the resource) in DB there for it cannot be repeated. If user entered an existing name please prompt an error message upon saving. Currently user clicks on save and no Queue is created neither user informed any reason. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1498) Cannot delete job submission protocols and data movement protocol from compute resource in edit mode
[ https://issues.apache.org/jira/browse/AIRAVATA-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1498. Resolution: Fixed Cannot delete job submission protocols and data movement protocol from compute resource in edit mode Key: AIRAVATA-1498 URL: https://issues.apache.org/jira/browse/AIRAVATA-1498 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org/ Reporter: Eroma Assignee: Nipurn Doshi After adding job submission protocols and data movement protocol clicked on the delete icon. Protocols remained without getting deleted or prompting any confirmation pop up window Using Firefox browser for testing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1508) Can provide spaces for Application Module Name and save the record successfully
[ https://issues.apache.org/jira/browse/AIRAVATA-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1508. Resolution: Fixed Can provide spaces for Application Module Name and save the record successfully --- Key: AIRAVATA-1508 URL: https://issues.apache.org/jira/browse/AIRAVATA-1508 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org/ Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor User should not be able to save application module detail by providing spaces for mandatory fields -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1512) Queue Description field length should be increased
[ https://issues.apache.org/jira/browse/AIRAVATA-1512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1512. Resolution: Fixed Queue Description field length should be increased -- Key: AIRAVATA-1512 URL: https://issues.apache.org/jira/browse/AIRAVATA-1512 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org/ Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor In both Register Compute Resource and Edit Compute Resource the field length of Queue Description is 30 in the UI. DB length is set at 255 characters. Please increase the length in the front-end -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1514) Integer fields Queue Max Nodes, Queue Max Processors and Max Jobs in Queue should not accept minus values, decimal values and characters
[ https://issues.apache.org/jira/browse/AIRAVATA-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1514. Resolution: Fixed Integer fields Queue Max Nodes, Queue Max Processors and Max Jobs in Queue should not accept minus values, decimal values and characters - Key: AIRAVATA-1514 URL: https://issues.apache.org/jira/browse/AIRAVATA-1514 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor Currently user can enter decimals characters and minus numbers in to above mentioned fields and save. Upon saving the decimals are removed, if characters are entered it will get replaced by 0. Ideally user should be given tooltip messages to indicate valid data ranges. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1506) Priority field for Job submission protocol and Data movement protocol should be numeric
[ https://issues.apache.org/jira/browse/AIRAVATA-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1506. Resolution: Fixed Priority field for Job submission protocol and Data movement protocol should be numeric --- Key: AIRAVATA-1506 URL: https://issues.apache.org/jira/browse/AIRAVATA-1506 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Fields in Update priority are varchar. Should be numeric and minus numbers and decimal numbers should also be restricted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1527) In Application Interface, App Output Fields 'Value' is indicated as mandatory by a red star but can create without giving a value
[ https://issues.apache.org/jira/browse/AIRAVATA-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1527. Resolution: Fixed In Application Interface, App Output Fields 'Value' is indicated as mandatory by a red star but can create without giving a value - Key: AIRAVATA-1527 URL: https://issues.apache.org/jira/browse/AIRAVATA-1527 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor App Catalog -- Interface in App Output Fields section, field 'Value' is indicated as mandatory by a red star. User can create the app interface without entering the value field. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1523) In Data Movement Interface page 'Grid FTP End Points' is shown as mandatory but can be saved without entering data
[ https://issues.apache.org/jira/browse/AIRAVATA-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1523. Resolution: Fixed In Data Movement Interface page 'Grid FTP End Points' is shown as mandatory but can be saved without entering data -- Key: AIRAVATA-1523 URL: https://issues.apache.org/jira/browse/AIRAVATA-1523 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi In Compute Resource -- Data Movement Interface page for protocol GRIDFTP, 'Grid FTP End Point' field is indicated as mandatory by a star (*) But the protocol can be saved without a Grid FTP End Point -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1526) Can Save Application Interface without Application Module which crashes the page at saving
[ https://issues.apache.org/jira/browse/AIRAVATA-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1526. Resolution: Fixed Can Save Application Interface without Application Module which crashes the page at saving -- Key: AIRAVATA-1526 URL: https://issues.apache.org/jira/browse/AIRAVATA-1526 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-11-14 at 1.14.58 PM.png App Catalog -- Interface entered all application interface information and removed application module and clicked Create. Page crashed. Here a warning message or a tooltip should be given forcing user to have at least on application module per interface Image attached -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1509) Application Module text field length is greater than the length defined for the text field in the Database. Hence the page crashes
[ https://issues.apache.org/jira/browse/AIRAVATA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1509. Resolution: Fixed Application Module text field length is greater than the length defined for the text field in the Database. Hence the page crashes -- Key: AIRAVATA-1509 URL: https://issues.apache.org/jira/browse/AIRAVATA-1509 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org/ Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor Attachments: Screen Shot 2014-11-07 at 12.59.00 PM.png Application Module Name field length is greater than the length defined for the field in the Database. Hence the page crashes. screen shot attached Please restrict the field length to the length defined in the database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1509) Application Module text field length is greater than the length defined for the text field in the Database. Hence the page crashes
[ https://issues.apache.org/jira/browse/AIRAVATA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208233#comment-14208233 ] Nipurn Doshi commented on AIRAVATA-1509: Can you let me know how much is the maximum allowed character length that has to be set for module name ? Application Module text field length is greater than the length defined for the text field in the Database. Hence the page crashes -- Key: AIRAVATA-1509 URL: https://issues.apache.org/jira/browse/AIRAVATA-1509 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org/ Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor Attachments: Screen Shot 2014-11-07 at 12.59.00 PM.png Application Module Name field length is greater than the length defined for the field in the Database. Hence the page crashes. screen shot attached Please restrict the field length to the length defined in the database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1504) Can save a Compute Resource by giving spaces for alias and ip address
[ https://issues.apache.org/jira/browse/AIRAVATA-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1504. Resolution: Fixed Can save a Compute Resource by giving spaces for alias and ip address - Key: AIRAVATA-1504 URL: https://issues.apache.org/jira/browse/AIRAVATA-1504 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org/ Reporter: Eroma Assignee: Nipurn Doshi User can successfully save spaces for compute resource alias and ip address Spaces should not be allowed as a valid input -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1503) Click on link 'View' of one of the listed compute resource in Compute Resource --Browse gives error
[ https://issues.apache.org/jira/browse/AIRAVATA-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1503. Resolution: Fixed Click on link 'View' of one of the listed compute resource in Compute Resource --Browse gives error Key: AIRAVATA-1503 URL: https://issues.apache.org/jira/browse/AIRAVATA-1503 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-11-04 at 4.22.54 PM.png When clicked on link 'View' of a listed compute resource gives the attached error screen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1505) When adding job submission protocols and data movement protocols can add the same protocol multiple times
[ https://issues.apache.org/jira/browse/AIRAVATA-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1505. Resolution: Fixed When adding job submission protocols and data movement protocols can add the same protocol multiple times - Key: AIRAVATA-1505 URL: https://issues.apache.org/jira/browse/AIRAVATA-1505 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Can add the same job submission protocol and data movement protocol multiple times to a single Compute resource. Ideally once added it should be removed fro nth drop down to restrict getting added again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1503) Click on link 'View' of one of the listed compute resource in Compute Resource --Browse gives error
[ https://issues.apache.org/jira/browse/AIRAVATA-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14201017#comment-14201017 ] Nipurn Doshi commented on AIRAVATA-1503: Viewing summary of Compute Resource is not complete yet. Click on link 'View' of one of the listed compute resource in Compute Resource --Browse gives error Key: AIRAVATA-1503 URL: https://issues.apache.org/jira/browse/AIRAVATA-1503 Project: Airavata Issue Type: Bug Components: Application Catalog Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-11-04 at 4.22.54 PM.png When clicked on link 'View' of a listed compute resource gives the attached error screen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1501) Should be able to delete/remove existing Queues from the compute resource.
[ https://issues.apache.org/jira/browse/AIRAVATA-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1501. Resolution: Fixed Should be able to delete/remove existing Queues from the compute resource. -- Key: AIRAVATA-1501 URL: https://issues.apache.org/jira/browse/AIRAVATA-1501 Project: Airavata Issue Type: New Feature Components: Application Catalog Reporter: Eroma Assignee: Nipurn Doshi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1500) When saving Compute Resource File System data a record gets saved even when a path is not defined.
[ https://issues.apache.org/jira/browse/AIRAVATA-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1500. Resolution: Fixed When saving Compute Resource File System data a record gets saved even when a path is not defined. -- Key: AIRAVATA-1500 URL: https://issues.apache.org/jira/browse/AIRAVATA-1500 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor Add a compute resource and then add paths to the file systems Home and Work and click on update. Not only Home and Work which has paths defined get saved but the others as well. If the added paths are removed and updated DB table will have records for all 5 file system without having a file path. Ideally the table should only have file systems which has paths defined. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1493) Confirmation messages, warning messages should be displayed below the main menu bar
[ https://issues.apache.org/jira/browse/AIRAVATA-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1493. Resolution: Fixed Confirmation messages, warning messages should be displayed below the main menu bar --- Key: AIRAVATA-1493 URL: https://issues.apache.org/jira/browse/AIRAVATA-1493 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org/pga/public Reporter: Eroma Assignee: Nipurn Doshi Priority: Minor All confirmation message, warning messages and any other message prompted in gateway page should be below the main menu bar. Currently the messages are displayed above the menu bar. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1490) When existing Host Aliases and IP addresses are modified and saved they multiplies
[ https://issues.apache.org/jira/browse/AIRAVATA-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1490. Resolution: Fixed When existing Host Aliases and IP addresses are modified and saved they multiplies -- Key: AIRAVATA-1490 URL: https://issues.apache.org/jira/browse/AIRAVATA-1490 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org/pga/public Reporter: Eroma Assignee: Nipurn Doshi Logged in to gateway through admin user. navigation Compute Resource -- Register Compute Resource and created the aliases and ip addresses Then modified the save aliases and ip address and clicked ' Save changes' Except updating the existing new aliases and ip addresses got created multiplying the aliases and ip addresses. Same multipication happens when an existing aliases or a IP address is removed. A new empty record gets created in HOST_ALIAS and HOST_IPADDRESS tables. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AIRAVATA-1491) When adding Queue to a resrouces even though all fields are indicated as mandatory with * can save a queue records without any values.
[ https://issues.apache.org/jira/browse/AIRAVATA-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi closed AIRAVATA-1491. -- When adding Queue to a resrouces even though all fields are indicated as mandatory with * can save a queue records without any values. -- Key: AIRAVATA-1491 URL: https://issues.apache.org/jira/browse/AIRAVATA-1491 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org/pga/public Reporter: Eroma Assignee: Nipurn Doshi After saving compute resource data click on 'Add Queue' without entering any data click on 'Create' Record get saved without any data although data labels indicate they are mandatory. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1496) When tried to change and update the security protocol of job interface protocol the page crashes with the attached error
[ https://issues.apache.org/jira/browse/AIRAVATA-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1496. Resolution: Fixed It was an API issue, fixed by Chathuri. When tried to change and update the security protocol of job interface protocol the page crashes with the attached error --- Key: AIRAVATA-1496 URL: https://issues.apache.org/jira/browse/AIRAVATA-1496 Project: Airavata Issue Type: Bug Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-11-04 at 12.57.24 PM.png Navigation PGA -- Compute Resource -- Register There after adding the compute resource details I added Job submission protocols and saved it. afterwards i again changed the 'Resource Manager Type' and clicked on Update. Gives the attached error screen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1482) When an experiment is in CREATED state is cloned; experiment name in the cloned experiment also changes to 'Clone of'
[ https://issues.apache.org/jira/browse/AIRAVATA-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1482. Resolution: Fixed When an experiment is in CREATED state is cloned; experiment name in the cloned experiment also changes to 'Clone of' -- Key: AIRAVATA-1482 URL: https://issues.apache.org/jira/browse/AIRAVATA-1482 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Create an experiment with exp_name Test_Echo2 Go to the experiment summary and clone the experiment Both new and old experiment will have name 'Clone of Test_Echo2' Experiment which was cloned (old experiment) should not get its name changed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (AIRAVATA-1482) When an experiment is in CREATED state is cloned; experiment name in the cloned experiment also changes to 'Clone of'
[ https://issues.apache.org/jira/browse/AIRAVATA-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi closed AIRAVATA-1482. -- When an experiment is in CREATED state is cloned; experiment name in the cloned experiment also changes to 'Clone of' -- Key: AIRAVATA-1482 URL: https://issues.apache.org/jira/browse/AIRAVATA-1482 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Create an experiment with exp_name Test_Echo2 Go to the experiment summary and clone the experiment Both new and old experiment will have name 'Clone of Test_Echo2' Experiment which was cloned (old experiment) should not get its name changed -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1484) Cannot view Experiment Summary by clicking an Experiment Status in Project Summary
[ https://issues.apache.org/jira/browse/AIRAVATA-1484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1484. Resolution: Fixed Cannot view Experiment Summary by clicking an Experiment Status in Project Summary -- Key: AIRAVATA-1484 URL: https://issues.apache.org/jira/browse/AIRAVATA-1484 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org/pga/public Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-10-24 at 11.25.08 AM.png Navigation Project -- Search Project -- View a Project All experiments are displayed under the project. Clicked on the Status of an experiment Gets the attached error prompt. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AIRAVATA-1486) Compute Alias created for resource doesn't get properly saved in the table HOST_ALIAS
[ https://issues.apache.org/jira/browse/AIRAVATA-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14182989#comment-14182989 ] Nipurn Doshi commented on AIRAVATA-1486: This issue is opened at another place ( Airavata 1477 ) that I have created, which Chathuri is on working currently. I'm closing this one. Compute Alias created for resource doesn't get properly saved in the table HOST_ALIAS - Key: AIRAVATA-1486 URL: https://issues.apache.org/jira/browse/AIRAVATA-1486 Project: Airavata Issue Type: Bug Reporter: Eroma Assignee: Nipurn Doshi When compute Aliases are saved it is not saved with the values i have given but saves as a index number sort of a value against the RESOURCE_ID in HOST_ALIAS table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1481) Cannot view experiments created under a project; Error message window prompted
[ https://issues.apache.org/jira/browse/AIRAVATA-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1481. Resolution: Fixed Cannot view experiments created under a project; Error message window prompted -- Key: AIRAVATA-1481 URL: https://issues.apache.org/jira/browse/AIRAVATA-1481 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org/pga/public/ Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-10-23 at 2.48.43 PM.png Navigation Projects -- Search Project -- Search for a project with experiments and click View Prompted error window attached as screen shot -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1480) In Experiment Summary; compute resource is blank; experiment immediately fails as well
[ https://issues.apache.org/jira/browse/AIRAVATA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1480. Resolution: Fixed Fixed Compute Resource being blank issue. Experiment failing is a separate issue. In Experiment Summary; compute resource is blank; experiment immediately fails as well -- Key: AIRAVATA-1480 URL: https://issues.apache.org/jira/browse/AIRAVATA-1480 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org/pga/public/ Reporter: Eroma Assignee: Nipurn Doshi When the experiment is created or when its created and launched at the same time compute resource is missing form the created experiment. Experiment fails as quickly as its created too. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (AIRAVATA-1483) When an experiment is launched confirmation message is prompted on a total new blank page/screen, not in the Summary page itself
[ https://issues.apache.org/jira/browse/AIRAVATA-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nipurn Doshi resolved AIRAVATA-1483. Resolution: Fixed When an experiment is launched confirmation message is prompted on a total new blank page/screen, not in the Summary page itself Key: AIRAVATA-1483 URL: https://issues.apache.org/jira/browse/AIRAVATA-1483 Project: Airavata Issue Type: Bug Environment: http://dev.test-drive.airavata.org Reporter: Eroma Assignee: Nipurn Doshi Attachments: Screen Shot 2014-10-23 at 4.24.17 PM.png -- This message was sent by Atlassian JIRA (v6.3.4#6332)
