Re: [foreman-users] Re: Cannot provision vnic correctly

2016-09-27 Thread Marek Hulán
On Monday 26 of September 2016 16:14:36 Lukas Zapletal wrote: > > According to what I see, the --nameserver [1] is used from subnet of > > primary interface. I think the provisioning interface was meant only for > > PXE boot but the rest of the installation goes through primary interface > > includ

Re: [foreman-users] Re: Cannot provision vnic correctly

2016-09-26 Thread Lukas Zapletal
> According to what I see, the --nameserver [1] is used from subnet of primary > interface. I think the provisioning interface was meant only for PXE boot but > the rest of the installation goes through primary interface including > downloading the content. I also think that is incorrect, we sh

Re: [foreman-users] Re: Cannot provision vnic correctly

2016-09-23 Thread Marek Hulán
Hello According to what I see, the --nameserver [1] is used from subnet of primary interface. I think the provisioning interface was meant only for PXE boot but the rest of the installation goes through primary interface including downloading the content. I'm still a bit confused about your se

[foreman-users] Re: Cannot provision vnic correctly

2016-09-22 Thread Cale Bouscal
Hmm, not sure that's what we're looking for. eth0 is capable of booting natively and provisioning. If we ignored the eth0.1 completely we'd be set. However, during ks, we don't resolve the repo name, because "dnsservers is " even though there is a dns server configured in the prov subnet. It's