yahoo-eng-team team mailing list archive

[Gorka Eguileor <2081859@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In the Zed release os-brick started needing to be initialized by calling
a `setup` method before the library could be used.

At that time there was only 1 feature that depended on it and it was
possible to introduce a failsafe for that instance so things wouldn't
break.

In the Antelope release that failsafe should have been removed from os-
brick and all projects should have been calling the `setup` method.

Currently nova is not initializing os-brick, so if os-brick removes the
failsafe the behavior in os-brick locks will break backward
compatibility.

Related os-brick patch: https://review.opendev.org/c/openstack/os-
brick/+/849324

** Affects: nova
     Importance: Undecided
         Status: In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2081859

Title:
  Nova not initializing os-brick

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  In the Zed release os-brick started needing to be initialized by
  calling a `setup` method before the library could be used.

  At that time there was only 1 feature that depended on it and it was
  possible to introduce a failsafe for that instance so things wouldn't
  break.

  In the Antelope release that failsafe should have been removed from
  os-brick and all projects should have been calling the `setup` method.

  Currently nova is not initializing os-brick, so if os-brick removes
  the failsafe the behavior in os-brick locks will break backward
  compatibility.

  Related os-brick patch: https://review.opendev.org/c/openstack/os-
  brick/+/849324

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2081859/+subscriptions