diff options
| author | Mark Goddard <mark@stackhpc.com> | 2019-08-12 16:19:37 +0100 |
|---|---|---|
| committer | Mark Goddard <mark@stackhpc.com> | 2019-12-04 11:26:01 +0000 |
| commit | 0bd26cc47ed51d19e07280db9e770ad09edd2bf8 (patch) | |
| tree | e3b04134588e934ed87006658020cd5a59ec2403 /tox.ini | |
| parent | 42faaabdeeaa45c8916f601ece2ca60f37443a3d (diff) | |
| download | python-ironicclient-stein-eol.tar.gz | |
Fix AttributeError in negotiate_versionstein-eolstein-em2.7.3stable/stein
Seen in kolla-ansible CI, if ironic inspector starts up before ironic
API is properly up, we see the following error:
The PXE filter DnsmasqFilter, state=initialized encountered an
exception: StrictVersion instance has no attribute 'version'; resetting
the filter: AttributeError: StrictVersion instance has no attribute
'version'
Example: http://paste.openstack.org/show/756342/
The usual cause of this error is when StrictVersion is initialised with
a version of None. This suggests to me that max_ver is None.
This leads to an exception being raised that circumvents the client's
retry mechanisms.
In the particular case of kolla-ansible CI, Ironic API is behind a load
balancer, and all backends are down resulting in a 503. The lack of a
retry caused ironic inspector to fail on startup.
This patch catches the case where we get a 4xx or 5xx return code when
checking the version, and raises an error that works with the client's
retry mechanisms.
Change-Id: Ib62ca3ee4626084e5e9b90e93e4fa97938023457
Story: 2006393
Task: 36266
(cherry picked from commit 0e9bf337f1f6aa41f67df2966dacf9e8e897b7da)
Diffstat (limited to 'tox.ini')
0 files changed, 0 insertions, 0 deletions
