** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905412
Title:
LVM install broken if other disks have meta-data on the
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2004
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905412
Title:
LVM install broken if other disks have meta-data on the
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Changed in: subiquity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Wed, 14 Apr 2021 at 21:52, Thierry FAUCK <1905...@bugs.launchpad.net>
wrote:
> I have tested the installation on multipath disk with LVM partition
> enabled - and it installed without any problem.
> However at reboot I got following messages but that could be related to
> other devices:
>
As such I think system is operational - and bug can be closed - if I
missed something let me know
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905412
Title:
LVM install broken if other disks have
I have tested the installation on multipath disk with LVM partition enabled -
and it installed without any problem.
However at reboot I got following messages but that could be related to other
devices:
Volume group "ubuntu-vg" not found
Cannot process volume group ubuntu-vg
[FAILED]
Oh that's yet another new bug, but a pretty simple one:
https://code.launchpad.net/~mwhudson/curtin/+git/curtin/+merge/401068
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905412
Title:
LVM
I today received a note from an IBMer who had issues to (re-)install an IBM Z
system with various DASD ECKD disks in a LVM configuration.
I was able to recreate the situation on our system and itis as follows:
more than 2 DASDs (used 8 DASD mod3) with:
dasda1 0.75 GB for /boot
dasda2 rest for a
** Attachment added: "12042021_2.tgz"
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1905412/+attachment/5486863/+files/12042021_2.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905412
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: curtin (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
** Changed in: ubuntu-z-systems
Assignee:
** Changed in: ubuntu-z-systems
Status: Confirmed => Fix Committed
** Changed in: ubuntu-power-systems
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: subiquity
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905412
Title:
LVM install broken if other disks have meta-data on the VG name
--- Comment From dougm...@us.ibm.com 2021-02-22 08:37 EDT---
Is this a regression? It's been a long time since I installed Ubuntu, but don't
recall any issues when installing multiple instances on a lab machine. Perhaps
I never chose LVM, though.
Other distros do ensure that the LVM
** Changed in: ubuntu-z-systems
Status: New => Confirmed
** Changed in: ubuntu-power-systems
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/1905412
Title:
LVM
** Changed in: curtin (Ubuntu)
Status: New => Confirmed
** Changed in: subiquity
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/1905412
Title:
LVM install
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905412
Title:
LVM install broken if other disks have meta-data on
One can make these things unambiguous.
curtin could generate a uuid on the fly, and then pass vg_uuid to all
the commands it uses.
or we could start making slightly more unique vg names, i.e. ubuntu-vg-
3a185.
I'm not sure what's best.
Indeed this is a long standing issue we have been
FYI I just looked at this system after installing with only one disk
enabled.
I found this which might be interesting for LVM handling:
#1 two LVMs with same name co-exist
$ sudo vgs -o vg_name,vg_uuid
VGVG UUID
ubuntu-vg
I think the issue here is that the guided lvm install always creates a
vg named ubuntu-vg -- even if there is already a vg with that name on
other disks. Installing over the top of the disk that has the ubuntu-vg
vg on it *ought* to work but I wouldn't be that surprised if it didn't.
--
You
** Tags added: fr-964
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905412
Title:
LVM install broken if other disks have meta-data on the VG name
already
To manage notifications about this bug
** Also affects: curtin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905412
Title:
LVM install broken if other disks have meta-data on the VG
** Description changed:
Hi,
- I was puzzled today at my install aborting until I was lookgin in the crash
file.
+ I was puzzled today at my install aborting until I was looking in the crash
file.
There I've found:
- Running command ['vgcreate', '--force', '--zero=y', '--yes', 'ubuntu-vg',
Even if I think that this is not s390x-specific, I'm marking this as
affecting s390x, since one bumped into this while doing an (LPAR)
install on s390x.
** Tags added: installer s390x
** Also affects: subiquity
Importance: Undecided
Status: New
** Also affects: ubuntu-z-systems
** Attachment added: "log as it was left in the installer environment"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1905412/+attachment/5437532/+files/1606223663.332479477.install_fail.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
24 matches
Mail list logo
