albailey 515c22944d Propagate unexpected errors from nfv client
The code that was iterating over unexpected errors would
accidentally 'return' rather than raise the error during
the area where it extracts a reason from the exception.

This meant that if the API returned an internal error (500)
the code would mistakenly treat the result as a None response.

This was particularly troublesome when performing GET operations.

Now it reports the error and allows the exception to be raised.

Test Plan:
  PASS: Verify the CLI reports an error when invoked while the API
is beng restarted.
  PASS: Verify the CLI returns a valid value when invoked under
normal circumstances.
  PASS: Verify the API reports an error rather than None when a
strategy is queried during an API restart.

Closes-Bug: 1950207
Signed-off-by: albailey <Al.Bailey@windriver.com>
Change-Id: I7dc62b28425f09edabf2e6e4914aebc013da3cf4
2021-11-09 11:19:26 -06:00
2018-09-25 14:01:33 -07:00
2019-04-19 19:52:26 +00:00
2018-05-31 07:36:51 -07:00
2018-07-10 10:18:28 -05:00

nfv

StarlingX NFVI Orchestration

Description
StarlingX NFVI Orchestration
Readme 40 MiB
Languages
Python 83.2%
JavaScript 7.1%
C++ 6.6%
Shell 1.5%
Handlebars 0.9%
Other 0.7%