Open Stack

Hi,

> What do you mean by "updating the respective table"? The optimal way
> to update a volume with a volume type is:
> 1) create a volume type pointing to the backend in which the volume
> currently is
> 2) retype the volume to that volume type

I know that one can retype an existing volume but in my case we were  
in the middle of a migration of the whole cloud environment, so the  
services were not up yet while the old control node was already  
shutdown. So I had to update the cinder table directly in the database  
in order to get cinder services up.

> The functionality to delete the __DEFAULT__ type is only available since
> cinder train >= 15.4.0
> (See the releasenotes for more info regarding the __DEFAULT__ type[1])
> Also you need to have a valid value defined with ``default_volume_type`` in
> cinder.conf
> Let me know if you have respective settings and still not able to delete
> the __DEFAULT__ type.

I haven't tried to delete it yet since we still have active volumes in  
our environment. I will start to retype them one by one before  
deleting the __DEFAULT__ type, but that may take a while.

Thanks!
Eugen


Zitat von Rajat Dhasmana <rdhasman at redhat.com>:

> Sorry i forgot to include openstack discuss mailing list with my reply.
>
> ---------- Forwarded message ---------
> From: Rajat Dhasmana <rdhasman at redhat.com>
> Date: Sun, Oct 18, 2020 at 1:06 PM
> Subject: Re: [ops] [cinder] __DEFAULT__ volume type
> To: Eugen Block <eblock at nde.ag>
>
>
> Hi Eugen,
>
> On Sun, Oct 18, 2020 at 12:54 PM Eugen Block <eblock at nde.ag> wrote:
>
>> Hi,
>>
>> I also was confused about that during our upgrade to Train. I noticed
>> that many volumes in our cloud didn't have any volume type defined at
>> all, so I had to update the respective table before I could continue
>> the upgrade process.
>
>
> What do you mean by "updating the respective table"? The optimal way
> to update a volume with a volume type is:
> 1) create a volume type pointing to the backend in which the volume
> currently is
> 2) retype the volume to that volume type
>
>
>> I have also defined a different volume type in
>> cinder.conf but I don't think you can just delete the __DEFAULT__
>> type,
>
>
> The functionality to delete the __DEFAULT__ type is only available since
> cinder train >= 15.4.0
> (See the releasenotes for more info regarding the __DEFAULT__ type[1])
> Also you need to have a valid value defined with ``default_volume_type`` in
> cinder.conf
> Let me know if you have respective settings and still not able to delete
> the __DEFAULT__ type.
>
>
>> I'm not sure anymore but I think I also tried that. But it
>> doesn't really hurt if you have one of your own types as default.
>>
>> Regards,
>> Eugen
>>
>>
> [1]
> https://docs.openstack.org/releasenotes/cinder/train.html#relnotes-15-4-0-stable-train-bug-fixes
>
> Regards
> Rajat Dhasmana