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

[TC_17] NebulOuS agent recovers after failure with communication with NebulOuS core #47

Open
jchmielewska opened this issue Sep 4, 2024 · 1 comment
Assignees
Labels
Test-Case Description of the Test Case

Comments

@jchmielewska
Copy link

Objective:

  • NebulOuS agent tries to recover from failure in communications with NebulOuS core and provides sufficient logs to identify the root of the problem.

Preconditions:

  • NebulOuS agent is installed on a manually-managed node and running correctly.
  • User is logged in the machine and has appropriate rights for accessing NebulOuS agent logs.
  • “Dummy APP” is registered in NebulOuS and an instance is running on the node.

Steps:

  1. Action:
  • NebulOuS agent can no longer contact NebulOuS core due some network issues (e.g: LAN cable disconnected, NebulOuS core goes down, etc…).

Expected results:

  • User can see relevant logs.
  • NebulOuS agent actively tries to resume normal operation.
  • Application running on the node is terminated.
  1. Action:
  • Link with NebulOuS core is recovered.

Expected results:

  • NebulOuS agent resumes normal operation briefly. User can see relevant logs.
@jchmielewska jchmielewska added the Test-Case Description of the Test Case label Sep 4, 2024
@Iqqdd99 Iqqdd99 added the bug Something isn't working label Sep 5, 2024
@jchmielewska jchmielewska removed the bug Something isn't working label Sep 5, 2024
@jchmielewska
Copy link
Author

jchmielewska commented Sep 5, 2024

for automation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Test-Case Description of the Test Case
Projects
None yet
Development

No branches or pull requests

4 participants