GitHub user nickwallen opened a pull request:
https://github.com/apache/incubator-metron/pull/307
METRON-499 Check for Metron Jar Fails During Quick-Dev Deployment
[METRON-499](https://issues.apache.org/jira/browse/METRON-499)
When deploying with Quick-Dev, it fails when checking to see if the Metron
jars have been built. When checking the local file system, it attempts to
obtain elevated privileges and fails.
```
@
~/Development/incubator-metron/metron-deployment/vagrant/quick-dev-platform
$ vagrant provision
Running with ansible-tags: ["hdp-deploy", "metron"]
Running with ansible-skip-tags: ["solr", "yaf"]
==> node1: Running provisioner: ansible...
node1: Running ansible-playbook...
....
TASK [metron_common : Check for Metron jar path]
*******************************
fatal: [node1 -> localhost]: FAILED! => {"changed": false, "failed": true,
"module_stderr": "sudo: a password is required\n", "module_stdout": "", "msg":
"MODULE FAILURE", "parsed": false}
```
When checking the local file system for the jar, Ansible attempts to obtain
elevated privileges, since most of the tasks defined in the playbooks run with
elevated privileges. Elevated privilege is not needed in this case.
Tested by running on Quick-Dev.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/incubator-metron METRON-499
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/307.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #307
----
commit e208ae50b8927cbbfab1a3467ddf76dc2506ab1a
Author: Nick Allen <[email protected]>
Date: 2016-10-12T21:12:59Z
METRON-499 Check for Metron Jar Fails During Quick-Dev Deployment
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
