Yes it is a bug and it is not fixed yet. For now you can work around this by either grant manage
privilege or explicitly add the action name for the remote index, e.g.:
ccr_leader:
cluster:
- read_ccr
- monitor
indices:
- names: '*'
privileges:
- read
- manage