Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2107658

Summary: [orchestrator] : upgrade : upgrade progress updation can be tuned to depict exact value
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: CephadmAssignee: Adam King <adking>
Status: CLOSED DEFERRED QA Contact: Sayalee <saraut>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.2CC: cephqe-warriors, mobisht, saraut
Target Milestone: ---   
Target Release: 9.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-08-28 10:18:57 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 Vasishta 2022-07-15 15:28:57 UTC
Description of problem:
Tried 5.2 one build to another build.

Upgrade failed becaused of planned blockade because of RGW issue.

In one cluster initial mgr upgrade was conveyed in upgrade status
>> "progress": "1/81 daemons upgraded"

In another cluster it was not despite the initial mgr upgrade
>> "progress": "0/147 daemons upgraded",
(Observed for more than an hour)

$ sudo ceph versions
..
...
    "mgr": {
        "ceph version 16.2.8-71.el8cp (5b74b47876e6cd6281981e263bc0d543c5ee39c8) pacific (stable)": 1,
        "ceph version 16.2.8-75.el8cp (3b7a6413ab943a935f85f10a25d51a88093d15e9) pacific (stable)": 1
    }


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

How reproducible:
Tried in two clusters observed in one.

Steps to Reproduce:
(Mentioned above)

Actual results:
(Mentioned above)

Expected results:
ceph orch upgrade status to convey the actual status.

Comment 7 Sahina Bose 2025-08-28 10:18:57 UTC
Closing this bug as part of bulk closing of bugs that have been open for more than 2 years without any significant updates for the last 3 months. Please reopen with justification if you think this bug is still relevant and needs to be addressed in an upcoming release