power9 install, trouble removing old lvm config

Bug #1872783 reported by Seth Arnold
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
The Ubuntu-power-systems project
Fix Released
High
Canonical Foundations Team
curtin
Fix Released
Undecided
Unassigned
subiquity
Fix Released
Undecided
Unassigned

Bug Description

Hello, I believe my previous bug may have been addressed:
https://bugs.launchpad.net/subiquity/+bug/1861369

However, the installer now appears to be stuck trying to remove LVM configs left over from previous installs. The python portions are just stuck doing repeated epolls, and there's no mechanism to force an error report at that point in the install, so all I've got are some photos.

Thanks

Revision history for this message
Seth Arnold (seth-arnold) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote :
Revision history for this message
Frank Heimes (fheimes) wrote :

The error messages look partially familiar.
It might be a duplicate of LP 1870037 and or LP 1869075.
@Ryan, can you confirm that this is a duplicate?

tags: added: installer ppc64el
Changed in ubuntu-power-systems:
importance: Undecided → High
assignee: nobody → Canonical Foundations Team (canonical-foundations)
no longer affects: subiquity (Ubuntu)
Changed in ubuntu-power-systems:
status: New → Triaged
Revision history for this message
Ryan Harper (raharper) wrote :

is this system multipathed?

@Frank
I can't tell if it's either at this point.

Changed in curtin:
status: New → Incomplete
Revision history for this message
Frank Heimes (fheimes) wrote :

@Seth, would you mind attaching the logs to the ticket for further analysis - ideally complete /var/log?

Revision history for this message
Seth Arnold (seth-arnold) wrote : Re: [Bug 1872783] Re: power9 install, trouble removing old lvm config

On Tue, Apr 14, 2020 at 07:11:20PM -0000, Ryan Harper wrote:
> is this system multipathed?

No multipath on this sysstem, it's a single nvme drive.

I'll try to grab some logs.

Thanks

Revision history for this message
Seth Arnold (seth-arnold) wrote :

Unfortunately several attempts to reproduce this didn't work. I'm sorry.

Revision history for this message
Andrew Cloke (andrew-cloke) wrote :

As this issue cannot be reproduced, and we know that the NVMe issue has been addressed.
I'm assuming that it has been fixed in one of the subiquity updates. Marking as "fix released".
If this issue reoccurs, please re-open this bug.

Changed in ubuntu-power-systems:
status: Triaged → Fix Released
Changed in curtin:
status: Incomplete → Fix Released
Changed in subiquity:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.