teardown.sh does not cleanup lvm.conf

Bug #1479870 reported by David Wilde
6
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/bootstrap-aio.sh

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
David Wilde (dave-wilde)
Changed in openstack-ansible:
assignee: nobody → David Wilde (david-wilde-rackspace)
milestone: none → liberty-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-ansible-deployment (master)

Fix proposed to branch: master
Review: https://review.openstack.org/217827

Changed in openstack-ansible:
status: Confirmed → In Progress
Changed in openstack-ansible:
milestone: liberty-3 → 12.0.0
Changed in openstack-ansible:
milestone: 12.0.0 → 12.1.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on openstack-ansible (master)

Change abandoned by Jesse Pretorius (<email address hidden>) on branch: master
Review: https://review.openstack.org/217827
Reason: This has been untouched for more than three months, so it's being abandoned. If you intend to work on it, then please restore it.

Changed in openstack-ansible:
status: In Progress → Won't Fix
Revision history for this message
Jesse Pretorius (jesse-pretorius) wrote :

Milestone will be re-added if/when a patch is submitted.

Changed in openstack-ansible:
milestone: 12.1.0 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.