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
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
>
>
>
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
- Set dhcp_search_domains, current value:
- 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 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
foreman-users+unsubscribe@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.
Nope…
2017-04-06 16:25:31,234 INFO [async-dispatch-2] [p.t.s.s.status-service]
Registering status service HTTP API at /status
2017-04-06 16:25:31,236 ERROR [async-dispatch-2] [p.t.internal] Error
during service start!!!
java.lang.IllegalArgumentException: service
:puppetlabs.trapperkeeper.services.status.status-service/status-service
does not appear in configuration
at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_endpoint_and_server_from_config.invokeStatic(webrouting_service_core.clj:55)
at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_endpoint_and_server_from_config.invoke(webrouting_service_core.clj:39)
at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_route.invokeStatic(webrouting_service_core.clj:99)
at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service_core$get_route.invoke(webrouting_service_core.clj:96)
at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service$reify__32452$service_fnk__5222__auto___positional$reify__32460.get_route(webrouting_service.clj:37)
at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval32182$fn__32346$G__32166__32352.invoke(webrouting_service.clj:10)
at
puppetlabs.trapperkeeper.services.webrouting.webrouting_service$eval32182$fn__32346$G__32165__32359.invoke(webrouting_service.clj:10)
at clojure.core$partial$fn__4759.invoke(core.clj:2515)
at
puppetlabs.trapperkeeper.services.status.status_service$reify__36567$service_fnk__5222__auto___positional$reify__36574.start(status_service.clj:34)
at
puppetlabs.trapperkeeper.services$eval5024$fn__5038$G__5014__5041.invoke(services.clj:8)
at
puppetlabs.trapperkeeper.services$eval5024$fn__5038$G__5013__5045.invoke(services.clj:8)
at
puppetlabs.trapperkeeper.internal$eval13792$run_lifecycle_fn_BANG___13799$fn__13800.invoke(internal.clj:204)
at
puppetlabs.trapperkeeper.internal$eval13792$run_lifecycle_fn_BANG___13799.invoke(internal.clj:187)
at
puppetlabs.trapperkeeper.internal$eval13821$run_lifecycle_fns__13826$fn__13827.invoke(internal.clj:238)
at
puppetlabs.trapperkeeper.internal$eval13821$run_lifecycle_fns__13826.invoke(internal.clj:215)
at
puppetlabs.trapperkeeper.internal$eval14291$build_app_STAR___14300$fn$reify__14310.start(internal.clj:591)
at
puppetlabs.trapperkeeper.internal$eval14337$boot_services_for_app_STAR__STAR___14344$fn__14345$fn__14347.invoke(internal.clj:617)
at
puppetlabs.trapperkeeper.internal$eval14337$boot_services_for_app_STAR__STAR___14344$fn__14345.invoke(internal.clj:615)
at
puppetlabs.trapperkeeper.internal$eval14337$boot_services_for_app_STAR__STAR___14344.invoke(internal.clj:609)
at clojure.core$partial$fn__4761.invoke(core.clj:2521)
at
puppetlabs.trapperkeeper.internal$eval13860$initialize_lifecycle_worker__13871$fn__13872$fn__13958$state_machine__11832__auto____13959$fn__13961.invoke(internal.clj:255)
at
puppetlabs.trapperkeeper.internal$eval13860$initialize_lifecycle_worker__13871$fn__13872$fn__13958$state_machine__11832__auto____13959.invoke(internal.clj:255)
at
clojure.core.async.impl.ioc_macros$run_state_machine.invokeStatic(ioc_macros.clj:1012)
at
clojure.core.async.impl.ioc_macros$run_state_machine.invoke(ioc_macros.clj:1011)
at
clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invokeStatic(ioc_macros.clj:1016)
at
clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invoke(ioc_macros.clj:1014)
at clojure.core.async$ioc_alts_BANG_$fn__12000.invoke(async.clj:383)
at
clojure.core.async$do_alts$fn__11946$fn__11949.invoke(async.clj:252)
at
clojure.core.async.impl.channels.ManyToManyChannel$fn__6756$fn__6757.invoke(channels.clj:95)
at clojure.lang.AFn.run(AFn.java:22)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2017-04-06 16:25:31,242 INFO [main] [p.t.internal] Beginning shutdown
sequence
···
On Thu, Apr 6, 2017 at 4:18 PM, Terrence Martin wrote:
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
- Set dhcp_search_domains, current value:
- 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 alanwevans@gmail.com 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/to
pic/foreman-users/zVB_74Tnyso/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@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.
