Volume fails to become 'available' after detach
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Fix Released
|
High
|
Roman Podoliaka | ||
5.1.x |
Invalid
|
High
|
Sergii Rizvan | ||
6.0.x |
Fix Released
|
High
|
Alexander Nevenchannyy | ||
6.1.x |
Fix Committed
|
High
|
Roman Podoliaka | ||
7.0.x |
Fix Released
|
High
|
MOS Nova |
Bug Description
Corresponding upstream bug: https:/
api: '1.0'
astute_sha: 055b2d82fe8499b
auth_required: true
build_id: 2015-04-16_21-30-10
build_number: '317'
feature_groups:
- mirantis
fuellib_sha: db5f39e96e7ab9f
fuelmain_sha: 0de2d2039e76839
nailgun_sha: 52d92c86e68602f
openstack_version: 2014.2-6.1
ostf_sha: b0991dbad159f53
production: docker
python-
release: '6.1'
Successfully deployed the following configuration:
Baremetal,
Controllers:3 Computes:47
We performed
During rally create_
rally.log:
http://
request to detaching was sent to node-1:
messages:
http://
from nova-all.log:
http://
diagnostic snapshot is here: http://
Changed in mos: | |
status: | New → Confirmed |
Changed in mos: | |
importance: | Medium → High |
description: | updated |
tags: | added: support |
no longer affects: | mos/8.0.x |
here is rally log of this scenario