You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
not sure what is the impact of err: Could not find a suitable provider for augeas in the vagrant provision output below:
==> default: notice: /Stage[main]/Elasticsearch::Config/File[/etc/elasticsearch]/owner: owner changed 'root' to 'elasticsearch'
==> default: notice: /Stage[main]/Elasticsearch::Config/File[/etc/elasticsearch]/group: group changed 'root' to 'elasticsearch'
==> default: notice: /Stage[main]/Elasticsearch::Config/File[/etc/elasticsearch/elasticsearch.yml]/ensure: removed
==> default: notice: /Stage[main]/Elasticsearch::Config/File[/etc/elasticsearch/logging.yml]/ensure: removed
==> default: notice: /Stage[main]//File[/usr/share/elasticsearch/config/elasticsearch.yml]/ensure: created
==> default: notice: /File[/usr/share/elasticsearch/lib/jna-4.1.0.jar]/owner: owner changed 'root' to 'elasticsearch'
==> default: notice: /File[/usr/share/elasticsearch/lib/jna-4.1.0.jar]/group: group changed 'root' to 'elasticsearch'
==> default: err: Could not find a suitable provider for augeas
==> default: notice: Finished catalog run in 537.40 seconds
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
not sure what is the impact of
err: Could not find a suitable provider for augeas
in thevagrant provision
output below:Using commit fd08f5c on the
master
branch.May relate to https://ask.puppetlabs.com/question/2147/could-not-find-a-suitable-provider-for-augeas/
The text was updated successfully, but these errors were encountered: