[ironic][release][stable] Ironic Train release can be broken due to entry in driver-requirements.txt

Thomas Goirand zigo at debian.org
Sat Oct 19 17:15:22 UTC 2019

On 10/16/19 2:55 AM, Richard.Pioso at dell.com wrote:
> Hi,
> The Ironic Train release can be broken due to an entry in its driver-requirements.txt. driver-requirements.txt defines a dependency on the sushy package [1] which can be satisfied by version 1.9.0. Unfortunately, that version contains a few bugs which prevent Ironic from being able to manage Dell EMC and perhaps other vendors' bare metal hardware with its Redfish hardware type (driver). The fixes to them [2][3][4] were merged into master before the creation of stable/train. Therefore, they are available on stable/train and in the last sushy release created during the Train cycle, 2.0.0, the only other version which can satisfy the dependency today. However, consumers -- packagers, operators, and users -- could, fighting time constraints or lacking solid visibility into Ironic, package or install Ironic with sushy 1.9.0 to satisfy the dependency, but, in so doing, unknowingly render the package or installation severely broken.

At least in Debian, sushy 2.0.0 is included in the Train release (sushy
2.0.0 was uploaded on the 26th of September). I don't know for other

> A change [5] has been proposed as part of a prospective solution to this issue. It creates a new release of sushy from the change which fixes the first bug [2]. Review comments [6] discuss basing the new release on a more recent stable/train change to pick up other bug fixes and, less importantly, backward compatible feature modifications and enhancements which merged before the change from which 2.0.0 was created. Backward compatible feature modifications and enhancements are interspersed in time among the bug fixes. Once a new release is available, the sushy entry in driver-requirements.txt on stable/train would be updated. However, apparently, the stable branch policy prevents releases from being done at a point earlier than the last release within a given cycle [6], which was 2.0.0.
> Another possible resolution which comes to mind is to change the definition of the sushy dependency in driver-requirements.txt [1] from "sushy>=1.9.0" to "sushy>=2.0.0".
> Does anyone have a suggestion on how to proceed?

I'm not sure if I understand you correctly. Is sushy 2.0.0 enough? Or
should I expect newer tags coming soon?

Thomas Goirand (zigo)

More information about the openstack-discuss mailing list