You ENC seems to depend upon the host's facts in the default yaml cache location. Perhaps you have removed the yaml caching of facts?

Regards, David

On 2014-07-14 23:46, Taylor Leese wrote:
I incorrectly redacted the host name in the error message. Here is the
correct version:

*==> nexus: **Warning: Unable to fetch my node definition, but the agent
run will continue:*

*==> nexus: **Warning: Error 400 on SERVER: Failed to find
nexus.myhost.com <http://nexus.myhost.com/> via exec: Execution of
'/etc/puppet/bin/node_classifier nexus.myhost.com <http://my.host.com/>'
returned 1: Error reading YAML file: No such file or directory -
/var/lib/puppet/yaml/facts/nexus.myhost.com.yaml*

*==> nexus: *



On Mon, Jul 14, 2014 at 2:43 PM, Taylor Leese <tlees...@gmail.com
<mailto:tlees...@gmail.com>> wrote:

    Hi all -

    I setup an ENC and classification works for the most part except on
    the first run. I've noticed that the yaml file in
    /var/lib/puppet/yaml/facts doesn't exist on the first run so I
    receive a warning during Vagrant provisioning similar to below.
    Note, when I run the Puppet agent a subsequent time there is no
    error. I am using Puppet 3.4.3 and Facter 1.7.5. I also found a
    similar issue referenced in the Foreman project here
    (https://projects.theforeman.org/issues/5925). Any idea what could
    be causing this or if this might be a bug?

    *==> nexus: **Warning: Unable to fetch my node definition, but the
    agent run will continue:*

    *==> nexus: **Warning: Error 400 on SERVER: Failed to find
    nexus.myhost.com <http://nexus.myhost.com> via exec: Execution of
    '/etc/puppet/bin/node_classifier my.host.com <http://my.host.com>'
    returned 1: Error reading YAML file: No such file or directory -
    /var/lib/puppet/yaml/facts/nexus.myhost.com.yaml*

    *==> nexus: *

    - Taylor

    --
    You received this message because you are subscribed to a topic in
    the Google Groups "Puppet Users" group.
    To unsubscribe from this topic, visit
    https://groups.google.com/d/topic/puppet-users/kbL4rwAsG1g/unsubscribe.
    To unsubscribe from this group and all its topics, send an email to
    puppet-users+unsubscr...@googlegroups.com
    <mailto:puppet-users+unsubscr...@googlegroups.com>.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/puppet-users/7d6f51e3-62e0-4311-a5a3-dbcf92d3070b%40googlegroups.com
    
<https://groups.google.com/d/msgid/puppet-users/7d6f51e3-62e0-4311-a5a3-dbcf92d3070b%40googlegroups.com?utm_medium=email&utm_source=footer>.
    For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google
Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to puppet-users+unsubscr...@googlegroups.com
<mailto:puppet-users+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAKwbMverR_hndKRZ%2BdRA%2BvorW6ONKxCV6okwz0C%2BopzadS0GxA%40mail.gmail.com
<https://groups.google.com/d/msgid/puppet-users/CAKwbMverR_hndKRZ%2BdRA%2BvorW6ONKxCV6okwz0C%2BopzadS0GxA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Puppet 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/53CCACE2.80203%40dasz.at.
For more options, visit https://groups.google.com/d/optout.

Reply via email to