I know this is "not recommended" vars but I really need HTTP instead of
TFTP (my pxelinux does support it).
In Debian PXELinux I get this error:
"There was an error rendering the Ubuntu_PXELinux template: undefined method `url_for_boot' for #<Debian:0x0000000c918398>"
I know Foreman has the HTTP URL to the above as it downloads both kernel
and initrd into TFTP boot dir, so how do I reference those variables? Of
course, it would be ideal if the vars the vars were more consistent.
Above works just fine for RedHat PXELinux templates:
···
On Tue, Apr 19, 2016 at 12:17:12PM -0700, 'Konstantin Orekhov' via Foreman users wrote:
> I know Foreman has the HTTP URL to the above as it downloads both kernel
> and initrd into TFTP boot dir, so how do I reference those variables? Of
> course, it would be ideal if the vars the vars were more consistent.
Just one more to follow up - are there some vars available to me in
"finish" template for Debian similar to @preseed_path and @preseed_server
in "preseed" template?
The closest one I see is @host.os.medium_uri(@host) which returns to me all
of the above but co-joined like this
http://<preseed_server>/<preseed_path>/<release_name>
Any way for me to avoid parsing and splitting the above?
···
On Tue, Apr 19, 2016 at 02:49:36PM -0700, 'Konstantin Orekhov' via Foreman users wrote:
> Just one more to follow up - are there some vars available to me in
> "finish" template for Debian similar to @preseed_path and @preseed_server
> in "preseed" template?
These should be usable also in the finish template just fine.
So it is expected behavior, I'm just wondering if there's some undocumented
var(s) maybe.
···
> "finish" template for Debian similar to @preseed_path and @preseed_server
> > in "preseed" template?
>
> These should be usable also in the finish template just fine.
>