[Spacewalk-list] Kickstarter - multiple problems?

[Lachlan Musicman]

Thanks Jonathan

On 10 March 2016 at 23:55, Jonathan Hoser <
jonathan.hoser at helmholtz-muenchen.de> wrote:

> Hi Lachlan,
>
> On 03/10/2016 06:34 AM, Lachlan Musicman wrote:
>
> We are having trouble with Cobbler/Kickstarter on Cisco M-Series servers.
>
> Spacewalk 2.4.x , running on Centos 7 7.2.1511
> According to Spacewalk, the Cobbler installed are:
> cobbler20-2.0.11-52.el7
> cobbler2-2.0.11-52.el7
> cobbler-loaders-1.0.3-1.el7
>
> Partly my own ignorance, but there are some things I would like to check
> with you all:
>
>  - the Cisco servers need a special Cisco SCSI disk driver installed into
> the kernel to see the LUN. I've added dd to the boot directives and it
> doesn't look in the right place? It only offers the opportunity for
> /dev/sr1 which is labelled Cobbler Install.
>
> Under kickstart details->advanced options we have
>
> driverdisk: --source=
> http://ISOSERVER/isos/driver_disk/dd-snic-0.0.1.22-1-centos-3.10.0-229.el7.img
>
> (we had the url raw, but I noticed in the resulting ks that the --source=
> wasn't included, and following the documentation here:
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html
> apparently that needs to be part of the command)
>
> that should work, I remember doing just that.
>


Unfortunately it doesn't. I guess I would like two points of clarification:

 - does the driverdisk apply to whatever is initially booting (the cobbler
image)? Because if *that* can't see the LUNs, then it wont be able to
install the system on those LUNs.
 - if the driverdisk is meant to work on the cobbler image, it isn't. How
might I get it to do so.

Alternatively, how do I inject the drivers into the cobbler image that
bootstraps the installation?


 - Finally the installation fails properly because it can't find /,
> presumably because without the device driver in the kernel, it can't see
> the SCSI drive onto which it should be installing itself.
>
> If I get into a terminal (ctl-alt-f2), I can't see the drives, and
> lsmod/dmesg confirm the driver isn't loaded.
>
> What am I doing wrong? Does the driver need to be in teh cobbler image
> rather than the kickstarter?
>
>

This feeds into my comment above - the booting system can't see the drive
that needs to be partitioned!

The way we got systems booting in the first place was to make a live cd
with the snic modules already installed in the kernel.

Reading the cobbler quickstart (
http://cobbler.github.io/manuals/quickstart/ ) this suggests that a live cd
shouldn't be used - only a full DVD.

Is that true?

cheers
L.


------
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20160311/0d89db58/attachment.htm>