Bug 2098777 - [RFE] [orchestrator] : Upgrade : Status message needs to be tuned when upgrade is initiated with same image
Summary: [RFE] [orchestrator] : Upgrade : Status message needs to be tuned when upgrad...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Cephadm
Version: 5.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 8.0
Assignee: Adam King
QA Contact: Manasa
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-20 09:32 UTC by Vasishta
Modified: 2023-07-05 15:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-4579 0 None None None 2022-06-20 09:49:38 UTC

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:
Note You need to log in before you can comment on or make changes to this bug.