From Fedora Project Wiki

(Created page with "{{header|qa}} {{QA/Test_Case |description=This testcase checks whether kpartx will crash when called with invalid options. It is reported in fixed bug that when kpartx was pas...")
 
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{header|qa}}
{{header|qa}}
{{QA/Test_Case
{{QA/Test_Case
|description=This testcase checks whether kpartx will crash when called with invalid options.
|description= This testcase checks if multipathd responds with 'fail' for invalid device name. It is reported in fixed bug that multipathd responds with 'ok' for invalid device name.
It is reported in fixed bug that when kpartx was passes something other than a file 
or a block device or a badly formed pathname, it could read off the end of the device string, and crash.
The test steps include:1)install device-mapper device-mapper-multipath 2)restart multipathd service 3)kpartx -l / 4)check dmesg if there is segmentation fault
|actions=
|actions=
1. Ensure the device-mapper-multipath package is installed
1. Ensure the device-mapper-multipath package is installed
 
    Execute: dnf -y install device-mapper device-mapper-multipath
2. Clone the multipath repository:
    Execute: rpm -qa <nowiki>|</nowiki> grep multipath
git clone https://github.com/skycastlelily/storage-fedora.git
2. Execute the following command to generate the configuration file
3. cd into the testcase directory
    Execute: mpathconf --enable
  cd storage-fedora/multipath/kpartx_crash
3. Restart multipathd service
4. run the testcase
    Execute: service multipathd restart
  ./runtest.sh
4. multipathd remove invalid device name 'foo'
    Execute: multipathd remove map foo
5. check whether the return value is 'ok' or 'fail'
|results=
|results=
# The testcase should pass without any error introduced.
# multipathd responds with 'fail' for invalid device name.
}}
}}
[[Category:package_device-mapper-multipath_test_cases]]
[[Category:package_device-mapper-multipath_test_cases]]

Latest revision as of 10:35, 29 October 2018

QA.png


Description

This testcase checks if multipathd responds with 'fail' for invalid device name. It is reported in fixed bug that multipathd responds with 'ok' for invalid device name.


How to test

1. Ensure the device-mapper-multipath package is installed

   Execute: dnf -y install device-mapper device-mapper-multipath
   Execute: rpm -qa | grep multipath

2. Execute the following command to generate the configuration file

   Execute: mpathconf --enable

3. Restart multipathd service

   Execute: service multipathd restart

4. multipathd remove invalid device name 'foo'

   Execute: multipathd remove map foo

5. check whether the return value is 'ok' or 'fail'

Expected Results

  1. multipathd responds with 'fail' for invalid device name.