[Bug 1919451] Re: Update (python-)zhmcclient to latest release

[Robie Basak]

It sounds like this type of update would qualify under the same
principle that MAAS (were it still in the archive) adds new features to
stable releases.

However, please see the requirements at
https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases.
Specifically:

I see no upload for Hirsute, but this is a requirement for new features
in an LTS so that there isn't a regression and lack of ability to
receive updates if users upgrade from the updated Focal to Hirsute.
Please provide an upload for Hirsute.

It must be demonstrated that the changes you propose are unintrusive,
have a minimal regression potential, and have been tested properly. You
could cherry-pick the required features, or you could update to a newer
upstream release wholesale as you're proposing. Please provide an
analysis and explanation as to why you think the latter approach is
better in this case with respect to these requirements, and what you're
doing to meet them. For example, I see nothing in your Test Plan that
seeks to ensure that unrelated behaviour in this package has not
regressed; nor do I see any analysis of the upstream changes to ensure
that functional/behavioural changes have not been made. And what about
other non-MAAS use cases for this package that users might have
established? How do you intend to mitigate regressing such use cases?


** Changed in: zhmcclient (Ubuntu Focal)
       Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1919451

Title:
  Update (python-)zhmcclient to latest release

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zhmcclient package in Ubuntu:
  Fix Released
Status in zhmcclient source package in Focal:
  Incomplete

Bug description:
  [Impact]

  In order to remotely power-cycle IBM z14 GA2 (or newer) or IBM
  LinuxONE III (or newer) machines/LPARs from within a MAAS controller,
  the python3-zhmcclient libraray (>= v0.29) is needed, to provide all
  the functions required for controlling the HMC.

  [Test Plan]
   * setup a MAAS controller inside a LPAR
   * use that controller to deploy a new Ubuntu Server instance in an additional LPAR
   * use that controller to deploy a new Ubuntu Server instance inside a KVM host (inside another LPAR)
   * Power-cycle the LPAR instance
   * Power-cycle the KVM instance

  Also get confirmation from the MAAS team that things are working as
  expected.

  [Where problems could occur]

  This library is s390x only and zhmcclient isn’t widely used yet, it has very limited exposure within the s390 environment. If we would be hit by a regression, we would not be able to power-cycle or deploy any LPAR (or KVM host inside LPAR) machine, using a Focal-based MAAS controller.
  This is basically also the status quo, as the current version in Focal (v0.22) does not allow for that functionality either.

  [Other Info]
  * https://maas.io/docs/snap/3.0/ui/power-management#heading--configure-use-ibm-z
  * As this is only used on MAAS controllers, running LTS releases, the backport is not needed for Hirsute 21.04
  * The new package dependencies are fulfilled in Focal:
    - python3-requests >= 2.20.1 (focal contains 2.22.0-2ubuntu1 in main)
    - python3-decorator >= 4.0.11 (focal contains 4.4.2-0ubuntu1 in main)

  === Original description ===

  While working on MAAS DPM/LPAR it turned out that a newer python-
  zhmcclient (package zhmcclient) is needed to get certain functions
  work, like especially storage group support.

  The latest is package is v0.27 on hirsute and v0.22 on focal.

  v0.28 is currently the latest release, but 0.29 is coming shortly.
  https://github.com/zhmcclient/python-zhmcclient/issues/731

  Hence an updated package (ideally to 0.29) is needed for focal (knowing that this will require a good justification: https://wiki.ubuntu.com/StableReleaseUpdates).
  Please notice that MAAS was the only reason why the zhmcclient package was created at all.

  The updated package is especially needed for focal, since focal is the
  recommended base distro for MAAS DPM/LPAR, hence this would require a
  special SRU (for this package version bump).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions