[QA] Please add test to check start/stop/restart lma_collector (heka) and collectd services

Bug #1560844 reported by Denis Klepikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
LMA-Toolchain Fuel Plugins
Mitaka
Invalid
High
LMA-Toolchain Fuel Plugins
StackLight
Confirmed
High
LMA-Toolchain Fuel Plugins

Bug Description

Due to we have the same behavior on customer's environments, where we restarting lma_collector (hekad) and collectd services via "kill -9 " please add test to check start/stop/restart lma_collector (heka) and collectd services.

Test plan should contain next steps:

1 create environment with LMA plugins installed.
2 create close to production load! Environment should generate a lot of logs during test. The load should be periodical.
3 move vip__management service into pacemaker to another controller node
4 ensure that lma_collector (heka) sending data to eleasticsearch, influxdb, nagios
5 in 1 hour move vip__management service into pacemaker to another controller node
6 ensure that lma_collector (heka) sending data to eleasticsearch, influxdb, nagios
7 check PID of hekad and collectd on all nodes ans save this data
8 stop lma_collector (heka) via "pcs resource disable lma_collector"
9 wait while pcs report that lma_collector (heka) stopped on all controllers
10 check PID of hekad and (collectd - need deeper investigation if it stopped too or we do not need to stop it) on all controllers. If hekad PID exist - test failed
11 stop lma_collector (heka) via "pcs resource enable lma_collector"
12 wait while pcs report that lma_collector (heka) started on all controllers.
13 check that data was correctly sent to eleasticsearch, influxdb, nagios
14 from fuel master nodes restart lma_collector on all nodes except controllers via
"for i in fuel nodes............; do ......... initctl restart lma_collector; done"
15 check lma_collector (heka) PID and compare it with PID from step 7. If you see even 1 the same PID - test failed.
16 check that data was correctly sent to eleasticsearch, influxdb, nagios
17 from fuel master nodes stop lma_collector on all nodes except controllers via
"for i in fuel nodes............; do ......... initctl stop lma_collector; done"
18 check lma_collector (heka) PID, if exist - test failed
19 from fuel master nodes start lma_collector on all nodes except controllers via
"for i in fuel nodes............; do ......... initctl start lma_collector; done"
20 check that data was correctly sent to eleasticsearch, influxdb, nagios

steps 14-20 should be applied to collectd service too
#/etc/init.d/collectd
Usage: /etc/init.d/collectd {start|stop|restart|force-reload|status}

Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → nobody
milestone: none → 9.0
importance: Undecided → High
Revision history for this message
Dmitry Klenov (dklenov) wrote :

Moving to LMA team.

tags: added: area-plugins
removed: area-qa
Changed in fuel:
assignee: nobody → LMA-Toolchain Fuel Plugins (mos-lma-toolchain)
Dmitry Klenov (dklenov)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

expected result

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
Changed in fuel:
milestone: 9.0 → 10.0
tags: added: to-cover-with-tests
Changed in lma-toolchain:
status: New → Confirmed
assignee: nobody → LMA-Toolchain Fuel Plugins (mos-lma-toolchain)
importance: Undecided → High
Changed in fuel:
status: Confirmed → Invalid
Swann Croiset (swann-w)
Changed in lma-toolchain:
milestone: none → 0.10.1
Swann Croiset (swann-w)
Changed in lma-toolchain:
milestone: 0.10.1 → 0.11.0
Changed in lma-toolchain:
milestone: 0.11.0 → 1.0.0
Swann Croiset (swann-w)
Changed in lma-toolchain:
milestone: 1.0.0 → none
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.