Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2029540

Summary:	python-sushy library tracking is pinned to a version, not synced nor tracking stable branch [17.0]
Product:	Red Hat OpenStack	Reporter:	Julia Kreger <jkreger>
Component:	python-sushy	Assignee:	OSP Team <rhos-maint>
Status:	CLOSED NOTABUG	QA Contact:	Arik Chernetsky <achernet>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	17.0 (Wallaby)	CC:	achernet, jschluet, rhos-maint, sbaker
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:	2029532	Environment:
Last Closed:	2022-01-10 15:11:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Jon Schlueter 2021-12-06 17:53:37 UTC

Description of problem:

Downstream package tracking is based upon a fixed release version of python-sushy, in particular for Train based releases of OpenStack, the version is locked to the very last upstream release of the python-sushy library.

While upstream, we're no longer able to cut new releases for the Train version of the library, we do occasionally land fixes upstream which we need to get downstream or have cases which would have been completely prevented if we were tracking the stable branch upstream.

At present, python-sushy 2.0.5 is what is shipped however we need to be able to pull down patches to stable branches and not have them overwritten upon the next sync. Two patches exist which we would like to ultimately merge into 16.1 and 16.2 OSP releases, requiring the packaging pipeline to be updated.

Comment 2 Steve Baker 2021-12-07 20:36:07 UTC

Assigning to PCD, its our component but we can't make this change