automation: Verify request_son_maintenance and cancel_request_son_maintenance commands #250

New issue

Closed

opened 2022-01-17 10:55:55 +00:00 by pavel.baykov · 5 comments

pavel.baykov commented

2022-01-17 10:55:55 +00:00

(Migrated from gitlab.com)

Consider a SON in active state

get_son <<son_account>>
Request for SON maintenance using below command:

request_son_maintenance <<son_account>> true
Verify SON is moved to request_maintenance status using below command
get_son <<son_account>>
Wait for next maintenance interval to be passed - Verify SON is moved to maintenance state using below command
get_son <<son_account>>
When the son sends next heartbeat, son status will be changed to active
get_son <<son_account>>
Verify SON is moved to active state using below command
get_son <<son_account>>
Consider a SON in any other state other than active state (ex: inactive, in_maintenance etc) and request for SON maintenance

request_son_maintenance <<son_account>> true
Consider a son which is any state other than request_maintenance state and run below command
cancel_request_son_maintenance <<son_account>> true
Consider an active son and request for son maintenance using below command
request_son_maintenance <<son_account>> true

Verify the status of the son using get_son command
cancel maintenance requested in the previous step using below command
cancel_request_son_maintenance <<son_account>> true
Verify the status of the son using get_son command

Consider a SON in active state get_son <<son_account>> Request for SON maintenance using below command: request_son_maintenance <<son_account>> true Verify SON is moved to request_maintenance status using below command get_son <<son_account>> Wait for next maintenance interval to be passed - Verify SON is moved to maintenance state using below command get_son <<son_account>> When the son sends next heartbeat, son status will be changed to active get_son <<son_account>> Verify SON is moved to active state using below command get_son <<son_account>> Consider a SON in any other state other than active state (ex: inactive, in_maintenance etc) and request for SON maintenance request_son_maintenance <<son_account>> true Consider a son which is any state other than request_maintenance state and run below command cancel_request_son_maintenance <<son_account>> true Consider an active son and request for son maintenance using below command request_son_maintenance <<son_account>> true Verify the status of the son using get_son command cancel maintenance requested in the previous step using below command cancel_request_son_maintenance <<son_account>> true Verify the status of the son using get_son command

pavel.baykov commented

2022-01-17 10:55:55 +00:00

(Migrated from gitlab.com)

assigned to @pavel.baykov

pavel.baykov commented

2022-01-21 09:17:25 +00:00

(Migrated from gitlab.com)

to test Request_SON_Maintenance:
pytest -s -v test.py::test_Request_SON_Maintenance
to test Cancel_Request_SON_Maintenance
pytest -s -v test.py::test_Cancel_Request_SON_Maintenance

to test Request_SON_Maintenance: pytest -s -v test.py::test_Request_SON_Maintenance to test Cancel_Request_SON_Maintenance pytest -s -v test.py::test_Cancel_Request_SON_Maintenance

serkixenos commented

2022-01-31 01:59:05 +00:00

(Migrated from gitlab.com)

Test fails

test.py::test_Verify_SON_State_Transition Verify SON state transition from active to in_maintenance and vice versa [auto]
Stopping docker: 3fe57afa0d37
Starting docker: 3fe57afa0d37
FAILED

Test fails ``` test.py::test_Verify_SON_State_Transition Verify SON state transition from active to in_maintenance and vice versa [auto] Stopping docker: 3fe57afa0d37 Starting docker: 3fe57afa0d37 FAILED ```

serkixenos commented

2022-01-31 03:23:36 +00:00

(Migrated from gitlab.com)

Is this test related?

serkixenos (Migrated from gitlab.com) closed this issue

2022-01-31 03:24:12 +00:00

pavel.baykov commented

2022-02-01 13:25:08 +00:00

(Migrated from gitlab.com)

i think test itself is good , but such tests have issues with Docker to accounts mapping
or there is a problem in the code itself

i think test itself is good , but such tests have issues with Docker to accounts mapping or there is a problem in the code itself