Introduce a version cap of zhmcclient
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-dpm |
Fix Released
|
Undecided
|
Unassigned | ||
nova-dpm |
Fix Released
|
Undecided
|
Andreas Scheuring |
Bug Description
Description
===========
We use the master code of the zhmcclient instead of the latest stable release.
This means that we could break more easily in case the zhmcclient merges a
behavior we haven't anticipated but plans to fix it before the next stable
release is published. This is due to [1] which copies the powervm behavior [2].
Steps to reproduce
==================
$ git clone https:/
$ cd nova-dpm
$ tox -e py27
$ .tox/py27/bin/pip show zhmcclient
Expected result
===============
It should show the latest stable release of that library. At time of this
bug report, it's version: 0.9.0
$ .tox/py27/bin/pip show zhmcclient
Name: zhmcclient
Version: 0.9.0
Actual result
=============
It shows a development release based on the latest commit of the master branch.
At time of this bug report, it looks like this:
$ .tox/py27/bin/pip show zhmcclient
Name: zhmcclient
Version: 0.9.1.dev2
Environment
===========
nova-dpm version:
$ git log --oneline -1
6f87677 Instance Destroy,
python-zhmcclient version:
$ git log --oneline -1
421ad4d Merge branch 'juergen/
Logs & Configs
==============
N/A
References
==========
[1] https:/
[2] https:/
Changed in networking-dpm: | |
status: | Fix Committed → Fix Released |
https:/ /review. openstack. org/#/c/ 413689/ merges in the next hours, that should enable us to use it in the requirements.txt file like every other dependency.