fuel-plugin-cinder-kaminario/doc/plugin guide/source/troubleshooting.rst

Verification

Login into the controller node from the Fuel-master node:

1. Verify the status of cinder-volume service for Kaminario backend

   $ cinder service-list

   

2. Create a volume. Verify the volume and volume group from the Kaminario K2 all-flash array dashboard.

   $ cinder create --name volume 1

   

   

Note: The volume name is cv-<cinder-volume-id> and volume group name is cvg-<cinder-volume-id>.

3. Run the OpenStack Test Framework (OSTF). From the Fuel web UI:

   • Click the Health Check tab

     • Select the Select All checkbox
     • Click Run Tests.

   Note: The Kaminario Fuel plugin verification is mainly based on the Functional tests.

Troubleshooting

On failure of the verification of Kaminario Fuel plugin or any Cinder volume operations related to the Kaminario backend, check the following log files for identifying the root cause of the failure:

1. /var/log/cinder/cinder-volume.log
2. /var/log/cinder/cinder-api.log
3. /var/log/cinder/cinder-scheduler.log
4. /var/log/nova/nova-compute.log

Check the status of cinder volume service for Kaminario backend.

$ cinder service-list

The failures may be caused due to many possibilities, the following are few of them:

1. Kaminario rest-api version is less than 2.2.0.

2. Kaminario K2 all-flash array version is less than 5.8.

3. Data path between the Fuel nodes (having cinder and compute role) and the Kaminario K2 all-flash array is not present or inaccessible:

   

   

   

4. Management IP of the Kaminario backend is not correct or inaccessible from the Fuel node having the Cinder role.

5. Wrong credentials (username and password) used for the Kaminario backend.

6. Not using the Kaminario Fuel plugin configuration options for; creating volume type and setting default volume type.

7. No proper use of Kaminario Fuel plugin configuration options like Filter Function, Goodness Function, Scheduler weighers and Scheduler filters.

8. Others.