Hi,
I have installed Katello 2.2.2 with Foreman 1.82 and the capsules running
also in version 2.2.2
When I try to deploy a server with PXE boot through a capsule, the
kickstart file is trying to be retrieved with the URL pointing to the
Katello server, not the capsule.
I have ran:
- in Katello: katello-installer --capsule-templates
in the Capsule: capsule-installer --templates
Then, I have refreshed the features in the web interface of Katello, but
still does not show anything related to templates, only the functions:
TFTP, DNS, DHCP, Puppet, Puppet CA, and Pulp Node
The Capsule is registered with the URL https://<capsule fqdn>:9090
Any idea why the kickstart URL is not to the Capsule?
Best Regards,
Joaquin
> Hi,
>
> I have installed Katello 2.2.2 with Foreman 1.82 and the capsules running
> also in version 2.2.2
>
> When I try to deploy a server with PXE boot through a capsule, the
> kickstart file is trying to be retrieved with the URL pointing to the
> Katello server, not the capsule.
>
> I have ran:
> - in Katello: katello-installer --capsule-templates
This one isn't needed
> in the Capsule: capsule-installer --templates
>
> Then, I have refreshed the features in the web interface of Katello, but
> still does not show anything related to templates, only the functions:
> TFTP, DNS, DHCP, Puppet, Puppet CA, and Pulp Node
> The Capsule is registered with the URL https://<capsule fqdn>:9090
>
> Any idea why the kickstart URL is not to the Capsule?
Try restarting the foreman-proxy service on the Capsule, and make sure
the host's Subnet has the Capsule as its TFTP Proxy.
If that doesn't help, what's the contents of
/etc/foreman-proxy/settings.d/templates.yml?
···
On Thu, Jul 16, 2015 at 09:19:49PM -0700, Joaquín Fernández Llamas wrote:
Best Regards,
Joaquin
–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
I have tried running in the capsule also: capsule-installer --templates
"true" and then restarting foreman proxy even all services "katello-service
restart"
I have deleted the host and recreated it after the changes, but is still
showing the Katello URL.
/etc/foreman-proxy/settings.d/templates.yml
···
---
# Enable this if the Proxy should handle template requests on behalf of
Foreman
# Can be true, false, or http/https to enable just one of the protocols
:enabled: true
This plugin also requires that :foreman_url: be set in the main
settings.yml
This lets the plugin know how to obtain the templates from foreman.
This allows the proxy to define how hosts that are being provisioned
where to
obtain the templates from. Most installers don’t support https, so it’s
recommended
to enable an http port listener in the main config file too, and use it in
the url below
:template_url is the URL the host should use to contact the proxy for a
template.
The default protocol is http on port 80 unless otherwise specified in the
url.
Examples:
:template_url: http://capsule.example.local:8000
On Friday, July 17, 2015 at 6:33:47 PM UTC+7, stephen wrote:
On Thu, Jul 16, 2015 at 09:19:49PM -0700, Joaquín Fernández Llamas wrote:
Hi,
I have installed Katello 2.2.2 with Foreman 1.82 and the capsules
running
also in version 2.2.2
When I try to deploy a server with PXE boot through a capsule, the
kickstart file is trying to be retrieved with the URL pointing to the
Katello server, not the capsule.
I have ran:
- in Katello: katello-installer --capsule-templates
This one isn’t needed
in the Capsule: capsule-installer --templates
Then, I have refreshed the features in the web interface of Katello, but
still does not show anything related to templates, only the functions:
TFTP, DNS, DHCP, Puppet, Puppet CA, and Pulp Node
The Capsule is registered with the URL https://:9090
Any idea why the kickstart URL is not to the Capsule?
Try restarting the foreman-proxy service on the Capsule, and make sure
the host’s Subnet has the Capsule as its TFTP Proxy.
If that doesn’t help, what’s the contents of
/etc/foreman-proxy/settings.d/templates.yml?
Best Regards,
Joaquin
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
> I have tried running in the capsule also: capsule-installer --templates
> "true" and then restarting foreman proxy even all services "katello-service
> restart"
> I have deleted the host and recreated it after the changes, but is still
> showing the Katello URL.
The below all looks right - a few more things to check:
-
Does the Templates feature show up under 'Infrastructure / Smart
Proxies'? Try refreshing the features list if not.
-
/etc/foreman-proxy/settings.yml - is :http_port: uncommented? It
should be just by the nature of templates being enabled.
-
Please confirm the subnet you're building the hostname has the TFTP
Proxy the same as the Templates proxy
···
On Fri, Jul 17, 2015 at 08:24:20AM -0700, Joaquín Fernández Llamas wrote:
/etc/foreman-proxy/settings.d/templates.yml
Enable this if the Proxy should handle template requests on behalf of
Foreman
Can be true, false, or http/https to enable just one of the protocols
:enabled: true
This plugin also requires that :foreman_url: be set in the main
settings.yml
This lets the plugin know how to obtain the templates from foreman.
This allows the proxy to define how hosts that are being provisioned
where to
obtain the templates from. Most installers don’t support https, so it’s
recommended
to enable an http port listener in the main config file too, and use it in
the url below
:template_url is the URL the host should use to contact the proxy for a
template.
The default protocol is http on port 80 unless otherwise specified in the
url.
Examples:
:template_url: http://capsule.example.local:8000
On Friday, July 17, 2015 at 6:33:47 PM UTC+7, stephen wrote:
On Thu, Jul 16, 2015 at 09:19:49PM -0700, Joaquín Fernández Llamas wrote:
Hi,
I have installed Katello 2.2.2 with Foreman 1.82 and the capsules
running
also in version 2.2.2
When I try to deploy a server with PXE boot through a capsule, the
kickstart file is trying to be retrieved with the URL pointing to the
Katello server, not the capsule.
I have ran:
- in Katello: katello-installer --capsule-templates
This one isn’t needed
in the Capsule: capsule-installer --templates
Then, I have refreshed the features in the web interface of Katello, but
still does not show anything related to templates, only the functions:
TFTP, DNS, DHCP, Puppet, Puppet CA, and Pulp Node
The Capsule is registered with the URL https://:9090
Any idea why the kickstart URL is not to the Capsule?
Try restarting the foreman-proxy service on the Capsule, and make sure
the host’s Subnet has the Capsule as its TFTP Proxy.
If that doesn’t help, what’s the contents of
/etc/foreman-proxy/settings.d/templates.yml?
Best Regards,
Joaquin
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
–
You received this message because you are subscribed to the Google Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Best Regards,
Stephen Benjamin
Red Hat Engineering
Hi Stephen,
- Now Templates is showing in the feature list of the capsule.
- http_port and https_port are uncommented
- the subnet is configured to use the Capsule for all the proxies and the
host is configured to use the Capsule for Puppet, PuppetCA and content
source.
Now the fetch of the kickstart file is working as the URL points to the
Capsule, but the treeinfo and squashfs img are trying to be downloaded with
the Katello URL.
Best Regards,
Joaquin
···
On Friday, July 17, 2015 at 11:36:43 PM UTC+7, stephen wrote:
>
> On Fri, Jul 17, 2015 at 08:24:20AM -0700, Joaquín Fernández Llamas wrote:
> > I have tried running in the capsule also: capsule-installer --templates
> > "true" and then restarting foreman proxy even all services
> "katello-service
> > restart"
> > I have deleted the host and recreated it after the changes, but is still
> > showing the Katello URL.
>
> The below all looks right - a few more things to check:
>
> - Does the Templates feature show up under 'Infrastructure / Smart
> Proxies'? Try refreshing the features list if not.
>
> - /etc/foreman-proxy/settings.yml - is :http_port: uncommented? It
> should be just by the nature of templates being enabled.
>
> - Please confirm the subnet you're building the hostname has the TFTP
> Proxy the same as the Templates proxy
>
>
> >
> > /etc/foreman-proxy/settings.d/templates.yml
> > ---
> > # Enable this if the Proxy should handle template requests on behalf of
> > Foreman
> > # Can be true, false, or http/https to enable just one of the protocols
> > :enabled: true
> >
> > # This plugin also requires that :foreman_url: be set in the main
> > settings.yml
> > # This lets the plugin know how to obtain the templates from foreman.
> >
> > # This allows the proxy to define how hosts that are being provisioned
> > where to
> > # obtain the templates from. Most installers don't support https, so
> it's
> > recommended
> > # to enable an http port listener in the main config file too, and use
> it in
> > # the url below
> > #
> > # :template_url is the URL the host should use to contact the proxy for
> a
> > template.
> > # The default protocol is http on port 80 unless otherwise specified in
> the
> > url.
> > # Examples:
> > # https://1.2.3.4:8443 # default proxy https port
> > # http://1.2.3.4:8000 # default proxy http port
> > # https://smart-proxy.example.com # assumes port 443
> > # http://smart-proxy.example.com # assumes port 80
> > # smart-proxy.example.com:8080 # assumes http
> > :template_url: http://capsule.example.local:8000
> >
> >
> > On Friday, July 17, 2015 at 6:33:47 PM UTC+7, stephen wrote:
> > >
> > > On Thu, Jul 16, 2015 at 09:19:49PM -0700, Joaquín Fernández Llamas > wrote:
> > > > Hi,
> > > >
> > > > I have installed Katello 2.2.2 with Foreman 1.82 and the capsules
> > > running
> > > > also in version 2.2.2
> > > >
> > > > When I try to deploy a server with PXE boot through a capsule, the
> > > > kickstart file is trying to be retrieved with the URL pointing to
> the
> > > > Katello server, not the capsule.
> > > >
> > > > I have ran:
> > > > - in Katello: katello-installer --capsule-templates
> > >
> > > This one isn't needed
> > >
> > > > in the Capsule: capsule-installer --templates
> > > >
> > > > Then, I have refreshed the features in the web interface of Katello,
> but
> > > > still does not show anything related to templates, only the
> functions:
> > > > TFTP, DNS, DHCP, Puppet, Puppet CA, and Pulp Node
> > > > The Capsule is registered with the URL https://:9090
> > > >
> > > > Any idea why the kickstart URL is not to the Capsule?
> > >
> > > Try restarting the foreman-proxy service on the Capsule, and make sure
> > > the host's Subnet has the Capsule as its TFTP Proxy.
> > >
> > > If that doesn't help, what's the contents of
> > > /etc/foreman-proxy/settings.d/templates.yml?
> > >
> > >
> > > >
> > > > Best Regards,
> > > >
> > > > Joaquin
> > > >
> > > >
> > > > --
> > > > You received this message because you are subscribed to the Google
> > > Groups "Foreman users" group.
> > > > To unsubscribe from this group and stop receiving emails from it,
> send
> > > an email to foreman-user...@googlegroups.com .
> > > > To post to this group, send email to forema...@googlegroups.com
> > > .
> > > > Visit this group at http://groups.google.com/group/foreman-users.
> > > > For more options, visit https://groups.google.com/d/optout.
> > >
> > >
> > > --
> > > Best Regards,
> > >
> > > Stephen Benjamin
> > > Red Hat Engineering
> > >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "Foreman users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to foreman-user...@googlegroups.com .
> > To post to this group, send email to forema...@googlegroups.com
> .
> > Visit this group at http://groups.google.com/group/foreman-users.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
> Best Regards,
>
> Stephen Benjamin
> Red Hat Engineering
>
