Shared filesystem management project for OpenStack.
ba3088c4ee
The test test_add_access_rule_on_share_with_no_host in
manila_tempest_tests.tests.api.test_rules_negative\
.ShareIpRulesForNFSNegativeTest
expects a share to fail to schedule, and then validates that an
access rule cannot be added. However, the share may
still be 'creating' when the access change is being
attempted.
While the test passes (access rules cannot be added when
the share status isn't 'available'), the intent of that particular
test is to ensure access rules cannot be added when the share has no
host.
This fixes the cleanup error that happens in consequence,
because we don't allow deleting shares that are in
'creating' state.
In the spirit of true black box testing, we should ensure that the
share fails to schedule before attempting this test.
Change-Id: Id150e0ef546ddfd40d97d9b1a54fd8ba23028720
Closes-Bug: #1661421
|
||
|---|---|---|
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc | ||
| install-guide/source | ||
| manila | ||
| manila_tempest_tests | ||
| rally-jobs | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| babel.cfg | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| pylintrc | ||
| README.rst | ||
| requirements.txt | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
Team and repository tags
MANILA
You have come across an OpenStack shared file system service. It has identified itself as "Manila." It was abstracted from the Cinder project.
- Wiki: https://wiki.openstack.org/Manila
- Developer docs: http://docs.openstack.org/developer/manila
Getting Started
If you'd like to run from the master branch, you can clone the git repo:
git clone https://github.com/openstack/manila.git
For developer information please see HACKING.rst
You can raise bugs here http://bugs.launchpad.net/manila