et its tftp stuff from,
otherwise it wont boot via PXE.
Johannes
P.S.: No need to CC me, I'm subscribed to the list.
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-sy
foreman server was on, as well as the NICs in the VMs.
Did I get you right?
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenss
g" mean the
foreman provisioning setup or the Vmware VM configuration?
> 3.) Ideally I don't want any DNS or DHCP being performed by the
> Foreman server, is it just a simple case specifying IPAM: None and
> Bootmode: Static?
No idea, sorry.
--
Johannes Kastl
Linux Consultant
ration, not the one that the
machine has on its local hard drive after provisioning?
Johannes
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unterne
t installed any updates. I'll try to dig into
this, if I get the time...
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohbu
r browser does not trust.
Replace it with a certificate you bought or got via lets encrypt or
similar, or just add an exception in your browser.
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 V
Lukas Zapletal schrieb:
> So this is solved, is it?
Yes.
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ing
e dhcp range.
So to get that one has to do what I mentioned.
AFAIK just modifying the subnet after creation, adding the range and not
running the installer again with the
'--foreman-proxy-dhcp-range="192.168.125.21 192.168.125.200"' option
does not result in a working installation.
Johann
Johannes Kastl schrieb:
> When hitting the SUBMIT button in the Provision-Step, I get some
> errors regarding the templates, that seems to be cause by an error
> with the interface:
>
> "Some of the interfaces are invalid. Please check the table below."
I could solv
Johannes Kastl schrieb:
> This is rendering foreman unusable for my usecase, so it is kind of
> urgent that I get this running.
I just set up a new instance of foreman, which also has working
discovery, but shows this error. And no, I do not get any more specific
error messages.
Pleas
r details.
Johannes
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
--
You received this messag
ng...
Johannes
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
--
You received this
r re-setup the
provisioning (and deleting the first subnet) seems to work.
Is this a known issue?
Foreman version is 1.14.2
Thanks in advance.
Johannes
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088
Johannes Kastl schrieb:
> Johannes Kastl schrieb:
>> It is the step after that, when provisioning the host, that fails.
>
> I am attaching a screen shot of the error (I hope it gets through to
> the list).
Is there anything I can do to debug this further? Any more logs?
Anythi
discovery, which is set
to "local" in the link you gave.
But that should only affect auto-discovery, which works fine in my case.
It is the step after that, when provisioning the host, that fails.
Or am I misunderstanding something?
Johannes
--
Johannes Kastl
Linux Consultant & Tr
this a known error in 1.14.2? Anything I can do to debug this? Any
information I can supply to help look for the root cause?
Thanks in advance.
Johannes
--
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 8
16 matches
Mail list logo