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

Bug 1825539

Summary:	[Backport][RHOSP16.1] Support for redfish management cleaning steps in sushy-oem-idrac
Product:	Red Hat OpenStack	Reporter:	Chris Dearborn <christopher_dearborn>
Component:	python-sushy	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED DEFERRED	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.0 (Train)	CC:	achernet, arkady_kanevsky, athomas, bfournie, dsneddon, ietingof, jkreger, kholtz, kurt_hey, morazi, rajini.karthik, richard.pioso, sbaker
Target Milestone:	---	Keywords:	OtherQA, Triaged
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:	2021-02-23 20:42:50 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:
Bug Depends On:
Bug Blocks:	1667921, 1718945, 1825535

Description Chris Dearborn 2020-04-18 18:02:48 UTC

Description of problem:
Support for redfish management cleaning steps in sushy-oem-idrac

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Julia Kreger 2020-08-13 14:05:14 UTC

It appears that this item requested for backport is pending on an upstream patch which has not gotten through the upstream review process. I've reached out to Richard Pioso who is the only individual with access to approve the patch to merge at this time. Once that merges, it seems reasonable that we can then evaluate the next step forward and if it will be possible to backport or not. Realistically, because this is setup as a branch-less library, we will likely need to carry a downstream patch to perform this functionality unless Dell can release a 0.0.3 version and ensure that no breaking changes are between that version and the current version on master branch.

Comment 2 Richard Pioso 2021-01-14 18:26:11 UTC

(In reply to Julia Kreger from comment #1)
> It appears that this item requested for backport is pending on an upstream
> patch which has not gotten through the upstream review process. I've reached
> out to Richard Pioso who is the only individual with access to approve the
> patch to merge at this time.

We added a couple of reviewers, Christopher Dearborn and Aija Jaunteva.

> Once that merges, it seems reasonable that we
> can then evaluate the next step forward and if it will be possible to
> backport or not.

Thank you, Julia!

> Realistically, because this is setup as a branch-less
> library, we will likely need to carry a downstream patch to perform this
> functionality unless Dell can release a 0.0.3 version and ensure that no
> breaking changes are between that version and the current version on master
> branch.

The library is fairly new. A branch was created for Victoria, stable/victoria. The changes will not be breaking.

Finally, we are actively reviewing the changes.

Comment 3 Steve Baker 2021-02-23 20:42:50 UTC

I think we should close these backport bugs until the changes have landed in upstream master, then we will have something to act on.

Also when we evaluate this for backport potential it will likely be targeted at 16.2