Devstack Install Fails with the error: Unable to add physical volume '/dev/loop2' to volume group 'stack-volumes-lvmdriver-1'.

Bug #1453899 reported by Amogh
48
This bug affects 11 people
Affects Status Importance Assigned to Milestone
devstack
Expired
Undecided
Unassigned

Bug Description

Devstack Install Fails with the error: Unable to add physical volume '/dev/loop2' to volume group 'stack-volumes-lvmdriver-1'.

Ubuntu: Ubuntu 14.04.2 LTS
uname -a:
Linux amogh-VirtualBox 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:56:26 UTC 2014 i686 i686 i686 GNU/Linux

Install log attached.

Revision history for this message
Amogh (amogh-r-mavinagidad) wrote :
Revision history for this message
Zhenguo Niu (niu-zglinux) wrote :

that's because the global_filter in /etc/lvm/lvm.conf, as a workaround you can manually add loop2 to filter dict.

Changed in devstack:
status: New → Confirmed
Revision history for this message
Zhenzan Zhou (zhenzan-zhou) wrote :

Do you know who occupied /dev/loop0 and /dev/loop1? It seems that your previous devstack install added loop0 and loop1 in /etc/lvm/lvm.conf but not cleaned. And this run of stack.sh is trying to use loop2.

Revision history for this message
Amogh (amogh-r-mavinagidad) wrote :

Thanks Zhenzan Zhou (zhenzan-zhou)
./clean.sh does not clean every thing from previous install?

Revision history for this message
Zhenzan Zhou (zhenzan-zhou) wrote :

From your log, /dev/loop0 is used by someone else, so the first VG uses /dev/loop1 and the second uses /dev/loop2. Please notice the WARNNING, you should check /etc/lvm/lvm.conf, find out global_filter and check its value. Normally after a successful install, it should have such line:

global_filter = [ "a|loop0|", "a|loop1|", "r|.*|" ] # from devstack

clean.sh should remove this line but something bad may happen.

From your log:

+ [[ -f /opt/stack/data/stack-volumes-default-backing-file ]]
++ sudo losetup -f --show /opt/stack/data/stack-volumes-default-backing-file
+ local vg_dev=/dev/loop1
+ sudo vgs stack-volumes-default
  WARNING: Ignoring duplicate config node: global_filter (seeking global_filter)
...
  VG #PV #LV #SN Attr VSize VFree
  stack-volumes-default 1 0 0 wz--n- 10.01g 10.01g
...
+ sudo vgs stack-volumes-lvmdriver-1
  WARNING: Ignoring duplicate config node: global_filter (seeking global_filter)

Changed in devstack:
assignee: nobody → Zhenzan Zhou (zhenzan-zhou)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (master)

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

Changed in devstack:
assignee: Zhenzan Zhou (zhenzan-zhou) → fengchaoyang (fengchaoyang)
status: Confirmed → In Progress
Revision history for this message
Trevor McCasland (twm2016) wrote :

I just want to put my two cents on this. I have found the ./clean.sh script will fix the issue only if you specify DEFAULT_VOLUME_GROUP_NAME=stack-volumes-default in your local.conf

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on devstack (master)

Change abandoned by fengchaoyang (<email address hidden>) on branch: master
Review: https://review.openstack.org/401265

Revision history for this message
Sean Dague (sdague) wrote :

No open reviews found in this bug, unassigning. Please add a comment with active reviews before assigning an individual, or tag the bug in the gerrit review, which will do that automatically. We try not to assign bugs without patches as that discourages other folks from looking into bugs.

Changed in devstack:
assignee: fengchaoyang (fengchaoyang) → nobody
status: In Progress → New
Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

If the issue still exists, please provide steps to reproduce.

Changed in devstack:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for devstack because there has been no activity for 60 days.]

Changed in devstack:
status: Incomplete → Expired
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.