Unmanage/manage a subcloud causes sysinv api exception in subcloud
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Jessica Castelino |
Bug Description
Brief Description
-----------------
In a distributed cloud deployment, when a subcloud is unmanaged and then managed again, the following exception appears in the sysinv logs on each subcloud:
sysinv 2020-01-22 14:00:03.016 99413 ERROR sysinv.
2020-01-22 14:00:03.016 99413 ERROR sysinv.
2020-01-22 14:00:03.016 99413 ERROR sysinv.
2020-01-22 14:00:03.016 99413 ERROR sysinv.
2020-01-22 14:00:03.016 99413 ERROR sysinv.
2020-01-22 14:00:03.016 99413 ERROR sysinv.
2020-01-22 14:00:03.016 99413 ERROR sysinv.
2020-01-22 14:00:03.016 99413 ERROR sysinv.
2020-01-22 14:00:03.016 99413 ERROR sysinv.
2020-01-22 14:00:03.016 99413 ERROR sysinv.
Severity
--------
Unknown - I don't know the functional impact of this exception
Steps to Reproduce
------------------
Install a distributed cloud system with at least one subcloud.
Unmanage and manage the subcloud.
Expected Behavior
------------------
Managing a subcloud should not result in exceptions.
Actual Behavior
----------------
Managing the subcloud causes an exception in the sysinv API in the subcloud.
Reproducibility
---------------
Reproducible
System Configuration
-------
Distributed cloud with AIO-DX system controller and AIO-SX subcloud.
Branch/Pull Time/Commit
-------
Designer load built on January 16, 2020.
Last Pass
---------
Unknown
Timestamp/Logs
--------------
See above
Test Activity
-------------
Developer Testing
Workaround
----------
None
Changed in starlingx: | |
status: | Fix Released → Triaged |
assignee: | Yang Liu (yliu12) → nobody |
Changed in starlingx: | |
assignee: | nobody → Jessica Castelino (jcasteli) |
stx.4.0 / medium priority - unexpected exception on DC.