Bug 2073030

Summary:	Please continue to support --yes-i-know
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	John Fulton <johfulto>
Component:	Cephadm	Assignee:	Adam King <adking>
Status:	CLOSED ERRATA	QA Contact:	Sayalee <saraut>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.2	CC:	adking, ekristov, fpantano, ltoscano, tserlin, vdas, vereddy
Target Milestone:	---
Target Release:	6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-17.2.3-12.el9cp	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-20 18:56:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description John Fulton 2022-04-07 13:50:35 UTC

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 \

Comment 1 RHEL Program Management 2022-04-07 13:50:41 UTC

Please specify the severity of this bug. Severity is defined here:
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.

Comment 2 John Fulton 2022-04-07 13:59:47 UTC

Severity is set to high since it could break OpenStack customers deploying ceph and I've been asked to set a severity.

Comment 19 errata-xmlrpc 2023-03-20 18:56:12 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat Ceph Storage 6.0 Bug Fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:1360