This makes sense too. Martin ----- "Hans de Goede" <hdegoede@xxxxxxxxxx> wrote: > While doing some tests with iscsi and kickstart I noticed that > currently > drives discovered through ibft (iscsi), edd (fcoe), or configured in > the > rclinux script (zfcp), can not be used in kickstart's clearpart or > ignoredrive commands. This patches fixes this. > > Note that the 3 added startup calls or complete no-ops on systems > without > ibft / edd-fcoe info / pre configured zfcp. > --- > kickstart.py | 6 ++++++ > 1 files changed, 6 insertions(+), 0 deletions(-) > > diff --git a/kickstart.py b/kickstart.py > index dd7278d..189e287 100644 > --- a/kickstart.py > +++ b/kickstart.py > @@ -1201,6 +1201,12 @@ def parseKickstart(anaconda, file): > > # We need this so all the /dev/disk/* stuff is set up before > parsing. > udev_trigger(subsystem="block") > + # So that drives onlined by these can be used in the ks file > + anaconda.id.storage.iscsi.startup(anaconda.intf) > + anaconda.id.storage.fcoe.startup(anaconda.intf) > + anaconda.id.storage.zfcp.startup() > + # Note we do NOT call dasd.startup() here, that does not online > drives, but > + # only checks if they need formatting, which requires zerombr to > be known > > try: > ksparser.readKickstart(file) > -- > 1.6.5.2 > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
