Re: install url trouble
by Harry Hoffman
You have a underscore instead of a hyphen in the kickstart output, no?
Tim Tassinari <tptass(a)yahoo.com> wrote:
>Tim,
>
>When I've seen this in the past it is usually because the network for the machine being kickstarted is either not setup or incorrect.
>
>I'd verify that the network information is correct and utilizing it without any routes that you can get to these media locations.
>
>-tim
>
>On Jun 14, 2011, at 11:33 PM, Tim Dunphy <bluethundr(a)jokefire.com> wrote:
>
>> hello list!
>>
>> I am having trouble with the install url portion of the kickstart file. The ks was working in the recent past and honestly I'm not sure what may have changed to break the darn thing.
>>
>> First is the mirror url I am attempting to use:
>>
>> ## use mirror to install
>> url --url http://mirror.trouble-free.net/centos/5.6/os/x86_64/
>>
>> Now if you pump that url into your browser you should see a viable installer location. But this is what happens in the installer:
>>
>> Welcome to CentOS
>>
>>
>> +-----------------+ HTTP Setup +------------------+
>> | |
>> | Please enter the following information: |
>> | |
>> | o the name or IP number of your Web server |
>> | o the directory on that server containing |
>> | CentOS for your architecture |
>> | |
>> | Web site name: mirror.trouble-free.net_ |
>> | CentOS directory: /centos/5.6/os/x86_64/__ |
>> | |
>> | +----+ +------+ |
>> | | OK | | Back | |
>> | +----+ +------+ |
>> | |
>> | |
>> +-------------------------------------------------+
>>
>>
>>
>> <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
>>
>>
>> Next I tried the NFS media I have used in the past without kickstart.
>>
>> # Use NFS installation media
>> nfs --server=192.168.1.250 --dir=/mnt/DVD
>>
>>
>> Now with this I can type the appropriate command on the command line and have it mount:
>>
>> [root@LCENT03:~] #mount 192.168.1.250:/mnt/DVD /mnt/DVD
>> [root@LCENT03:~] #cd /mnt/DVD
>> [root@LCENT03:/mnt/DVD] #ls
>> CentOS RELEASE-NOTES-cs RELEASE-NOTES-en_US RELEASE-NOTES-ja RELEASE-NOTES-ro
>> EULA RELEASE-NOTES-cs.html RELEASE-NOTES-en_US.html RELEASE-NOTES-ja.html RELEASE-NOTES-ro.html
>> GPL RELEASE-NOTES-de RELEASE-NOTES-es RELEASE-NOTES-nl repodata
>> images RELEASE-NOTES-de.html RELEASE-NOTES-es.html RELEASE-NOTES-nl.html RPM-GPG-KEY-beta
>> isolinux RELEASE-NOTES-en RELEASE-NOTES-fr RELEASE-NOTES-pt_BR RPM-GPG-KEY-CentOS-5
>> NOTES RELEASE-NOTES-en.html RELEASE-NOTES-fr.html RELEASE-NOTES-pt_BR.html TRANS.TBL
>>
>>
>> But in the installer this is what happens:
>>
>> Welcome to CentOS
>>
>> +----------------------+ NFS Setup +----------------------+
>> | |
>> | Please enter the following information: |
>> | |
>> | o the name or IP number of your NFS server |
>> | o the directory on that server containing |
>> | CentOS for your architecture |
>> | o optionally, parameters for the NFS mount |
>> | |
>> | NFS server name: 192.168.1.250___________ |
>> | CentOS directory: /mnt/DVD________________ |
>> | NFS mount options (optional): ________________________ |
>> | |
>> | +----+ +------+ |
>> | | OK | | Back | |
>> | +----+ +------+ |
>> | |
>> | |
>> +---------------------------------------------------------+
>>
>>
>> <Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
>>
>> I'd really appreciate it if a fresh set of eyes could help spot the problem and possibly posit a solution.
>>
>> Thanks!
>> tim
>> _______________________________________________
>> cobbler mailing list
>> cobbler(a)lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/cobbler
>_______________________________________________
>cobbler mailing list
>cobbler(a)lists.fedorahosted.org
>https://fedorahosted.org/mailman/listinfo/cobbler
>
12 years, 10 months
fetchable_files, boot_files, and VMWare.
by Douglas Kilpatrick
The vmware support patch started using the field "fetchable_files" to
add some files to be copied into /tftpboot by sync. (Well, by a
post-sync trigger, but that's slightly different issue). Unfortunately,
if you're using fetchable_files for the reason I originally envisioned,
the trigger will likely blow up.
I added fetchable_files to handle tftp clients that requested hardcoded
paths. For example, FreeBSDs pxeboot client looks for
"/boot/mfsroot.gz". The fetchable_files support is required to sanely
support multiple versions of FreeBSD.
The VMWare import module uses it differently. It looks like the VMWare
module is using it to list additional files that need to be copied into
/tftpboot to support VMWare, beyond just the two that cobbler already
supports (kernel,initrd).
The VMWare import patch added two triggers: one post sync, the other
post distro-add to copy files in fetchable_files into /tftpboot.
From the perspective of the python tftp server, that's not a problem.
So there are some bad paths in fetchable files: that's ok. We'll just
never check them.
However, the new triggers can't really handle fetchable_files being used
for the original use case. The copy fails.
I think the use case that the VMWare module has is a very rational use
case. I just don't think it's the appropriate use case for
fetchable_files. So I'd like to propose a new field: "boot_files".
I've got a couple of proposed patches on my github tree
(https://github.com/kilpatds/cobbler/commits/master). At the commit
history on the tree, both changes are were made on May 26th.
https://github.com/kilpatds/cobbler/commit/24a531ea4943848598e8774aff408d...
is the change that adds the boot_files field.
https://github.com/kilpatds/cobbler/commit/5b90509288d09bf337c7e14de780f0...
changes the sync/add triggers to use it.
(The change on the 30th refactors things to get rid of the triggers:
move the copy logic over to sync/litesync. But I'm not done testing that)
Comments? Commentary? Requests for "TL;DR" blocks?
Doug
--
Doug Kilpatrick
kilpatds(a)oppositelock.org
12 years, 10 months
endraw doesn't end raw processing
by petermity
In Cobbler V2.0.10, within a given kickstart file or snippet, a
raw block does not seem to actually terminate with endraw.
Example kickstart:
# Kickstart to show raw/endraw bug
#set global $test1 = "abc"
somesetting1 $test1
#raw
somerawsetting1 $test1
#endraw
#set global $test2 = "def"
somesetting2 $test2
Results of doing "cobbler profile getks" for the profile specifying
that kickstart:
# Kickstart to show raw/endraw bug
somesetting1 abc
somerawsetting1 $test1
#endraw
#set global $test2 = "def"
somesetting2 $test2
That last line should be showing the value of the test2 variable,
not the literal line.
The workaround is to split into multiple files - EOF always seems
to terminate the raw block. But this seems like a bug that
should be fixed.
12 years, 11 months
Child Profile Explanation
by Briggs, Lee
Hi,
We've been using cobbler here for a while, but in the web UI there's a button that's been bugging me. That little "Add Child" button in the profiles section.
Now I've been doing some reading about what this does and haven't got a satisfactory answer. What I'm hoping it does it this:
I create a profile, let's called it Master. Now this master profile contains the main configs for our cluster. However, we also have site specific profiles, such as location A and location B. Previously, this would be 3 separate profiles, but, can we create a master profile and then make location A and location B child profiles of Master, where location A will get all of Master's snippets, kickstarts, configs etc?
If that's not how it works, can someone provide me a use case of these child profiles!?
Regards,
Lee
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.
12 years, 11 months