[Bug 1978465] Re: [SRU] Stable point releases for python-os-brick

Tue Jul 19 15:56:16 UTC 2022

Verified successfully on victoria-proposed:

======
Totals
======
Ran: 106 tests in 1706.9799 sec.
 - Passed: 89
 - Skipped: 16
 - Expected Fail: 0
 - Unexpected Success: 0
 - Failed: 1
Sum of execute time for each test: 559.3312 sec.

Note: The failure is unrelated and a known policy issues with octavia.

** Tags removed: verification-victoria-needed
** Tags added: verification-victoria-done

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to python-os-brick in Ubuntu.
https://bugs.launchpad.net/bugs/1978465

Title:
  [SRU] Stable point releases for python-os-brick

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive ussuri series:
  Fix Committed
Status in Ubuntu Cloud Archive victoria series:
  Fix Committed
Status in Ubuntu Cloud Archive wallaby series:
  Fix Committed
Status in Ubuntu Cloud Archive xena series:
  Fix Committed
Status in python-os-brick package in Ubuntu:
  Fix Released
Status in python-os-brick source package in Focal:
  Fix Committed
Status in python-os-brick source package in Impish:
  Won't Fix

Bug description:
  [Impact]
  This release sports mostly bug-fixes and we would like to make sure all of our users have access to these improvements.

  While python-os-brick is not covered under the OpenStack stable
  release exception I would like to see if these would be covered by the
  Ubuntu SRU "New upstream microrelease" exception.

  The update contains the following package updates:

     * python-os-brick 5.0.2 (Xena/Impish)
     * python-os-brick 4.3.3 (Wallaby)
     * python-os-brick 4.0.5 (Victoria)
     * python-os-brick 3.0.8 (Ussuri/Focal)

  [Test Case]
  The following SRU process was followed:
  https://wiki.ubuntu.com/OpenStack/StableReleaseUpdates

  In order to avoid regression of existing consumers, the OpenStack team
  will run their continuous integration test against the packages that
  are in -proposed. A successful run of all available  tests will be
  required before the proposed packages can be let into -updates.

  The OpenStack team will be in charge of attaching the output summary
  of the executed tests. The OpenStack team members will not mark
  ‘verification-done’ until this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the aforementioned tests are attached to this bug.

  [Discussion]
  Thew new versions of os-brick are defined by opentack's upper-constraints  which are the versions that get tested by the upstream gate: https://github.com/openstack/requirements/blob/master/upper-constraints.txt

  Following are the delta of fixes between the current versions in
  Ubuntu/UCA and the new versions that we would like to pick up:

  # Xena (Impish)
  /tmp/os-brick$ git-pretty 5.0.1..5.0.2
   - [19a4820] Use file locks in connectors
   - [4d11648] multipath/iscsi: iSCSI connections are not reinitiated after reboot

  # Wallaby
  /tmp/os-brick$ git-pretty 4.3.1..4.3.3
   - [d09dc9e] linuxscsi: Only raise and log multipathd errors when required
   - [ecaf7f8] Use file locks in connectors
   - [779d1e4] multipath/iscsi: iSCSI connections are not reinitiated after reboot
   - [0c7f5fc] NVMe-oF: Flush on disconnect
   - [0cd58a9] multipath/iscsi: remove devices from multipath monitoring
   - [d0884a8] Drop lower-constraints job

  # Victoria
  /tmp/os-brick$ git-pretty 4.0.1..4.0.5
   - [ffe0cbf] linuxscsi: Only raise and log multipathd errors when required
   - [b03eca8] Use file locks in connectors
   - [7c7650b] multipath/iscsi: iSCSI connections are not reinitiated after reboot
   - [a0e995b] multipath/iscsi: remove devices from multipath monitoring
   - [9f73446] Drop lower-constraints job
   - [9528cea] iSCSI: Fix flushing after multipath cfg change
   - [57c8f43] Avoid unhandled exceptions during connecting to iSCSI portals
   - [3adcb40] FC: Fix not flushing on detach
   - [9317f9f] ScaleIO: More connection info backward compatibility
   - [2bf4dcc] opencas: Use BrickException instead of Exception
   - [958e4f5] Improve error handling on target query
   - [1ffde6b] Adjust requirements and lower-constraints

  # Ussuri (Focal)
  /tmp/os-brick$ git-pretty 3.0.1..3.0.8
   - [9d3ce01] Use file locks in connectors
   - [d0eea8a] multipath/iscsi: iSCSI connections are not reinitiated after reboot
   - [c336cb7] Avoid unhandled exceptions during connecting to iSCSI portals
   - [5c031cb] multipath/iscsi: remove devices from multipath monitoring
   - [579e464] Drop lower-constraints job
   - [4894b24] iSCSI: Fix flushing after multipath cfg change
   - [fba9810] ScaleIO: More connection info backward compatibility
   - [1e7ad8b] FC: Fix not flushing on detach
   - [897dbdb] Improve error handling on target query
   - [f815146] Add oslo.context dependency
   - [9a8726a] Adjust lower-constraints
   - [91c73a4] New fix for rbd connector to work with ceph octopus
   - [d3ee7a0] rbd: Warn if ceph udev rules are not configured
   - [31c01b5] Leverage the iSCSI mpath to get the WWN
   - [a04e553] iSCSI detect multipath DM with no WWN
   - [930ce7f] Add release note for scaleio connector upgrade
   - [31589a6] ScaleIO: Connection info backward compatibility
   - [935daea] Improve WWN detection
   - [9491b6a] prepend platform info to by-path string
   - [bf0faea] rbd: Support 'rbd showmapped' output from ceph 13.2.0+
   - [a1c9f64] Remove VxFlex OS credentials from connection_properties
   - [55cfc97] rbd: Correct local_attach disconnect test and showmapped arguments
   - [dfd835e] Fix hacking min version to 3.0.1
   - [396fe1a] Update TOX/UPPER_CONSTRAINTS_FILE for stable/ussuri
   - [0cc24c0] Update .gitreview for stable/ussuri

  [Discussion]
  It is important to note that upstream has:

  1) a reliable and credible test suite for assuring the quality of every commit or release,
  2) the tests are covering both functionality and API/ABI stability

  The upstream policy for testing is described a bit here: https://docs.openstack.org/cinder/latest/contributor/contributing.html#getting-your-patch-merged
  (specifically see the paragraphs starting with "Patches lacking unit tests are unlikely to be approved." and "If your patch has a -1 from Zuul.."). Pep8, unit, and functional (tempest) tests are run during the gate for each patch. For example, looking at the following upstream review: https://review.opendev.org/c/openstack/os-brick/+/822025 we can see that zuul tests must vote +1 in order for the patch to be merged. It is also important to note the upstream openstack stable branch policy noted at https://docs.openstack.org/project-team-guide/stable-branches.html#review-guidelines.

  It is also import to note that the ubuntu package has:

  1) unit tests run during package build to cover all architectures

  Additionally, the OpenStack team will run their continuous integration
  test against the packages that are in -proposed (a juju deployed
  openstack with tempest functional tests executed to validate the
  cloud). A successful run of all available tests will be required
  before the proposed packages can be let into -updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1978465/+subscriptions