[root@localhost admin]# semanage fcontext -a -t textrel_shlib_t '/opt/google/chrome/chrome'
[root@localhost admin]# restorecon -v '/opt/google/chrome/chrome'
restorecon reset /opt/google/chrome/chrome context system_u:object_r:execmem_exec_t:s0->system_u:object_r:textrel_shlib_t:s0
[root@localhost admin]# grep chrome /var/log/audit/audit.log | audit2allow -M mypol
******************** IMPORTANT ***********************
To make this policy package active, execute:

semodule -i mypol.pp

[root@localhost admin]# semodule -i mypol.pp
[root@localhost admin]# grep chrome-sandbox /var/log/audit/audit.log | audit2allow -M mypol
******************** IMPORTANT ***********************
To make this policy package active, execute:

semodule -i mypol.pp

[root@localhost admin]# semodule -i mypol.pp
[root@localhost admin]#

SELinux is preventing /opt/google/chrome/chrome from execmod access on the file /opt/google/chrome/chrome.

*****  Plugin allow_execmod (91.4 confidence) suggests  **********************

If you want to allow chrome to have execmod access on the chrome file
Then you need to change the label on '/opt/google/chrome/chrome'
Do
# semanage fcontext -a -t textrel_shlib_t '/opt/google/chrome/chrome'
# restorecon -v '/opt/google/chrome/chrome'

*****  Plugin catchall (9.59 confidence) suggests  ***************************

If you believe that chrome should be allowed execmod access on the chrome file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep chrome /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp