Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cFE req. cES1007.2: Restart Application - Reject On Missing File #915

Closed
dmknutsen opened this issue Sep 28, 2020 · 4 comments · Fixed by #1128 or #1150
Closed

cFE req. cES1007.2: Restart Application - Reject On Missing File #915

dmknutsen opened this issue Sep 28, 2020 · 4 comments · Fixed by #1128 or #1150
Labels
bug docs This change only affects documentation. requirements
Milestone

Comments

@dmknutsen
Copy link
Contributor

Describe the bug
cFE requirement cES1007.2 specifies that a user can not restart an Application if the original file has been removed. If the user attempts to restart an application following removal of file, the cFE shall reject the Command, increment the invalid Command counter, and generate an event message.

This is not what happens when the restart application command is received. If a user has deleted the cFE Application file and then sends the restart application command. The application successfully restarts.

To Reproduce
Steps to reproduce the behavior:
Delete an applications shared library file from the /cf/ location.
Send the associated restart application command.

System observed on:
Oracle VM VirtualBox
OS: ubuntu-19.10
Versions: cfe v6.8.0-rc1+dev28, osal v5.1.0-rc1+dev12, psp v1.4.0+dev76

Reporter Info
Dan Knutsen
NASA/Goddard

@skliper skliper transferred this issue from nasa/cFS Sep 28, 2020
@skliper
Copy link
Contributor

skliper commented Sep 28, 2020

Related to #424, which was reported as a requirements failure since the restart didn't work. Need to resolve if something changed, or a different process is being used, or if it's a system dependency.

@skliper skliper added the bug label Sep 30, 2020
@skliper
Copy link
Contributor

skliper commented Jan 12, 2021

Now that osal is working as expected, we are still failing this requirement since the command doesn't error (the request to restart is sent correctly so the valid command counter is incremented). Likely worth just adding the file check so it is even more similar to reload.

@skliper
Copy link
Contributor

skliper commented Jan 12, 2021

Actually there's 3 requirements that no longer are met in terms of incrementing the error counter:
cES1007.2 (already documented above)
cES1007.3: If the cFE Application Restart fails due to a non-parameter error, then the cFE shall delete the Application, increment the invalid Command counter, and generate an event message.
cES1008.3: If the cFE Application Reload fails due to a non-parameter error, then the cFE shall delete the Application, increment the invalid Command counter, and generate an event message.

Command just does the request, failure to load due to a non-parameter error does not increment the invalid command counter.

@skliper skliper added this to the 7.0.0 milestone Jan 12, 2021
@skliper
Copy link
Contributor

skliper commented Jan 25, 2021

This issue is partially fixed by #1038, still will fail on missing file though without incrementing the invalid command counter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug docs This change only affects documentation. requirements
Projects
None yet
3 participants