manila access-allow doesn't appear to properly handle 0.0.0.0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
High
|
Thomas Bechtold |
Bug Description
Manila setup with default driver, see here from manila.conf.
[generic1]
driver_
service_
service_image_name = manila-
path_to_private_key = /home/amrith/
path_to_public_key = /home/amrith/
share_backend_name = GENERIC1
share_driver = manila.
service_
[generic2]
driver_
service_
service_image_name = manila-
path_to_private_key = /home/amrith/
path_to_public_key = /home/amrith/
share_backend_name = GENERIC2
share_driver = manila.
service_
Look ma, no share.
amrith@
+----+-
| ID | Name | Size | Share Proto | Status | Is Public | Share Type Name | Host | Availability Zone |
+----+-
+----+-
=== Here's a share ===
amrith@
+------
| Property | Value |
+------
| status | creating |
| share_type_name | default |
| description | None |
| availability_zone | None |
| share_network_id | 7a9c3dc6-
| share_server_id | None |
| host | |
| access_rules_status | active |
| snapshot_id | None |
| is_public | False |
| task_state | None |
| snapshot_support | True |
| id | 6d28ec08-
| size | 3 |
| name | manila-share |
| share_type | dfeba8fc-
| has_replicas | False |
| replication_type | None |
| created_at | 2016-03-
| share_proto | NFS |
| consistency_
| source_
| project_id | 391a288e0dff4df
| metadata | {} |
+------
=== Yup, it's there ===
amrith@
+------
| Property | Value |
+------
| status | available |
| share_type_name | default |
| description | None |
| availability_zone | nova |
| share_network_id | 7a9c3dc6-
| export_locations | |
| | uuid = ae256cfe-
| | created_at = 2016-03-
| | updated_at = 2016-03-
| | is_admin_only = False |
| | share_instance_id = bfe39581-
| | path = 10.0.0.
| share_server_id | 0027c61c-
| host | amrith-
| access_rules_status | active |
| snapshot_id | None |
| is_public | False |
| task_state | None |
| snapshot_support | True |
| id | 6d28ec08-
| size | 3 |
| name | manila-share |
| share_type | dfeba8fc-
| has_replicas | False |
| replication_type | None |
| created_at | 2016-03-
| share_proto | NFS |
| consistency_
| source_
| project_id | 391a288e0dff4df
| metadata | {} |
+------
=== Let's grant access ===
amrith@
+------
| Property | Value |
+------
| share_id | 6d28ec08-
| access_type | ip |
| access_to | 0.0.0.0/0 |
| access_level | rw |
| state | new |
| id | ba63be56-
+------
amrith@
mount.nfs: access denied by server while mounting 10.0.0.
==== But, can't mount it ... ====
==== Let's try this ====
amrith@
| Property | Value |
+------
| share_id | 6d28ec08-
| access_type | ip |
| access_to | 10.0.0.0/24 |
| access_level | rw |
| state | new |
| id | 7837bca1-
+------
==== Did that work? ====
amrith@
amrith@
==== Sure it did =====
I believe that 0.0.0.0/0 is a good enough wildcard ...
description: | updated |
tags: | added: bugsmash-mitaka |
Changed in manila: | |
assignee: | nobody → Surya Ghatty (ghatty) |
Changed in manila: | |
milestone: | none → mitaka-rc1 |
importance: | Undecided → High |
Changed in manila: | |
assignee: | Surya Ghatty (ghatty) → Thomas Bechtold (toabctl) |
Fix proposed to branch: master /review. openstack. org/294140
Review: https:/