[2.2] MAAS renames VGname back to vg0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned | ||
2.2 |
Won't Fix
|
High
|
Unassigned |
Bug Description
1- Using MAAS from PPA on 16.04
ubuntu@maas:~$ dpkg -l | grep -i maas
ii maas 2.2.0~rc4+
ii maas-cli 2.2.0~rc4+
ii maas-common 2.2.0~rc4+
ii maas-dhcp 2.2.0~rc4+
ii maas-dns 2.2.0~rc4+
ii maas-proxy 2.2.0~rc4+
ii maas-rack-
ii maas-region-api 2.2.0~rc4+
ii maas-region-
ii python3-django-maas 2.2.0~rc4+
ii python3-maas-client 2.2.0~rc4+
ii python3-
2- On a system that is in READY state, go and modify the storage
2.1- Create a new partition
2.2- Click on the new partition and add a volume group (the name can't be chosen upon creation)
2.3- Click on the VG and edit the vg name, changing it to any string... in this case I set it to foo.
2.4- Add logical volumes, such as foo-root, foo-var, etc etc.
2.5- refresh the page, and notice that the VG went back to vg0
2.6- deploy the system and notice that the vg is called vg0
ubuntu@node1:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
vg0 1 3 0 wz--n- 446.16g 122.07g
description: | updated |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
Changed in maas: | |
milestone: | 2.3.x → 2.5.x |
For the record, it's simple to circumvent this by updating the vgname in postgres:
postgres=# \connect maasdb
You are now connected to database "maasdb" as user "postgres".
maasdb=# select group_type,name from maasserver_ filesystemgroup ;
group_type | name
------------+------
lvm-vg | vg0
(1 row)
maasdb=# update maasserver_ filesystemgroup SET name = 'foo' WHERE group_type = 'lvm-vg'; filesystemgroup ;
UPDATE 1
maasdb=# select group_type,name from maasserver_
group_type | name
------------+------
lvm-vg | foo
(1 row)
ubuntu@node1:~$ sudo vgs
VG #PV #LV #SN Attr VSize VFree
foo 1 3 0 wz--n- 446.16g 122.07g