Bug 2081592

Summary: Stop deploying Ceph during the overcloud deployment
Product: Red Hat OpenStack Reporter: Francesco Pantano <fpantano>
Component: python-tripleoclientAssignee: Francesco Pantano <fpantano>
Status: CLOSED ERRATA QA Contact: Alfredo <alfrgarc>
Severity: high Docs Contact:
Priority: high    
Version: 17.0 (Wallaby)CC: alfrgarc, astupnik, gfidente, hbrock, jlabarre, johfulto, jschluet, jslagle, mburns
Target Milestone: z1Keywords: Triaged
Target Release: 17.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-tripleoclient-16.5.1-0.20221124080343.23dbe54.el9ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-01-25 12:28:47 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 Francesco Pantano 2022-05-04 07:00:15 UTC
Description of problem:

TripleO recently concluded the migration to the new ceph deployment
tool (cephadm). 
Now TripleO is able to deploy ceph in a separated stage, and we should prevent operators to deploy Ceph during the overcloud deployment stage, suggesting the right command that should be run.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yaniv Kaul 2022-06-02 09:48:14 UTC
Both upstream and downstream patches are merged. Can we update this BZ with the latest status? (asking as it is set as high severity and priority).

Comment 2 Francesco Pantano 2022-06-07 08:30:01 UTC
(In reply to Yaniv Kaul from comment #1)
> Both upstream and downstream patches are merged. Can we update this BZ with
> the latest status? (asking as it is set as high severity and priority).

The upstream patch is still waiting [1] to merge (otherwise we risk to break the current TripleO CI).
For the same reason, since downstream we run upstream jobs with the downstream bits, we had to revert
[2] via [3] (it works for IR based jobs but not for quickstart).

Once [1] is ready downstream, then we can move forward with this bug. 


[1] https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/834352
[2] https://code.engineering.redhat.com/gerrit/406770
[3] https://code.engineering.redhat.com/gerrit/c/python-tripleoclient/+/406914

Comment 10 John Fulton 2022-09-08 14:36:51 UTC
Root cause for qe failure:

The overcloud_deploy.py installed by the FIV RPM [0] is missing lines from the original fix [1].

If we manually apply the fix to this file and re-run the test we see the expected results [2].


[0] python3-tripleoclient-16.4.1-0.20220705111521.23dbe54.el9ost.noarch
[1] https://review.opendev.org/c/openstack/python-tripleoclient/+/839727/15/tripleoclient/v1/overcloud_deploy.py

[2] 
2022-09-08 14:17:14.492 229732 INFO tripleoclient.heat_launcher [-] Deleting /home/stack/overcloud-deploy/overcloud/heat-launcher/log/heat-1662646622.1236708.log                            
2022-09-08 14:17:14.492 229732 ERROR openstack [-] Ceph deployment is not available anymore during overcloud deploy. If you want to deploy Ceph, please see "openstack  overcloud ceph deploy
--help" to deploy ceph  before deploying the overcloud and then include the cephadm environment file.: tripleoclient.exceptions.InvalidConfiguration: Ceph deployment is not available anymore during overcloud deploy. If you want to deploy Ceph, please see "openstack  overcloud ceph deploy --help" to deploy ceph  before deploying the overcloud and then include the cephadm environment file.
2022-09-08 14:17:14.494 229732 INFO osc_lib.shell [-] END return value: 1

Comment 24 errata-xmlrpc 2023-01-25 12:28:47 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 OpenStack Platform 17.0.1 bug fix and enhancement advisory), 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:0271