It's an error in openstackclient/volume/v2/backup.py, line 322, the return value of the "take_action" is an object which is incorrect for the command line return info. I just modify it to the value of _info()
-----邮件原件----- 发件人: Yong Hu [mailto:yong.hu@intel.com] 发送时间: 2019年7月8日 11:52 收件人: starlingx-discuss@lists.starlingx.io 主题: [lists.starlingx.io代发]Re: [Starlingx-discuss] 答复: [lists.starlingx.io代 发]Re: 答复: Help needed to add patch to openstackclient
as Dean mentioned, there might be other way to resolve the problems you see. Probably you can paste your patch here to community so that guys can come up with some suggestions?
On 04/07/2019 8:42 AM, Dean Troyer wrote:
On 7/4/19 10:16 AM, Song Gao song (高松) wrote:
Yes, it has been fixed, but cannot be directly used because maybe the related novaclient or cinderclient project need to upgrade at the same time. It seems that the only solution is to add patch to the starlingx/upstream r2018.10 branch, isn't it?
If you need to continue with that release, yes you will need to backport whatever patches you need. pike is on 'extended maintenance' upstream so nothing that is not a CVE will get fixed there now.
If the fix also depends on other client libs you will need to bring those down too.
Is this fix required for the internal operations of StarlingX? ie, is it the puppet or other internal code that needs it, or is it for your administrative uses that you need it? If it is for admin use, you can install OSC 3.19.0 into a virtual env, even on a controller if necessary, and use it directly.
dt
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss