Bug in SubcloudNotFound exception handling
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Jessica Castelino |
Bug Description
Brief Description
-----------------
During the investigation for bug 1883589, two other issues were found that should be fixed in the stx.5.0 release. From the review comments:
If you decide to cleanup the logs associated with this failure, there's probably 2 places
1) Where the SubcloudNotFound was raised with improper arguments
https:/
2) Where self.msg does not get set if improper arguments are passed
https:/
Severity
--------
Minor - an exception is not generated correctly in an error case and makes debugging the issue more difficult
Steps to Reproduce
------------------
Code changes would likely be required to trigger the exception
Expected Behavior
------------------
Exception generated cleanly
Actual Behavior
----------------
Exception is generated incorrectly.
Reproducibility
---------------
<Reproducible/
State if the issue is 100% reproducible, intermittent or seen once. If it is intermittent, state the frequency of occurrence
System Configuration
-------
Distributed Cloud
Branch/Pull Time/Commit
-------
6th June, 2020
Last Pass
---------
never
Timestamp/Logs
--------------
See bug 1883589
Test Activity
-------------
Developer Testing
Workaround
----------
none
tags: | added: stx.distcloud |
stx.5.0 - minor impact, but would be nice to fix to improve debug-ability