[2.2] MAAS renames VGname back to vg0

[Write0nly]

1- Using MAAS from PPA on 16.04

ubuntu@maas:~$ dpkg -l | grep -i maas
ii maas 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all MAAS client and command-line interface
ii maas-common 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all Region Controller for MAAS
ii python3-django-maas 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.2.0~rc4+bzr6048-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)

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

[Write0nly (write0nly)]

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';
UPDATE 1
maasdb=# select group_type,name from maasserver_filesystemgroup;
 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

[Björn Tillenius (bjornt)]

Confirmed. The volume group name doesn't seem to get saved to the database when editing it.

[Adam Collard (adam-collard)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team