[Bug 1817422] Re: "vg0 is not a valid name for a volume group" if VG already exists

2020-03-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: subiquity (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817422

Title:
  "vg0 is not a valid name for a volume group" if VG already exists

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1817422/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1817422] Re: "vg0 is not a valid name for a volume group" if VG already exists

2019-02-23 Thread Michael Hudson-Doyle
Yeah, I've hit this too. As with everything else, the "reusing existing
partitions" work is the answer, because that will include probing for
existing LVM/mdraid/etc devices.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817422

Title:
  "vg0 is not a valid name for a volume group" if VG already exists

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1817422/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs