Atlas classification tags not appearing in Ranger tag policy options?

[Reed Villanueva <rv...@ucera.org>]

Installed HDP 3.1 cluster and later added Atlas and Ranger services. Seeing
problem where classifications and glossary tags created in atlas do not
show up in ranger's tag-based policy creation ui, eg. in atlas I see [image:
enter image description here] <https://i.stack.imgur.com/tm66b.png>but in
ranger UI, I see nothing... [image: enter image description here]
<https://i.stack.imgur.com/t8wlK.png>[image: enter image description here]
<https://i.stack.imgur.com/2JqeD.png>though granted I have never used atlas
or ranger before, so not exactly sure what I *should* be seeing.

Looking at a post with a similar question
<http://community.hortonworks.com/answers/93426/view.html>, they offer some
possibilities:

1) Tags are syncd but resource lookup not working for tags.

2) tags are not syncd

Checking (1), I look for the tagsync node and do...

[root@HW01 /]# clush -ab ls -lh /var/log/ranger/tagsync
HW01: ls: cannot access /var/log/ranger/tagsync: No such file or directory
HW02: ls: cannot access /var/log/ranger/tagsync: No such file or directory
HW05: ls: cannot access /var/log/ranger/tagsync: No such file or
directory---------------
HW03---------------
total 0---------------
HW04---------------
total 20K-rw-r--r--. 1 ranger hadoop 16K Aug  5 15:04
tagsync.log-rw-r--r--. 1 ranger hadoop 298 Aug  5 15:04 tagsync.out
clush: HW[01-02,05] (3): exited with exit code 2[root@HW01 /]# ssh
hw04Last login: Thu Aug  8 11:54:12 2019[root@HW04 ~]# vi
/var/log/ranger/tagsync/tagsync.log[root@HW04 ~]# cat
/var/log/ranger/tagsync/tagsync.log | grep ERROR[root@HW04 ~]# cat
/var/log/ranger/tagsync/tagsync.log | grep WARN[root@HW04 ~]# cat
/var/log/ranger/tagsync/tagsync.log | grep WARNING

and see nothing. checking for (2), on the the ranger DB-hosting node, I see

$ mysql -uroot -proot
mysql> use ranger;
mysql> select * from x_tag;
+----+--------------------------------------+---------------------+---------------------+-------------+-----------+---------+------+----------+----------------+----------------+|
id | guid                                 | create_time         |
update_time         | added_by_id | upd_by_id | version | type |
owned_by | policy_options | tag_attrs_text
|+----+--------------------------------------+---------------------+---------------------+-------------+-----------+---------+------+----------+----------------+----------------+|
 1 | ed6ef4a8-2d88-48af-12cf-a2ee6b23bc44 | 2019-08-06 20:58:13 |
2019-08-06 20:58:13 |           4 |         4 |       1 |    1 |
 0 | NULL           | NULL           ||  2 |
f5e753bf-1c36-4bae-34f7-3e12fe94a32a | 2019-08-06 21:00:57 |
2019-08-06 21:00:57 |           4 |         4 |       1 |    1 |
 0 | NULL           | NULL
|+----+--------------------------------------+---------------------+---------------------+-------------+-----------+---------+------+----------+----------------+----------------+2
rows in set (0.00 sec)

apparently if atlas tagsync were not working I'd see nothing (I assume what
I'm seeing here are the only two entities in my mock atlas setup that I
have assigned classification tags to (if anyone knows where the docs are
for understanding what ranger's x_tag db is, do let me know)).

Also note that in the ambari UI, for atlas I see

ranger.plugin.atlas.ambari.cluster.name={{cluster_name}}

and for ranger I see

ranger.tagsync.atlas.default.cluster.name={{cluster_name}}

So the syncing should not be a problem.

So neither of these seem to be a problem, yet not seeing a way to set
ranger tags on the classifications created in atlas. Am I misunderstanding
something here? Anyone with more experience have any debugging suggestions
or fixes?

-- 
This electronic message is intended only for the named 
recipient, and may 
contain information that is confidential or 
privileged. If you are not the 
intended recipient, you are 
hereby notified that any disclosure, copying, 
distribution or 
use of the contents of this message is strictly 
prohibited. If 
you have received this message in error or are not the 
named
recipient, please notify us immediately by contacting the 
sender at 
the electronic mail address noted above, and delete 
and destroy all copies 
of this message. Thank you.