When RGW multisite is supported I assume you will stop requiring deployments to pass --yes-i-know to 'cephadm bootstrap'. When this happens, please do not make the deployment fail if --yes-i-know is passed. 

E.g. I can imagine reverting the original patch which cased BZ 2072665 and then the fix on the tripleo side [1] for 2072665 would cause a new error like:

Unrecognized option --yes-i-know

This bug requests that --yes-i-know remain a recognized option, even if it doesn't do anything.



[1] 

diff --git a/tripleo_ansible/roles/tripleo_cephadm/tasks/bootstrap.yaml b/tripleo_ansible/roles/tripleo_cephadm/tasks/bootstrap.yaml
index 3f39265..6e93578 100644
--- a/tripleo_ansible/roles/tripleo_cephadm/tasks/bootstrap.yaml
+++ b/tripleo_ansible/roles/tripleo_cephadm/tasks/bootstrap.yaml
@@ -47,6 +47,7 @@
         {{ tripleo_cephadm_bin }} \
         {% if not tripleo_cephadm_default_container %}--image {{ tripleo_cephadm_container_ns + '/' + tripleo_cephadm_container_image + ':' + tripleo_cephadm_container_tag|string }} \{% endif %}
         bootstrap \
+        --yes-i-know \
         --skip-firewalld \
         --ssh-private-key /home/{{ tripleo_cephadm_ssh_user }}/.ssh/id_rsa \
         --ssh-public-key /home/{{ tripleo_cephadm_ssh_user }}/.ssh/id_rsa.pub \