I am still getting this.

[ WARN 2017-04-06 16:05:25 verbose]  Undefined variable 'ipaddress_eno1';
[ WARN 2017-04-06 16:05:25 verbose]    (file & line not available)
[ERROR 2017-04-06 16:05:25 verbose]  Evaluation Error: Error while
evaluating a Function Call, Could not get the ip address from fact
ipaddress_eno1 at
/usr/share/foreman-installer/modules/foreman_proxy/manifests/proxydns.pp:15:5
on node server.name

Even with


foreman-installer --verbose  --foreman-proxy-dhcp-interface=eth0
--foreman-proxy-dhcp=true

I get the error.

So that switch apparently is not enough.

What is really interesting is that when I went interactive the default was
set correctly

75. Set dhcp_search_domains, current value:
76. Set dhcp_interface, current value: eth0

It was the DNS interface apparently that was messing things up.

Of course now foreman installer seems to be undoing all of the fixes I had
to do to get it working. So maybe I will or will not have a working foreman
after this is done...

Terrence








On Thu, Apr 6, 2017 at 3:24 PM, Alan Evans <[email protected]> wrote:

> Terrance,
>
> If eno1 is the correct interface for DHCP, please make sure that it has an
> IP address on it.  If not, you can use the switch
> --foreman-proxy-dhcp-interface for foreman-installer to correct the
> interface.
>
> ipaddress_eno1 is a puppet "fact".  You can use the commandline tool
> "facter" to see what the values of facts are.  In this case:
>
> $ sudo facter -p ipaddress_eno1
>
> Note:  We use -p here which enables puppet facts (since the installer _is_
> puppet...) and sudo because some of the puppet facts need elevated
> privileges.
>
> -Alan
>
> On Thursday, April 6, 2017 at 12:23:59 PM UTC-6, Terrence Martin wrote:
>>
>> When I originally setup my foreman host its network interface name was
>> eno1, or at least had a similar interface. However later on after I did
>> some network modifications/kernel upgrades the host changes its interface
>> names to eth0 and and eth1.
>>
>> This is correctly reflected in the puppet facts and via hammer.
>>
>> However I get this error.
>>
>>
>> [DEBUG 2017-04-06 11:11:56 main]  importing '/usr/share/foreman-installer/
>> modules/foreman_proxy/manifests/proxydhcp.pp' in environment production
>> [DEBUG 2017-04-06 11:11:56 main]  Automatically imported
>> foreman_proxy::proxydhcp from foreman_proxy/proxydhcp into production
>> [DEBUG 2017-04-06 11:11:56 main]  template[inline]: Bound template
>> variables for inline template in 0.00 seconds
>> [ WARN 2017-04-06 11:11:56 main]  Undefined variable 'ipaddress_eno1';
>> [ WARN 2017-04-06 11:11:56 main]    (file & line not available)
>> [DEBUG 2017-04-06 11:11:56 main]  template[inline]: Interpolated template
>> inline template in 0.00 seconds
>> [ERROR 2017-04-06 11:11:56 main]  Evaluation Error: Error while
>> evaluating a Function Call, pick(): must receive at least one non empty
>> value at 
>> /usr/share/foreman-installer/modules/foreman_proxy/manifests/proxydhcp.pp:6:11
>> on node foreman.t2.ucsd.edu
>>
>> Where could this information be hiding and how can I excise it?
>>
>> Terrence
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/foreman-users/zVB_74Tnyso/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
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