One of the requirements on the new client (insights-client) and it's installation was that it continue to support existing scripts, playbooks, etc. that use or depend on the old client (redhat-access-insights).
The redhat-access-insights-client does not work with the new client. The script does indeed install the new client, but does not ever register the host with the server.
The ansible role must test for the existence of /etc/redhat-access-insights/.registered to avoid rerunning "redhat-access-insights --register" when it isn't necessary. Any script (ansible, puppet, chef, bash, ...) that runs on a regular bases to ensure that a server's configuration is correct would need to do the same thing.
The RPM installation of the new client makes that file a soft link to the location of the new clients version of that file. A soft link always exists, even if the file it points to does not. So scripts that test for the existance of this file, find it always exists, and so will never run 'register'.
Fixed via https://github.com/RedHatInsights/insights-core/commit/6a76245a87611074917e70a4b22efbff8b824dd1
Delete existing symlinks on run, and recreate dotfile as a real file, maintain both locations.
Symlinks for these files should also be explicitly deleted by the RPM spec, will be included next RPM release.