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 2098777

Summary: [RFE] [orchestrator] : Upgrade : Status message needs to be tuned when upgrade is initiated with same image
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vasishta <vashastr>
Component: CephadmAssignee: Adam King <adking>
Status: CLOSED DEFERRED QA Contact: Manasa <mgowri>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.2CC: cephqe-warriors, mobisht, saraut
Target Milestone: ---Keywords: FutureFeature
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-29 07:40:40 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-06-20 09:32:29 UTC
Description of problem:
When Upgrade to same image is initiated upgrade status still has "services_complete": field and progress says "progress": "x/y daemons upgraded".

This might send out a wrong message that there were some upgrade of daemon happened which should not happen.

Users with disconnected env might use custom image name with different image name for each new container and might end up trying out upgrade start with same image name. So this issue is good to fix.

Version-Release number of selected component (if applicable):
16.2.8-50.el8cp

Steps to Reproduce:
1. Configure RHCS cluster
2. Upgrade cluster to updated container image.
3. Initiate upgrade once again with same image once first upgrade is done.
and check upgrade status.

Actual results:
>> "progress": "32/42 daemons upgraded"
Even when there were no upgrade of daemons happened as upgrade was initiated with same image

Expected results:
"progress" section in upgrade status must not depict that X daemons were upgraded when there was not upgrade involved.

Additional info:

Comment 9 Abhishek Kane 2025-06-10 04:15:18 UTC
Moving all the RFEs out of 9.0 as they were not prioritized by PMs, and engineering team doesn't have bandwidth to take them up.

Comment 10 Sahina Bose 2025-08-29 07:40:40 UTC
Closing this bug as part of bulk closing of bugs that have been open for more than a year without any significant updates. Please reopen with justification if you think this bug is still relevant and needs to be addressed in an upcoming release