using tgt-admin --conf option creates false sense of security, volume attach still fails after tgtd restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Eoghan Glynn | ||
OpenStack Compute (nova) |
Fix Released
|
High
|
Eoghan Glynn |
Bug Description
In order to avoid problems with tgtd not knowing that it should pick up iscsi target configs from /etc/cinder/volumes (formerly /var/lib/
https:/
However this just creates a false sense of security, as problems arise if a volume is created before a tgtd restart and then we attempt to attach afterwards (on F17, this manifests as an iscsiadm login timeout).
It would be preferable to fail fast when the tgtd config is not correct from the get-go.
This would force users to correct their /etc/tgt/
sudo sed -i '1iinclude /etc/cinder/
instead of volumes appearing to work and then inexplicably failing after a tgtd restart.
This fail-fast behavior would be achieved by reverting the commit mentioned above.
Changed in nova: | |
assignee: | nobody → Eoghan Glynn (eglynn) |
tags: | added: folsom-rc-potential |
tags: | added: folsom-backport-potential |
Changed in nova: | |
importance: | Undecided → High |
Changed in cinder: | |
importance: | Undecided → High |
Changed in cinder: | |
milestone: | none → folsom-rc3 |
Changed in nova: | |
milestone: | none → folsom-rc3 |
tags: | removed: folsom-backport-potential folsom-rc-potential |
Changed in cinder: | |
milestone: | folsom-rc3 → 2012.2 |
Changed in nova: | |
milestone: | folsom-rc3 → 2012.2 |
Fix proposed to branch: master /review. openstack. org/13632
Review: https:/