...
The following test/verification assumes that a full reference setup has been deployed. I.e. all components in the system should be deployed and running. It also requires that the tester has access to disable one of the components that is expected to deliver status messages.
- Check that the service reports all components report the status "OK", resulting them marked as green on the Status page of the Webclient.
- http://int-bitmag-02.kb.dk:8080/bitrepository-webclient/status-service.html
- Shutdown a status contributor and verify that its status is reported as "UNRESPONSIVE" and marked with a red color, after MaxRetries*Check Interval time.
ssh bm-refpillar@int-bitmag-01.kb.dk
- bash pillars/reference2/bin pillar.sh stop
- When after a contributor has been marked as "UNRESPONSIVE" verify that an alarm message has been received by the alarm service and that the name of the unresponsive contributor is to be found in it.
...
- Start the contributor that were previously shutdown, and verify that it's status changes back to "OK" on the status page.
- ssh bm-refpillar@int-bitmag-01.kb.dk
- bash pillars/reference2/bin pillar.sh start
| Child pages (Children Display) |
|---|
| excerpt | true |
|---|
| excerptType | simple |
|---|
|
Open issues
| Jira Legacy |
|---|
| server | SBForgeSystem JIRA |
|---|
| columns | key,priority,summary,type,created |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = BITMAG AND resolution = Unresolved AND component = "getfilemonitoring" ORDER BY priority DESC |
|---|
| serverId | 327e372c81c76265-baf0cab2-3de43ba5-afa1b74d-7694d9fcf12bee7cd9a2765e |
|---|
|