iscsid container fails to start on storage node
Bug #1629381 reported by
Mark Duggan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
When the iscsid containers is included in the kolla deployment it starts successfully on a compute node but fails to start on a storage node, if cinder is enabled because the config file is not copied to the container.
If cinder is not enabled the iscsid container starts successfully on both the compute and storage nodes. A previous fix was submitted for the case where cinder was not enabled - https:/
| Changed in kolla: | |
| milestone: | none → newton-rc2 |
| importance: | Undecided → Critical |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to kolla (master) | #1 |
| Changed in kolla: | |
| status: | New → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kolla 3.0.0.0rc2 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 74c85cfe822638a
Author: Mark Duggan <email address hidden>
Date: Mon Oct 3 15:46:35 2016 +0100
Iscsid container fails to start on storage node when cinder is enabled
When the iscsid containers is included in the kolla deployment it starts
successfully on a compute node but fails to start on a storage node, if
cinder is enabled because the config file is not copied to the container
BTW, if cinder is not enabled the iscsid container starts successfully
on both the compute and storage nodes.
Change-Id: I665535d858affe
Closes-Bug: #1629381