METRON-1145: Profiler mpack does not create kafka acl and hbase acls correctly in kerberized cluster #726
Conversation
|
You should add something to the PR Template or something |
|
haha actually, it's more like, "if a mpack, have you tested on kerberized full-dev" |
|
Tested this in full dev with Kerberos enabled. The profiler topology starts up without issue and data appears in HBase after creating a profile. +1 |
| @@ -59,6 +60,9 @@ def configure(self, env, upgrade_type=None, config_dir=None): | |||
| commands.create_hbase_tables() | |||
| if params.security_enabled and not commands.is_hbase_acl_configured(): | |||
| commands.set_hbase_acls() | |||
There was a problem hiding this comment.
Is there a reason that we do not call commands.set_hbase_acl_configured() here?
There was a problem hiding this comment.
Sorry to bring this up on an old, closed PR, but I am currently trying to track a bug that is giving me an uber headache. :) Thought this was the easiest way to reach out.
There was a problem hiding this comment.
@nickwallen It happens at the end of set_hbase_acls()
There was a problem hiding this comment.
Ah, daft, you're right. It works different than the Kafka ACL functions.
Contributor Comments
Title says it all. The management pack will not start the profiler in a kerberized cluster due to us not setting the acls correctly for the hbase tables and kafka group acls.
To test this, spin up full-dev, kerberize it and ensure the profiler topology starts without error.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:
For code changes:
Have you included steps to reproduce the behavior or problem that is being changed or addressed?
Have you included steps or a guide to how the change may be verified and tested manually?
Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.