
The NSX3Client did not get the nsx managers IPs, and they where missing from error messages. To fix this, and also better fix a similar problem with max_attempts, the client init method may get another instance of the client, and copy relevant information from it. This option is used by the copy-constructor "new_client_for" without the RestClient class being aware of arguments relevant only to the NSXClient. Also adding a new test for a resource error message, to make sure it contains the nsx_manager ip. (Cherry picked from : I9e7e28eb5fd69ace44547d40cf8cd09e2457c5ed) Change-Id: I5066ae12aadd286ff880c8545df99a567aeddbeb
vmware-nsxlib
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/vmware-nsxlib
- Source: http://git.openstack.org/cgit/openstack/vmware-nsxlib
- Bugs: http://bugs.launchpad.net/replace with the name of the project on launchpad
Features
- TODO
Description
Languages
Python
99.5%
Shell
0.5%