Red Hat Bugzilla – Bug 1276333
Anaconda crashes upon probing iSCSI LUN with existing LVM structures
Last modified: 2015-10-30 08:48:33 EDT
Created attachment 1087478 [details]
Description of problem:
If an exported iSCSI LUN already contains LVM labels which match those autogenerated by the guided partitioning system, Anaconda will crash and the host will reboot when you attempt to probe the LUN (immediately after clicking "Login" at the iSCSI target selection window).
This could feasibly be encountered any time a user decides to perform a clean install, the installer should recognize the existing LVM volume group and either handle overwriting it, or alert the user to its existence.
Version-Release number of selected component (if applicable):
anaconda: /sbin/anaconda 23.19.10-1
Steps to Reproduce:
1. Install Fedora in a /boot on local | root on SAN iSCSI config with default guided partitioning.
2. Attempt to repeat the process without first wiping the exported LUN.
Anaconda crashes upon logging into the target and probing LUNs.
Anaconda should recognise and handle the old LVM volume group.
Please attach the other logs from /tmp at the time of this crash, in particular /tmp/anaconda-tb*
Created attachment 1087481 [details]
Created attachment 1087482 [details]
There are no files matching that criteria in /tmp, only /tmp/anaconda.log
I will attach the other logs although I believe them unrelated.
Created attachment 1087512 [details]
Created attachment 1087526 [details]
Proposed as a Blocker for 23-final by Fedora user bradfirj using the blocker tracking app because:
I believe this bug violates the "Network attached storage" blocker criteria:
The installer must be able to detect (if possible) and install to supported network-attached storage devices.
Supported network-attached storage types include iSCSI, Fibre Channel and Fibre Channel over Ethernet (FCoE).
Created attachment 1087544 [details]
Created attachment 1087546 [details]
Created attachment 1087547 [details]
Created attachment 1087548 [details]
Created attachment 1087549 [details]
As noted in your initial comment, and in the traceback, you have more than LVM volume group with the same name: one on a localally attached disk, and one on a disk being attached via iSCSI. LVM cannot handle this situation. Normally if anaconda detects mutliple VGs with the same name it will display a dialog advising the user to manually correct the storage, but this dialog is not currently displayed when a volume group is added from network storage.
It's worth noting this only presents if we try and install to an iSCSI volume when there is already an LVM volume group on both the network LUN and the local disk.
It's therefore probably enough of an edge case not to block on it, apologies for the false alarm.
(In reply to Richard Bradfield from comment #14)
> It's worth noting this only presents if we try and install to an iSCSI
> volume when there is already an LVM volume group on both the network LUN and
> the local disk.
> It's therefore probably enough of an edge case not to block on it, apologies
> for the false alarm.
IE It requires at least two attempts (successful or not) at installing the OS before it can occur.
OK, based on the discussion summarized here, I'm firmly -1 blocker on this issue.
FWIW this is fixed in rawhide by https://github.com/rhinstaller/anaconda/commit/5da4ee6b8825c52d7a75dba2012aff2efa595c8b
Discussed at 2015-10-29 Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-2/2015-10-29/f23-final-go_no_go-meeting_2.2015-10-29-16.00.html . Rejected as a blocker on the basis that this is a fairly unusual corner case, does not constitute a violation of the criterion - in most cases, iSCSI installs will work OK.
Closing this since it will not be going into F23 and is already in rawhide.