[Bug 1919451] Please test proposed package

Łukasz Zemczak 1919451 at bugs.launchpad.net
Thu Aug 5 23:19:03 UTC 2021


Hello Frank, or anyone else affected,

Accepted zhmcclient into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/zhmcclient/0.31.0-0ubuntu3~20.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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:
  Fix Committed
Status in zhmcclient source package in Hirsute:
  Fix Committed

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
   * on top and for regression testing the example (as shipped by the zhmcclient) can be ran as well (as far as possible on a non-DPM HMC setup):
  https://github.com/zhmcclient/python-zhmcclient/tree/master/examples

  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.

  Reviewing the changes/commits starting from 0.28 to 0.31 (68 + 37 + 27
  + 15 commits) let me think that these are largely unintrusive, just a
  few new features were added (like DPM Capacity Groups), the docs,
  examples and lots of meta updated, error and exception handling
  refined <important>, and last but not least several important bugs
  fixed (for installation, .find for objects <again important>,
  certificates, missing argument in method) - some of them were
  identified during the development of DPM/LPAR support in MAAS earlier
  this year (for example LP#1916475).

  Therefore, and because the zhmcclient is not wide-spread yet (since
  MAAS v3.0 is the first version that can make use of it and was just
  made available on June the 22nd), it's for accessing and managing Z
  systems only via the HMC API, which not many organizations allow (in
  general - for security reasons) and because v0.31 was the version that
  was already used for development _nd final product testing (these days
  as a git clone), makes me rating the regression risk as low.

  [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




More information about the Ubuntu-sponsors mailing list