[TC_18] NebulOuS agent recovers after some of its component fails.

Bug #2054106 reported by Christos-Alexandros Sarros
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NebulOuS
New
Undecided
Unassigned

Bug Description

Objective:

NebulOuS agent tries to recover from failure of any of its components and provides sufficient logs to identify the root of the problem.

Preconditions:
1. NebulOuS agent is installed on a manually-managed node and running correctly.

2. User is logged in the machine and has appropriate rights for accessing NebulOuS agent logs.

3. “Dummy APP” is registered in NebulOuS and an instance is running on the node.

Steps:

Step 1.

- Action: A component of NebulOuS agent (X, Y, Z) fails (e.g: the process is manually killed).
- Expected results: User can see relevant logs. NebulOuS agent actively tries to resume normal operation. Application running on the node is terminated.

Step 2.
- Action: NebulOuS agent detects that one of its sub-component has failed and remediates the situation to make it again available.
- Expected results: NebulOuS agent resumes normal operation briefly. User can see relevant logs.

tags: added: test-case-r.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.