unstack.sh fails with sed lvm.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Fix Released
|
Undecided
|
clayg |
Bug Description
unstack.sh seems to take great care to be idempotent and atomic.
But if you run unstack.sh on a fresh new system before you initially stack it [1] - you get the following no-zero exit:
+./unstack.
+lib/lvm:
+lib/lvm:
+lib/lvm:
+lib/lvm:
sudo: lvremove: command not found
++lib/lvm:
+lib/lvm:
+lib/lvm:
+lib/lvm:
+lib/lvm:
+lib/lvm:
+./unstack.
+lib/lvm:
sed: can't read /etc/lvm/lvm.conf: No such file or directory
I think this was mostly meant to be addressed by https:/
1. You can imagine that `unstack.sh && stack.sh` might always pass and result in a cleaned fresh stack regardless of if you're running that on a old setup or a fresh new box
Fix proposed to branch: master /review. openstack. org/364181
Review: https:/