teardown.sh does not cleanup lvm.conf
Bug #1479870 reported by
David Wilde
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Won't Fix
|
Wishlist
|
David Wilde |
Bug Description
In an AIO we are dropping a new lvm.conf that filters out all block devices. Since this file is not removed the bootstrap-aio.sh script will fail on subsequent runs if new block devices are added.
Steps to reproduce:
1) Create a cloud server and run an aio build
2) Run scripts/teardown.sh
3) Add a block device to the cloud server
4) Run scripts/
This will fail with something like the following:
+ pvcreate -ff -y /dev/xvdb1
Device /dev/xvdb1 not found (or ignored by filtering)
We should replace /etc/lvm/lvm.conf with the backup file created during the ansible run.
Changed in openstack-ansible: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
Changed in openstack-ansible: | |
assignee: | nobody → David Wilde (david-wilde-rackspace) |
milestone: | none → liberty-3 |
Changed in openstack-ansible: | |
milestone: | liberty-3 → 12.0.0 |
Changed in openstack-ansible: | |
milestone: | 12.0.0 → 12.1.0 |
Changed in openstack-ansible: | |
status: | In Progress → Won't Fix |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/217827
Review: https:/