On 05/31/2012 06:49 PM, Brian C. Lane wrote:
On Thu, May 31, 2012 at 11:12:52AM +0200, Radek Vykydal wrote:
These kind of devices, when qla4xxx.ql4xdisablesysfsboot=1,
is discovered by anaconda/udev as iscsi device yet it can not
be handled by iscsiadm so we need to treat it specially.
Resolves: rhbz#823810
The comments mention qla4xxx but nothing checks for that, it depends
on the node being None. Is there other hardware that could also trigger
this condition that would need to be handled differently?
There is no such other hardware. Having iscsi device in tree
without Node discovered and managed by anaconda/iscsiadm
is something new that qla4xxx in firmware boot mode requires.
I was thinking about adding some attribute or property to
iSCSIDiskDevice so that the conditions in some places
(generating dracut arguments, modifying ifcfg files) are more clear
but I'd like to do it also for some other cases and
I want to keep this post-RC 6.3 patch as safe as possible.
Perhaps the comment can be improved, what about
# qla4xxx in firmware boot mode (#823810)
Radek
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
