Known Issues in Navigator Encrypt

Known issues and technical limitations for Navigator Encrypt are addressed in Cloudera Runtime 7.1.9 SP2.

Known issues identified in Cloudera Runtime 7.1.9 SP2

There are no new known issues identified in this release.

Known Issues identified before Cloudera Runtime 7.1.9 SP2

Failed to start navencrypt-mount.service
7.1.9 and its SPs and CHFs
After installing NavEncrypt on SLES, if the comand "systemctl status navencrypt-mount" fails with the error: "Failed to start navencrypt-mount.service: Unit navencrypt-mount.service failed to load: No such file or directory", the systemd files need to be reloaded..
Run the command:
(sudo) systemctl daemon-reload
.
Crash in Navigator Encrypt kernel module if --profile-file= option isused with ACLs
7.1.9 and its SPs and CHFs
When you add ACLs with the acl --add --rule command, if you include any ACLs that uses the --profile-file= option, the kernel module (and host) crashes during Navigator Encrypt shutdown.
None.