nfv client shows raw REST results for 500 errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Al Bailey |
Bug Description
Brief Description
-----------------
When "sw-manager <some strategy> apply" receives a 500 error, the CLI shows a mess of raw REST results.
This issue is purely cosmetic but should be cleaned up.
there are 2 print statements in the rest_api.py for nfv_client that should be removed.
Severity
--------
Minor
Steps to Reproduce
------------------
sw-manager kube-rootca-
sw-manager kube-rootca-
( then apply a second time after it has completed or failed)
sw-manager kube-rootca-
Expected Behavior
------------------
Should not show a mess
Actual Behavior
----------------
sw-manager kube-rootca-
Rest-API status=500, POST, http://
HTTP Error 500: Internal Server Error
Reproducibility
---------------
100% If the strategy is in a scenario where it will report a 500 failure (like there are active alarms, or the strategy has already been applied)
System Configuration
-------
AIO-SX
Branch/Pull Time/Commit
-------
Nov 16 2022
Last Pass
---------
N/A
Timestamp/Logs
--------------
See the logs above
Test Activity
-------------
Developer Testing
Workaround
----------
None. it is cosmetic.
Changed in starlingx: | |
assignee: | nobody → Al Bailey (albailey1974) |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.8.0 stx.nfv |
Fix proposed to branch: master /review. opendev. org/c/starlingx /nfv/+/ 864779
Review: https:/