Description of problem:

If the multisite is not configured via ceph-ansible, the ceph-dashboard configure task fails at the secondary zone. 

Version-Release number of selected component (if applicable):
4.1

How reproducible:
Always

Steps to Reproduce:
1. Install ceph cluster w/o multisite configuration
2. Configure multisite with radosgw-admin commands
3. Run the ansible-playbook again

Actual results:
TASK [ceph-dashboard : create radosgw system user] *******************************************************************************************************************************************************************************************
Monday 29 June 2020  08:27:00 -0400 (0:00:01.312)       0:11:26.797 *********** 
FAILED - RETRYING: create radosgw system user (3 retries left).
FAILED - RETRYING: create radosgw system user (2 retries left).
FAILED - RETRYING: create radosgw system user (1 retries left).
fatal: [ceph4osd1 -> ceph4osd1]: FAILED! => changed=true 
  attempts: 3
  cmd:
  - timeout
  - --foreground
  - -s
  - KILL
  - '20'
  - docker
  - exec
  - ceph-mon-ceph4osd1
  - radosgw-admin
  - --cluster
  - ceph
  - user
  - create
  - --uid=ceph-dashboard
  - --display-name=Ceph dashboard
  - --system
  delta: '0:00:02.239991'
  end: '2020-06-29 08:27:26.360889'
  msg: non-zero return code
  rc: 22
  start: '2020-06-29 08:27:24.120898'
  stderr: |-
    Please run the command on master zone. Performing this operation on non-master zone leads to inconsistent metadata between zones
    Are you sure you want to go ahead? (requires --yes-i-really-mean-it)
  stderr_lines: <omitted>
  stdout: ''
  stdout_lines: <omitted>


Expected results:

The ansible playbook should succeed even if the multisite is not configured via ceph-ansible. there might be many reason why the Customers would use manual method such as lack of multiple zonegroup support or using keepalived IP for zonegroup/zone endpoints. 

Additional info: