[
https://issues.apache.org/jira/browse/AIRAVATA-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318057#comment-17318057
]
Marcus Christie commented on AIRAVATA-3435:
-------------------------------------------
Discussed with [~eroma_a]. The issue is with the names of the stdout/stderr
files in the job script, which are named based on the "application interface"
application name.
https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/TaskContext.java#L851
When the application module name is changed, this doesn't automatically trigger
an update of the application name of the interface. But it could and fixing
that issue should fix this. The app interface name should be kept in sync with
the app module name for consistency.
> INVESTIGATE: When Application name changes, the STDOUT and STDERR file names
> doesn't get updated with the latest name
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-3435
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3435
> Project: Airavata
> Issue Type: Sub-task
> Components: Django Portal
> Affects Versions: 0.18
> Environment: https://django.seagrid.org/
> Reporter: Eroma
> Assignee: Marcus Christie
> Priority: Major
> Fix For: 0.19
>
>
> # Create a new application with module, interface and deployment.
> # The application STDOUT and STDERR are created with the application name.
> # Change the application name only
> # The STDOUT and STDERR names are not updated with the new application name.
> # An simple save in the interface, will updated the names at the moment but
> if user only changes the Description tab name, the STDOUT and STDERR remains
> with the old name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
