hiera.yaml - remove non-compliant line #35
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
On both Fedora 18+ and Ubuntu 13.10+, whilst using Puppet 3.6.2, the
clientcert line in hiera.yaml prevents loom from working. Specifically
the error message that appears is:
```
[192.168.50.10] out: Error: Error from DataBinding 'hiera' while looking
up 'sudo::enable': (<unknown>): found character that cannot start any
token while scanning for the next token at line 7 column 5 on node
ubuntu-14.04-amd64-vbox
[192.168.50.10] out: Wrapped exception:
[192.168.50.10] out: (<unknown>): found character that cannot start any
token while scanning for the next token at line 7 column 5
[192.168.50.10] out: Wrapped exception:
[192.168.50.10] out: (<unknown>): found character that cannot start any
token while scanning for the next token at line 7 column 5
[192.168.50.10] out: Error: Error from DataBinding 'hiera' while looking
up 'sudo::enable': (<unknown>): found character that cannot start any
token while scanning for the next token at line 7 column 5 on node
ubuntu-14.04-amd64-vbox
[192.168.50.10] out:
```
It is possible that I have misconfigured my Puppet manifests and that is
causing this error. However removing the `%{::clientcert}` line from
`hiera.yaml` does not seem to have any negative consequences.
Author
|
The Travis build failed because the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On both Fedora 18+ and Ubuntu 13.10+, whilst using Puppet 3.6.2, the
clientcert line in hiera.yaml prevents loom from working. Specifically
the error message that appears is:
It is possible that I have misconfigured my Puppet manifests and that is
causing this error. However removing the
%{::clientcert}line fromhiera.yamldoes not seem to have any negative consequences.If you'd like a better, more minimal reproduction of this issue please let
me know; I have some Vagrant/Puppet scripts lying around.