Thank you Robie for your thorough review and detailed comments & references.
Thank you Frank for improving upon the original test plan, your volunteering to help with the verification on real hardware and for your review and comments regarding the changes. I also went through the changelog (https://github.com/zhmcclient/python- zhmcclient/blob/9270ac306586b235751d432cf4a7bd4cfac84c0d/docs/changes.rst) since 0.22 (i.e. Focal+) that lists a few "incompatible changes" that we need to be aware of and watch out for: 0.24.0 * Operations that resulted in HTTP status 403, reason 1 ("The user under which the API request was authenticated does not have the required authority to perform the requested action.") so far raised ServerAuthError. However, that exception does not represent that situation properly, because the login user is actually properly authenticated. The handling of this case was changed to now raise HTTPError instead of ServerAuthError. This change is only incompatible to users of the zhmcclient API who have code handling this exception specifically. => Tiny API change in the error handling. 0.28.0 * Removed the installed scripts cpcdata and cpcinfo and added them as cpcdata.py and cpcinfo.py to the examples folder. => Moving of (example) scripts to a different folder, but they are still available. 0.31.0 * Method 'NotificationReceiver.notifications()' now raises JMS errors returned by the HMC as a new exception 'NotificationJMSError'. JSON parse errors are now raised as a new exception 'NotificationParseError'. Both new exceptions are based on a new base exception 'NotificationError'. (issue #770) => Extension of error handling API. * By default, the zhmcclient now verifies the HMC certificate using the CA certificates in the Python 'certifi' package. This can be controlled with a new 'verify_cert' init parameter to the 'zhmcclient.Session' class. (issue #779) => Checking of HMC certificates by default, that can easily be disabled using the 'verify_cert' parameter. * The 'properties' attribute of the resource classes (e.g. 'Partition') now is an immutable 'DictView' object in order to enforce the stated rule that that callers must not modify the properties dictionary. If your code used to make such modifications nevertheless, it will now get a 'TypeError' or 'AttributeError' exception, dependent on the nature of the modification. => This change was reverted in debian/patches/0001-Revert-Changed-properties-attribute-to-be-immutable.patch for compatibility reasons (i.e. missing python immutable-views dependency). Summary: - 2 tiny changes in the error handling API - 1 change of example script installation location - 1 changed default, that can be controlled via 'verify_cert' parameter - 1 reverted change that does not affect our users As Frank stated, the primary user of this package is MAAS v3.0, that was developed and tested with this newer version in mind already. Apart from that the use case of zhmc-client is very small with few (if any at all) external users. Therefore we do not expect to break anybody by introducing those changes. I've uploaded the version bump to Hirsute as well, albeit we expect very little (if any) usage outside the LTS releases. It is included in Impish/devel already. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919451 Title: Update (python-)zhmcclient to latest release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1919451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
