...
Tests that alarms can be generated and viewed correctly through the Alarm webgui. Specific alarms are tested in the tests cases related to the concrete specific functionalities.
Basic alarm
- Delete a file on a pillar.
- Run an integity integrity check for missing files.
- A new alarm should be generated by the integrity service, indicating that a integrity problem has been detected.
- A new alarm should be generated by the integrity service, indicating that a integrity problem has been detected.
...
Tests that alarms are stored on the messagebus persistent and durable (
Jira Legacy | ||||||||
---|---|---|---|---|---|---|---|---|
|
ssh bm_webservice@int-bitmag-02.kb.dk
and runtomcat-init.sh start
if it isn't running- The alarm service should be present under the active durable subscribers (can be checked at http://int-bitmag-01.kb.dk:8001/admin/subscribers.jsp)Now stop
Ensure the alarm service is running, and that it is a durable subscriber- Shutdown the alarm service
- Stop the service with
tomcatalarm-service-initit.sh stop
- This will stop the webclient,
- remove the alarm service from the tomcat90/webapps/ folder and restart the webclient tomcat server
- Checked that the alarm service is present under offline durable subscribers at http://int-bitmag-01.kb.dk:8001/admin/subscribers.jsp
- Stop the service with
- Alarm Generate a an alarm (run a integrity check on a inconsistent collection).
- Note the time of the alarm, and any other details to be able to identify it again.
- again
- Using
alarm-service-it.
- The alarm should be received on the alarm service
sh start
- When the webclient is restarted, it will automatically perform some checks that will cause alarms. This is where you need to use the details about the alarm you triggered to check that the alarm is present.
Start the alarm service - Using
Jira Issues | ||||||
---|---|---|---|---|---|---|
|