openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #17712
Re: Possible upgrade bug in nova-volume (& cinder)?
On Wed, Oct 24, 2012 at 12:57 PM, Jonathan Proulx <jon@xxxxxxxxxxxxx> wrote:
> On Wed, Oct 24, 2012 at 2:45 PM, Jonathan Proulx <jon@xxxxxxxxxxxxx>
> wrote:
>
> > To fix this for me I can look up the volumes by ID in the database and
> > then lvrename the logical volumes (I don't have too many and all on
> > one volume server right now).
>
> That maybe the wrong answer as the database (both cinder and the older
> nova leavings) has a provider_location that implies the "right"
> logical volume name:
>
>
> +--------------------------------------+--------+-----------------------------------------------------------------------------------------------+
> | id | ec2_id | provider_location
>
> |
>
> +--------------------------------------+--------+-----------------------------------------------------------------------------------------------+
> | 25cb6abc-1938-41da-b4a4-7639fa122117 | NULL | 128.52.x.x:3260,9
> iqn.2010-10.org.openstack:volume-0000001c 1
> |
> | 60cd2c0e-6d61-4010-aee2-df738adb3581 | NULL | 128.52.x.x:3260,4
> iqn.2010-10.org.openstack:volume-0000001a 1
> |
> | 67ba5863-9f92-4694-b639-6c9520e0c6f3 | NULL | 128.52.x.x:3260,2
> iqn.2010-10.org.openstack:volume-00000016 1
> |
> | 7397daa1-f4a7-47d4-b0dc-0b306defdf62 | NULL | 128.52.x.x:3260,14
> iqn.2010-10.org.openstack:volume-00000014 1
> |
> | 7d8c51bc-9cac-4edf-b1e6-1c37d5a8256f | NULL | 128.52.x.x:3260,10
> iqn.2010-10.org.openstack:volume-7d8c51bc-9cac-4edf-b1e6-1c37d5a8256f
> 1 |
> | 86426e77-e396-489d-9e66-49f0beef46bb | NULL | 128.52.x.x:3260,16
> iqn.2010-10.org.openstack:volume-00000019 1
> |
> | 98ac28f5-77d8-476b-b3e1-c90a0fd3e880 | NULL | 128.52.x.x:3260,1
> iqn.2010-10.org.openstack:volume-00000010 1
> |
> | a6e68eae-23a9-483e-bd42-e4b8a7f47dc4 | NULL | 128.52.x.x:3260,24
> iqn.2010-10.org.openstack:volume-a6e68eae-23a9-483e-bd42-e4b8a7f47dc4
> 1 |
> | a89b9891-571c-43be-bc1b-0c346a161d38 | NULL | 128.52.x.x:3260,9
> iqn.2010-10.org.openstack:volume-a89b9891-571c-43be-bc1b-0c346a161d38
> 1 |
> | cbd32221-7794-41d1-abf2-623c49f4ff03 | NULL | 128.52.x.x:3260,6
> iqn.2010-10.org.openstack:volume-0000001b 1
> |
>
> +--------------------------------------+--------+-----------------------------------------------------------------------------------------------+
>
> so I'm also open to suggestions on the "right" resolution to this.
> Should I rename the logical volume sand update the provider_location
> or should I make the /var/lib/cinder/volumes/* files match what is in
> the database and LVM (and if I do the latter will something come along
> and undo that)?
>
> -Jon
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
Hey Jon,
Couple of things going on, one is the volume naming (in progress here:
https://review.openstack.org/#/c/14615/). I'll take a closer look at some
of the other issues you pointed out.
Thanks,
John
Follow ups
References