openstack/manila
Code Issues Proposed changes
40da25f286
manila/doc/source/admin/shared-file-systems-troubleshoot.rst
Tom Barron 2be2160ddb doc migration: admin guide 
Migrate the shared file systems documents from the
centralized Admin Guide as outlined in the migration
spec [1].

[1] https://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html

Partial-Bug: #1706181
Needed-By: Ibe3588c3f4560c037cf109058fc357234e70a846
Depends-On: Ieea33262101a1d2459492c1c8aaac5fe042279f6
Depends-On: Ia750cb049c0f53a234ea70ce1f2bbbb7a2aa9454

Change-Id: I7924d94b82e7c8d9716bad7a219fc38c57970773
2017-08-24 09:16:52 -04:00

3.0 KiB
Raw Blame History

Troubleshoot Shared File Systems service

Failures in Share File Systems service during a share creation

Problem

New shares can enter error state during the creation process.

Solution

  1. Make sure, that share services are running in debug mode. If the debug mode is not set, you will not get any tips from logs how to fix your issue.
  2. Find what share service holds a specified share. To do that, run command manila show <share_id_or_name> and find a share host in the output. Host uniquely identifies what share service holds the broken share.
  3. Look thought logs of this share service. Usually, it can be found at /etc/var/log/manila-share.log. This log should contain kind of traceback with extra information to help you to find the origin of issues.

No valid host was found

Problem

If a share type contains invalid extra specs, the scheduler will not be able to locate a valid host for the shares.

Solution

To diagnose this issue, make sure that scheduler service is running in debug mode. Try to create a new share and look for message Failed to schedule create_share: No valid host was found. in /etc/var/log/manila-scheduler.log.

To solve this issue look carefully through the list of extra specs in the share type, and the list of share services reported capabilities. Make sure that extra specs are pointed in the right way.

Created share is unreachable

Problem

By default, a new share does not have any active access rules.

Solution

To provide access to new share, you need to create appropriate access rule with the right value. The value must defines access.

Service becomes unavailable after upgrade

Problem

After upgrading the Shared File Systems service from version v1 to version v2.x, you must update the service endpoint in the OpenStack Identity service. Otherwise, the service may become unavailable.

Solution

  1. To get the service type related to the Shared File Systems service, run:

    # openstack endpoint list

# openstack endpoint show <share-service-type>

    You will get the endpoints expected from running the Shared File Systems service.

  2. Make sure that these endpoints are updated. Otherwise, delete the outdated endpoints and create new ones.

Failures during management of internal resources

Problem

The Shared File System service manages internal resources effectively. Administrators may need to manually adjust internal resources to handle failures.

Solution

Some drivers in the Shared File Systems service can create service entities, like servers and networks. If it is necessary, you can log in to project service and take manual control over it.