Bug 2140139

Summary:	Sizer gist state bug when using count >1
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Chris Blum <cblum>
Component:	odf-sizer-tool	Assignee:	Bipul Adhikari <badhikar>
Status:	VERIFIED ---	QA Contact:	Prasad Desala <tdesala>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.12	CC:	badhikar, jefbrown, muagarwa, nthomas, odf-bz-bot, skatiyar
Target Milestone:	---
Target Release:	---
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:		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 Chris Blum 2022-11-04 15:44:24 UTC

Description of problem (please be detailed as possible and provide log
snippests):
When configuring a cluster with a workload that has count set to something other than 1, the state that will be saved to the gist when creating a link will have duplicates of that workload, each set to the same count value

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, link sharing broken

Is there any workaround available to the best of your knowledge?
Manually fixing the gist :/

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes

Steps to Reproduce:
1. Open the Sizer
2. Use one of the Workload templates
3. Set the count of the new Workload to 3
4. Go to the Results tab, create a sharing link
5. Use the sharing link


Actual results:
The Workloads tab looks the same as before using the Sharing link, but the node count is increased now, showing that we now actually have 9 (3*3) Workloads, instead of the expected 3.


Expected results:
There are only 3 Workloads scheduled

Additional info:
When saving the state we need to either
1) Set count to 1 or preferably:
2) Remove the duplicates and keep the count value

Comment 10 Chris Blum 2023-04-26 10:11:22 UTC

issue is still there in the prod and beta version. Easiest way to try out is the small postgres workload, set count to 3, then go to result tab, get sharing link and look at the state in gist. It will have three postgres workloads, each set to count=3

Comment 11 Bipul Adhikari 2023-04-27 09:41:18 UTC

Should work on production link as well.

Comment 12 Chris Blum 2023-04-27 10:23:32 UTC

confirmed