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:
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.
(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.
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