[rhn-satellite-users] Dynamic URL in Kickstart File

[o***@bayerbbs.com]

Hi Folks,

my environment consists of one Satellite Server and two Proxy Servers. In
my kickstart profiles I am using the dynamic URL generation that results
in a kickstart file containing for example:

url --url http://<hostname>/ty/MHeBxXP1

Depending on which server I am asking (the Satellite or one of my two
Proxy server), e.g.
https://10.191.141.22/kickstart/ks/view_label/RHEL5-x86_64, <hostname> is
replaced by the FQDN of the server. I can remember that in the past
<hostname> was replaced by the IP address of the server (the one that I
specified in the HTTP request).

Unfortunatly I do not have DNS in all my network segments. The IP address
works better for me. Is it possible to prevent the kickstart generator
from resolving the IP address?

Mit freundlichen Grüßen / Best Regards

Oliver Fenker
_________________________________________

BBS-ITO-BDC-GSE-SSS

Bayer Business Services GmbH
Gebäude B151
51368 Leverkusen, Deutschland

Tel: [phone]
Fax: [phone]
E-Mail: ***@bayerbbs.com
Web: http://www.BayerBBS.com

Geschäftsführung: Vorsitzender Daniel Hartert | Arbeitsdirektor
Norbert Fieseler
Vorsitzender des Aufsichtsrats: Klaus Kühn
Sitz der Gesellschaft: Leverkusen | Amtsgericht Köln, HRB 49895

[Miroslav Suchý]

Post by o***@bayerbbs.com
Hi Folks,
my environment consists of one Satellite Server and two Proxy Servers.
In my kickstart profiles I am using the dynamic URL generation that
url --url http://<hostname>/ty/MHeBxXP1
Depending on which server I am asking (the Satellite or one of my two
Proxy server), e.g.
https://10.191.141.22/kickstart/ks/view_label/RHEL5-x86_64, <hostname>
is replaced by the FQDN of the server. I can remember that in the past
<hostname> was replaced by the IP address of the server (the one that I
specified in the HTTP request).

You mean that IP is replaced by FQDN in content of that KS?
Or that the request come from http://FQDN/... instead of http://IP/...,
which cause you problem in network setup?

[o***@bayerbbs.com]

Hello,

sorry for being imprecisely. What I'd like to achieve is that the url
option in the kickstart file uses the same address as given in the http
request, i.e. if I specify

ks=https://10.191.141.22/kickstart/ks/view_label/RHEL5-x86_64

then my kickstart file should contain

url --url http://10.191.141.22/ty/MHeBxXP1


and if I specify

ks=https://by-proxy.example.com/kickstart/ks/view_label/RHEL5-x86_64

then my kickstart file should contain

url --url http://by-proxy.example.com/ty/MHeBxXP1


At the moment the ks file I get from the ks generator always contains the
FQDN and that causes some trouble in network segments without DNS.

Post by Miroslav Suchý

Post by o***@bayerbbs.com
Hi Folks,
my environment consists of one Satellite Server and two Proxy Servers.
In my kickstart profiles I am using the dynamic URL generation that
url --url http://<hostname>/ty/MHeBxXP1
Depending on which server I am asking (the Satellite or one of my two
Proxy server), e.g.
https://10.191.141.22/kickstart/ks/view_label/RHEL5-x86_64, <hostname>
is replaced by the FQDN of the server. I can remember that in the

past

Post by Miroslav Suchý

Post by o***@bayerbbs.com
<hostname> was replaced by the IP address of the server (the one that

I

Post by Miroslav Suchý

Post by o***@bayerbbs.com
specified in the HTTP request).

You mean that IP is replaced by FQDN in content of that KS?
Or that the request come from http://FQDN/... instead of http://IP/...,
which cause you problem in network setup?
--
Miroslav Suchy
Red Hat Satellite Engineering

Mit freundlichen Grüßen / Best Regards

Oliver Fenker
_________________________________________

BBS-ITO-BDC-GSE-SSS

Bayer Business Services GmbH
Gebäude B151
51368 Leverkusen, Deutschland

Tel: [phone]
Fax: [phone]
E-Mail: ***@bayerbbs.com
Web: http://www.BayerBBS.com

Geschäftsführung: Vorsitzender Daniel Hartert | Arbeitsdirektor
Norbert Fieseler
Vorsitzender des Aufsichtsrats: Klaus Kühn
Sitz der Gesellschaft: Leverkusen | Amtsgericht Köln, HRB 49895

[Miroslav Suchý]

Post by o***@bayerbbs.com
Hello,
sorry for being imprecisely. What I'd like to achieve is that the url
option in the kickstart file uses the same address as given in the http
request, i.e. if I specify
ks=https://10.191.141.22/kickstart/ks/view_label/RHEL5-x86_64
then my kickstart file should contain
url --url http://10.191.141.22/ty/MHeBxXP1
and if I specify
ks=https://by-proxy.example.com/kickstart/ks/view_label/RHEL5-x86_64
then my kickstart file should contain
url --url http://by-proxy.example.com/ty/MHeBxXP1
At the moment the ks file I get from the ks generator always contains
the FQDN and that causes some trouble in network segments without DNS.

You may want to track:
https://bugzilla.redhat.com/show_bug.cgi?id=432058
https://bugzilla.redhat.com/show_bug.cgi?id=253274
Which are very similar and anyone of them will fix your problem. They
are in plan for next major release.

[o***@bayerbbs.com]

Hello,

Post by Miroslav Suchý
https://bugzilla.redhat.com/show_bug.cgi?id=432058
https://bugzilla.redhat.com/show_bug.cgi?id=253274
Which are very similar and anyone of them will fix your problem. They
are in plan for next major release.
--
Miroslav Suchy
Red Hat Satellite Engineering

Unfortunately I am not authorized to access those bugs :-( You are
stating that it will be fixed in the next major release that I guess will
not be available within the next months. We are currently unable to
kickstart new systems in some network segments due to this bug/feature. Is
there a workaround available? Otherwise I feel that I need to open a RH
support ticket for that as I cannot wait for the next major release.

Best Regards
Oliver Fenker

[Miroslav Suchý]

Post by o***@bayerbbs.com
Hello,

Post by Miroslav Suchý
https://bugzilla.redhat.com/show_bug.cgi?id=432058
https://bugzilla.redhat.com/show_bug.cgi?id=253274
Which are very similar and anyone of them will fix your problem. They
are in plan for next major release.
--
Miroslav Suchy
Red Hat Satellite Engineering

Unfortunately I am not authorized to access those bugs :-( You are

To summary: one is multihomed proxy and one to use proxy under CNAME.

Post by o***@bayerbbs.com
stating that it will be fixed in the next major release that I guess
will not be available within the next months. We are currently unable
to kickstart new systems in some network segments due to this
bug/feature. Is there a workaround available? Otherwise I feel that I
need to open a RH support ticket for that as I cannot wait for the next
major release.

I do not think, there is workaround available.
Yes, opening Red Hat support ticket is good idea as it will increase the
priority of this feature.