the problem in this case is probably that we configure these interfaces during 
last step of provisioning (%post in case of kickstart, finish script in case of 
debian). If you need to use VLAN for the actual installation you should be 
able to achieve it by changing provisioning template, there's no built-in 
support for it atm. OTOH the data that you'd need should be accessible in that 
template, you can take a look at [1] for good example.


Hope this helps


On Thursday 22 of September 2016 06:20:03 Cale Bouscal wrote:
> I have a UCS instance with a nic trunked to a pair of vlans, one for
> provisioning  (vlan1) and one for primary service (vlan 101)
> My expectation:
> - all pxe/provision activity happens over nic1/vlan1, while a nic1.101
> sysconfig file is created to define the primary interface.
> My result:
> - no matter how I configure this, I end up with a system trying to use
> nic1.101 dns servers during provisioning, and fails. Further inspection
> shows "only one interface found" during boot - it's like the virtual nic
> isn't being recognized, even though I've configured it with the appropriate
> vlan tag and listed the parent eth0.
> I understand that nic1.101 has to be flagged as "managed" in order for
> foreman to configure it - but that seems to lead to all sorts of other
> issues, including registration of DNS (which I don't want) being attempted
> and failing.
> How do I achieve the result I'm looking for?

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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to